Go to file
John Wiegley 35786cb7e8 Use Git's own tree entry sorting algorithm
If plain strcmp is used, as this code did before, the final sorting may
end up different from what git-add would do (for example, 'boost'
appearing before 'boost-build.jam', because Git sorts as if it were
spelled 'boost/').

If the sorting is incorrect like this, Git 1.7.4 insists that unmodified
files have been modified.  For example, my test repository has these
four entries:

drwxr-xr-x  199 johnw  wheel   6766 Feb  2 17:21 boost
-rw-r--r--    1 johnw  wheel    849 Feb  2 17:22 boost-build.jam
-rw-r--r--    1 johnw  wheel    989 Feb  2 17:21 boost.css
-rw-r--r--    1 johnw  wheel   6308 Feb  2 17:21 boost.png

Here is the output from git-ls-tree for these files, in a commit tree
created using git-add and git-commit:

100644 blob 8b8775433aef73e9e12609610ae2e35cf1e7ec2c    boost-build.jam
100644 blob 986c4050fa96d825a1311c8e871cdcc9a3e0d2c3    boost.css
100644 blob b4d51fcd5c9149fd77f5ca6ed2b6b1b70e8fe24f    boost.png
040000 tree 46537eeaa4d577010f19b1c9e940cae9a670ff5c    boost

Here is the output for the same commit produced using libgit2:

040000 tree c27c0fd1436f28a6ba99acd0a6c17d178ed58288	boost
100644 blob 8b8775433aef73e9e12609610ae2e35cf1e7ec2c	boost-build.jam
100644 blob 986c4050fa96d825a1311c8e871cdcc9a3e0d2c3	boost.css
100644 blob b4d51fcd5c9149fd77f5ca6ed2b6b1b70e8fe24f	boost.png

Due to this reordering, git-status claims the three blobs are always
modified, no matter what I do using git-read-tree or git-reset or
git-checkout to update the index.
2011-02-03 01:47:26 -05:00
src Use Git's own tree entry sorting algorithm 2011-02-03 01:47:26 -05:00
tests Refactor reference parsing code 2011-01-30 02:35:29 +02:00
.gitignore Fixed .gitignore typo. 2010-12-04 14:04:12 +01:00
.HEADER Switch the license from BSD to GPL+libgcc exception 2008-11-01 15:55:47 -07:00
api.doxygen fix doxygen setup and automate generation 2010-12-08 10:35:55 -08:00
CMakeLists.txt Update install info and test resource path handling 2010-12-12 00:20:43 +02:00
CONVENTIONS Move include files to include/git/, drop git_ prefix from file names 2008-11-01 15:42:23 -07:00
COPYING Switch the license from BSD to GPL+libgcc exception 2008-11-01 15:55:47 -07:00
git.git-authors Correct Adam Simpkins' name 2010-04-15 09:57:58 +02:00
libgit2.pc.in Add support for installing to a libdir other than 'lib'. 2009-02-01 15:00:10 -08:00
README.md Add Delphi bindings to the readme 2011-01-08 21:54:14 +02:00
waf Add more features to the build system 2010-11-24 00:23:14 +02:00
wscript Revised build configuration for MSVC. 2011-01-08 22:17:01 +02:00

libgit2 - the Git linkable library

libgit2 is a portable, pure C implementation of the Git core methods provided as a re-entrant linkable library with a solid API, allowing you to write native speed custom Git applications in any language with bindings.

What It Can Do

libgit2 is already very usable.

  • raw <-> hex SHA conversions
  • raw object reading (loose and packed)
  • raw object writing (loose)
  • revlist walker
  • commit, tag and tree object parsing and write-back
  • tree traversal
  • basic index file (staging area) operations

Building libgit2 - External dependencies

The following libraries are required to manually build the libgit2 library:

When building in Windows using MSVC, make sure you compile ZLib using the MSVC solution that ships in its source distribution. Alternatively, you may download precompiled binaries from: http://www.winimage.com/zLibDll/

libgit2 can be built using the SHA1 implementation of LibSSL-Crypto, instead of the built-in custom implementations. Performance wise, they are quite similar.

Building libgit2 - Using waf

Waf is a minimalist build system which only requires a Python 2.5+ interpreter to run. This is the default build system for libgit2.

To build libgit2 using waf, first configure the build system by running:

$ ./waf configure

Then build the library, either in its shared (libgit2.so) or static form (libgit2.a):

$ ./waf build-static
$ ./waf build-shared

You can then run the full test suite with:

$ ./waf test

And finally you can install the library with (you may need to sudo):

$ sudo ./waf install

The waf build system for libgit2 accepts the following flags:

--debug
	build the library with debug symbols.
	Defaults to off.

--sha1=[builtin|ppc|openssl]
	use the builtin SHA1 functions, the optimized PPC versions
	or the SHA1 functions from LibCrypto (OpenSSL).
	Defaults to 'builtin'.

--msvc=[7.1|8.0|9.0|10.0]
	Force a specific version of the MSVC compiler, if more than
	one version is installed.

--arch=[ia64|x64|x86|x86_amd64|x86_ia64]
	Force a specific architecture for compilers that support it.

You can run ./waf --help to see a full list of install options and targets.

Building libgit2 - Using CMake

The libgit2 library can also be built using CMake 2.6+ (http://www.cmake.org) on all platforms.

On most systems you can build the library using the following commands

$ mkdir build && cd build
$ cmake ..
$ cmake --build .

Alternatively you can point the CMake GUI tool to the CMakeLists.txt file and generate platform specific build project or IDE workspace.

To install the library you can specify the install prefix by setting:

$ cmake .. -DCMAKE_INSTALL_PREFIX=/install/prefix
$ cmake --build . --target install

For more advanced use or questions about CMake please read http://www.cmake.org/Wiki/CMake_FAQ.

Language Bindings

Here are the bindings to libgit2 that are currently available:

If you start another language binding to libgit2, please let us know so we can add it to the list.

How Can I Contribute

Fork libgit2/libgit2 on GitHub, add your improvement, push it to a branch in your fork named for the topic, send a pull request.

You can also file bugs or feature requests under the libgit2 project on GitHub, or join us on the mailing list by sending an email to:

libgit2@librelist.com

License

libgit2 is under GPL2 with linking exemption. This means you can link to the library with any program, commercial, open source or other. However, you cannot modify libgit2 and distribute it without supplying the source.

See the COPYING file for the full license text.