git2go/git_system_static.go

// +build static,system_libgit2

package git

/*
#cgo pkg-config: libgit2 --static
#cgo CFLAGS: -DLIBGIT2_STATIC
#include <git2.h>

#if LIBGIT2_VER_MAJOR != 1 || LIBGIT2_VER_MINOR != 1
# error "Invalid libgit2 version; this git2go supports libgit2 v1.1"
#endif
*/
import "C"
Revamp the ways in which the library can be built (#621) This change allows to link the system version of libgit2 statically. Since `-tags static` is already used for the bundled version of the library and to avoid breaking old workflows, `-tags static,system_libgit2` is now used to select that. This means that the valid combinations are: \| Flag \| Effect \| \|-------------------------------\|-----------------------------------------------\| \| _No flags_ \| Dynamically-linked against the system libgit2 \| \| `-tags static,system_libgit2` \| Statically-linked against the system libgit2 \| \| `-tags static` \| Statically-linked against the bundled libgit2 \| Note that there is no way to express dynamically linking against the bundled libgit2 because that makes very little sense, since the binaries wouldn't be able to be distributed. If that's still desired, the `PKG_CONFIG_PATH` environment variable can set before building the code. [`Makefile`](https://github.com/libgit2/git2go/blob/master/Makefile) has an example of how it is used in the CI. 2020-06-21 17:40:52 -05:00			`// +build static,system_libgit2`
Allow building statically via the "static" build tag 2016-11-19 08:48:39 -06:00
			`package git`

			`/*`
Revamp the ways in which the library can be built (#621) This change allows to link the system version of libgit2 statically. Since `-tags static` is already used for the bundled version of the library and to avoid breaking old workflows, `-tags static,system_libgit2` is now used to select that. This means that the valid combinations are: \| Flag \| Effect \| \|-------------------------------\|-----------------------------------------------\| \| _No flags_ \| Dynamically-linked against the system libgit2 \| \| `-tags static,system_libgit2` \| Statically-linked against the system libgit2 \| \| `-tags static` \| Statically-linked against the bundled libgit2 \| Note that there is no way to express dynamically linking against the bundled libgit2 because that makes very little sense, since the binaries wouldn't be able to be distributed. If that's still desired, the `PKG_CONFIG_PATH` environment variable can set before building the code. [`Makefile`](https://github.com/libgit2/git2go/blob/master/Makefile) has an example of how it is used in the CI. 2020-06-21 17:40:52 -05:00			`#cgo pkg-config: libgit2 --static`
			`#cgo CFLAGS: -DLIBGIT2_STATIC`
Allow building statically via the "static" build tag 2016-11-19 08:48:39 -06:00			`#include <git2.h>`

Create v31 to support libgit2 v1.1.x (#668) The libgit2 `v1.1.0` is released two weeks ago. This PR allows `git2go` to link against the new version. 2020-10-26 20:09:26 -05:00			`#if LIBGIT2_VER_MAJOR != 1 \|\| LIBGIT2_VER_MINOR != 1`
			`# error "Invalid libgit2 version; this git2go supports libgit2 v1.1"`
Allow building statically via the "static" build tag 2016-11-19 08:48:39 -06:00			`#endif`
			`*/`
			`import "C"`