libgit2-sys
Advanced tools
| Build Status | |
|---|---|
| main branch builds |   |
| v1.9 branch builds |   |
| v1.8 branch builds |   |
| Nightly builds |   |
libgit2 is a portable, pure C implementation of the Git core methods
provided as a linkable library with a solid API, allowing to build Git
functionality into your application.
libgit2 is used in a variety of places, from GUI clients to hosting
providers ("forges") and countless utilities and applications in
between. Because it's written in C, it can be made available to any
other programming language through "bindings", so you can use it in
Ruby,
.NET,
Python,
Node.js,
Rust, and more.
libgit2 is licensed under a very permissive license (GPLv2 with
a special Linking Exception). This means that you can link against
the library with any kind of software without making that software
fall under the GPL. Changes to libgit2 would still be covered under
its GPL license.
Most of these instructions assume that you're writing an application in C and want to use libgit2 directly. If you're not using C, and you're writing in a different language or platform like .NET, Node.js, or Ruby, then there is probably a "language binding" that you can use to take care of the messy tasks of calling into native code.
But if you do want to use libgit2 directly - because you're building an application in C - then you may be able use an existing binary. There are packages for the vcpkg and conan package managers. And libgit2 is available in Homebrew and most Linux distributions.
However, these versions may be outdated and we recommend using the latest version if possible. Thankfully libgit2 is not hard to compile.
Prerequisites for building libgit2:
PATH.PATH.Build
mkdir build && cd buildcmake ..cmake --build .Trouble with these steps? Read our troubleshooting guide. More detailed build guidance is available below.
Chat with us
#libgit2Getting Help
If you have questions about the library, please be sure to check out the
API documentation. If you still have
questions, reach out to us on Slack or post a question on
StackOverflow
(with the libgit2 tag).
Reporting Bugs
Please open a GitHub Issue and include as much information as possible. If possible, provide sample code that illustrates the problem you're seeing. If you're seeing a bug only on a specific repository, please provide a link to it if possible.
We ask that you not open a GitHub Issue for help, only for bug reports.
Reporting Security Issues
Please have a look at SECURITY.md.
libgit2 provides you with the ability to manage Git repositories in the programming language of your choice. It's used in production to power many applications including GitHub.com, Plastic SCM and Azure DevOps.
It does not aim to replace the git tool or its user-facing commands. Some APIs resemble the plumbing commands as those align closely with the concepts of the Git system, but most commands a user would type are out of scope for this library to implement directly.
The library provides:
As libgit2 is purely a consumer of the Git system, we have to adjust to changes made upstream. This has two major consequences:
While the library provides git functionality with very few dependencies, some recommended dependencies are used for performance or complete functionality.
The library needs to keep track of some global state. Call
git_libgit2_init();
before calling any other libgit2 functions. You can call this function many times. A matching number of calls to
git_libgit2_shutdown();
will free the resources. Note that if you have worker threads, you should
call git_libgit2_shutdown after those threads have exited. If you
require assistance coordinating this, simply have the worker threads call
git_libgit2_init at startup and git_libgit2_shutdown at shutdown.
See threading for information
See conventions for an overview of the external and internal API/coding conventions we use.
libgit2 builds cleanly on most platforms without any external
dependencies as a requirement. libgit2 is built using
CMake (version 2.8 or newer) on all platforms.
On most systems you can build the library using the following commands
$ mkdir build && cd build
$ cmake ..
$ cmake --build .
To include the examples in the build, use cmake -DBUILD_EXAMPLES=ON ..
instead of cmake ... The built executable for the examples can then
be found in build/examples, relative to the toplevel directory.
Alternatively you can point the CMake GUI tool to the CMakeLists.txt file and generate platform specific build project or IDE workspace.
If you're not familiar with CMake, a more detailed explanation may be helpful.
You can specify a number of options to cmake that will change the
way libgit2 is built. To use this, specify -Doption=value during
the initial cmake configuration. For example, to enable SHA256
compatibility:
$ mkdir build && cd build
$ cmake -DEXPERIMENTAL_SHA256=ON ..
$ cmake --build .
libgit2 options:
EXPERIMENTAL_SHA256=ON: turns on SHA256 compatibility; note that
this is an API-incompatible change, hence why it is labeled
"experimental"Build options:
BUILD_EXAMPLES=ON: builds the suite of example codeBUILD_FUZZERS=ON: builds the fuzzing suiteENABLE_WERROR=ON: build with -Werror or the equivalent, which turns
compiler warnings into errors in the libgit2 codebase (but not its
dependencies)Dependency options:
USE_SSH=type: enables SSH support and optionally selects the provider;
type can be set to libssh2 or exec (which will execute an external
OpenSSH command). ON implies libssh2; defaults to OFF.USE_HTTPS=type: enables HTTPS support and optionally selects the
provider; type can be set to OpenSSL, OpenSSL-Dynamic (to not
link against OpenSSL, but load it dynamically), SecureTransport,
Schannel or WinHTTP; the default is SecureTransport on macOS,
WinHTTP on Windows, and whichever of OpenSSL or mbedTLS is
detected on other platforms. Defaults to ON.USE_SHA1=type: selects the SHA1 mechanism to use; type can be set
to CollisionDetection, HTTPS to use the system or HTTPS provider,
or one of OpenSSL, OpenSSL-Dynamic, OpenSSL-FIPS (to use FIPS
compliant routines in OpenSSL), CommonCrypto, or Schannel.
Defaults to CollisionDetection. This option is retained for
backward compatibility and should not be changed.USE_SHA256=type: selects the SHA256 mechanism to use; type can be
set to HTTPS to use the system or HTTPS driver, builtin, or one of
OpenSSL, OpenSSL-Dynamic, OpenSSL-FIPS (to use FIPS compliant
routines in OpenSSL), CommonCrypto, or Schannel. Defaults to HTTPS.USE_GSSAPI=<on/off>: enables GSSAPI for SPNEGO authentication on
Unix. Defaults to OFF.USE_HTTP_PARSER=type: selects the HTTP Parser; either http-parser
for an external
http-parser dependency,
llhttp for an external llhttp
dependency, or builtin. Defaults to builtin.REGEX_BACKEND=type: selects the regular expression backend to use;
one of regcomp_l, pcre2, pcre, regcomp, or builtin. The
default is to use regcomp_l where available, PCRE if found, otherwise,
to use the builtin.USE_BUNDLED_ZLIB=type: selects the bundled zlib; either ON or OFF.
Defaults to using the system zlib if available, falling back to the
bundled zlib.The libgit2 project uses cmake since it helps with cross-platform
projects, especially those with many dependencies. If your dependencies
are in non-standard places, you may want to use the _ROOT_DIR options
to specify their location. For example, to specify an OpenSSL location:
$ cmake -DOPENSSL_ROOT_DIR=/tmp/openssl-3.3.2 ..
Since these options are general to CMake, their documentation may be helpful. If you have questions about dependencies, please contact us.
Once built, you can run the tests from the build directory with the command
$ ctest -V
Alternatively you can run the test suite directly using,
$ ./libgit2_tests
Invoking the test suite directly is useful because it allows you to execute
individual tests, or groups of tests using the -s flag. For example, to
run the index tests:
$ ./libgit2_tests -sindex
To run a single test named index::racy::diff, which corresponds to
the test function
test_index_racy__diff:
$ ./libgit2_tests -sindex::racy::diff
The test suite will print a . for every passing test, and an F for any
failing test. An S indicates that a test was skipped because it is not
applicable to your platform or is particularly expensive.
Note: There should be no failing tests when you build an unmodified source tree from a release, or from the main branch. Please contact us or open an issue if you see test failures.
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 the CMake FAQ.
The following CMake variables are declared:
CMAKE_INSTALL_BINDIR: Where to install binaries to.CMAKE_INSTALL_LIBDIR: Where to install libraries to.CMAKE_INSTALL_INCLUDEDIR: Where to install headers to.BUILD_SHARED_LIBS: Build libgit2 as a Shared Library (defaults to ON)BUILD_TESTS: Build the unit and integration test suites (defaults to ON)USE_THREADS: Build libgit2 with threading support (defaults to ON)To list all build options and their current value, you can do the following:
# Create and set up a build directory
$ mkdir build && cd build
$ cmake ..
# List all build options and their values
$ cmake -L
There are several options that control the behavior of the compiler and linker. These flags may be useful for cross-compilation or specialized setups.
CMAKE_C_FLAGS: Set your own compiler flagsCMAKE_C_STANDARD: the C standard to compile against; defaults to C90CMAKE_C_EXTENSIONS: whether compiler extensions are supported; defaults to OFFCMAKE_FIND_ROOT_PATH: Override the search path for librariesZLIB_LIBRARY, OPENSSL_SSL_LIBRARY AND OPENSSL_CRYPTO_LIBRARY:
Tell CMake where to find those specific librariesLINK_WITH_STATIC_LIBRARIES: Link only with static versions of
system librariesIf you'd like to work with Xcode, you can generate an Xcode project with "-G Xcode".
# Create and set up a build directory
$ mkdir build && cd build
$ cmake -G Xcode ..
[!TIP] Universal binary support:
If you want to build a universal binary for macOS 11.0+, CMake sets it all up for you if you use
-DCMAKE_OSX_ARCHITECTURES="x86_64;arm64"when configuring.[Deprecated] If you want to build a universal binary for Mac OS X (10.4.4 ~ 10.6), CMake sets it all up for you if you use
-DCMAKE_OSX_ARCHITECTURES="i386;x86_64"when configuring.
You can use a pre-existing toolchain file like ios-cmake or write your own.
Assuming you're using the ios-cmake toolchain, the command might look like this:
cmake -G Xcode -DCMAKE_TOOLCHAIN_FILE=path/to/ios.toolchain.cmake -DCMAKE_SYSTEM_NAME=iOS -DPLATFORM=OS64 ..
After generating the project, open the .xcodeproj file in Xcode, select your iOS device or simulator as the target, and build your project.
Extract toolchain from NDK using, make-standalone-toolchain.sh script.
Optionally, crosscompile and install OpenSSL inside of it. Then create CMake
toolchain file that configures paths to your crosscompiler (substitute {PATH}
with full path to the toolchain):
SET(CMAKE_SYSTEM_NAME Linux)
SET(CMAKE_SYSTEM_VERSION Android)
SET(CMAKE_C_COMPILER {PATH}/bin/arm-linux-androideabi-gcc)
SET(CMAKE_CXX_COMPILER {PATH}/bin/arm-linux-androideabi-g++)
SET(CMAKE_FIND_ROOT_PATH {PATH}/sysroot/)
SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
SET(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
SET(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
Add -DCMAKE_TOOLCHAIN_FILE={pathToToolchainFile} to cmake command
when configuring.
If you want to build the library in MinGW environment with SSH support
enabled, you may need to pass
-DCMAKE_LIBRARY_PATH="${MINGW_PREFIX}/${MINGW_CHOST}/lib/" flag
to CMake when configuring. This is because CMake cannot find the
Win32 libraries in MinGW folders by default and you might see an
error message stating that CMake could not resolve ws2_32 library
during configuration.
Another option would be to install msys2-w32api-runtime package before
configuring. This package installs the Win32 libraries into /usr/lib
folder which is by default recognized as the library path by CMake.
Please note though that this package is meant for MSYS subsystem which
is different from MinGW.
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.
We welcome new contributors! We have a number of issues marked as "up for grabs" and "easy fix" that are good places to jump in and get started. There's much more detailed information in our list of outstanding projects.
Please be sure to check the contribution guidelines to understand our workflow, and the libgit2 coding conventions.
libgit2 is under GPL2 with linking exception. This means you can
link to and use the library from any program, proprietary or open source;
paid or gratis. However, if you modify libgit2 itself, you must distribute
the source to your modified version of libgit2.
See the COPYING file for the full license text.
FAQs
Unknown package
We found that libgit2-sys demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
/Research
Newly published Trivy Docker images (0.69.4, 0.69.5, and 0.69.6) were found to contain infostealer IOCs and were pushed to Docker Hub without corresponding GitHub releases.
Research
/Security News
The worm-enabled campaign hit @emilgroup and @teale.io, then used an ICP canister to deliver follow-on payloads.
Research
/Security News
Attackers compromised Trivy GitHub Actions by force-updating tags to deliver malware, exposing CI/CD secrets across affected pipelines.