Build/Link: mention pkg-config and autotools

carlosmn · carlosmn · commit e04220f83d18 · 2013-10-10T00:00:17.000+02:00
diff --git a/docs/guides/build-and-link/index.md b/docs/guides/build-and-link/index.md
@@ -115,13 +115,26 @@ Then select "Add Other…":
 Browse to the location where the libgit2 binaries are located (if you're working from source, this is `/path/to/libgit2/build`), select the `libgit2.dylib` file, and click OK.
 
 
-## Makefiles
+## Makefiles, Autotools
 
-The binaries that are output from the build are dependent on the build system you're using.
-On posix-type systems, the output is typically a `libgit2.so` (or `libgit2.a` if you built statically).
+The binaries that are output from the build are dependent on the build system you're using. On posix-type systems, the output is typically a `libgit2.so` (`.dylib` on MacOS, `libgit2.a` if you built statically).
 
-Using these files is dependent on your application's project system.
-For a Makefile-based build, this is what you'll need:
+Using these files is dependent on your application's project system. If you installed the library to a standard system location, you can use `pkg-config` to get the right flags to pass to the compiler.
+
+```
+LDFLAGS = $(shell pkg-config --libs libgit2)
+CFLAGS = $(shell pkg-config --cflags libgit2)
+```
+
+In the same vein, using GNU Autotools, pkg-config can help you there
+
+```
+PKG_CHECK_MODULES([libgit2], [libgit2])
+AC_SUBST([libgit2_LIBS])
+AC_SUBST([libgit2_FLAGS])
+```
+
+If none of these options are available, then you can do it by hand with
 
 ```
 CFLAGS += -I/path/to/libgit2/include
