12Git installation34Normally you can just do "make" followed by "make install", and that5will install the git programs in your own ~/bin/ directory. If you want6to do a global install, you can do78$ make prefix=/usr all doc info ;# as yourself9# make prefix=/usr install install-doc install-html install-info ;# as root1011(or prefix=/usr/local, of course). Just like any program suite12that uses $prefix, the built results have some paths encoded,13which are derived from $prefix, so "make all; make prefix=/usr14install" would not work.1516The beginning of the Makefile documents many variables that affect the way17git is built. You can override them either from the command line, or in a18config.mak file.1920Alternatively you can use autoconf generated ./configure script to21set up install paths (via config.mak.autogen), so you can write instead2223$ make configure ;# as yourself24$ ./configure --prefix=/usr ;# as yourself25$ make all doc ;# as yourself26# make install install-doc install-html;# as root2728If you're willing to trade off (much) longer build time for a later29faster git you can also do a profile feedback build with3031$ make profile-all32# make prefix=... install3334This will run the complete test suite as training workload and then35rebuild git with the generated profile feedback. This results in a git36which is a few percent faster on CPU intensive workloads. This37may be a good tradeoff for distribution packagers.3839Note that the profile feedback build stage currently generates40a lot of additional compiler warnings.4142Issues of note:4344- Ancient versions of GNU Interactive Tools (pre-4.9.2) installed a45program "git", whose name conflicts with this program. But with46version 4.9.2, after long hiatus without active maintenance (since47around 1997), it changed its name to gnuit and the name conflict is no48longer a problem.4950NOTE: When compiled with backward compatibility option, the GNU51Interactive Tools package still can install "git", but you can build it52with --disable-transition option to avoid this.5354- You can use git after building but without installing if you want55to test drive it. Simply run git found in bin-wrappers directory56in the build directory, or prepend that directory to your $PATH.57This however is less efficient than running an installed git, as58you always need an extra fork+exec to run any git subcommand.5960It is still possible to use git without installing by setting a few61environment variables, which was the way this was done62traditionally. But using git found in bin-wrappers directory in63the build directory is far simpler. As a historical reference, the64old way went like this:6566GIT_EXEC_PATH=`pwd`67PATH=`pwd`:$PATH68GITPERLLIB=`pwd`/perl/blib/lib69export GIT_EXEC_PATH PATH GITPERLLIB7071- Git is reasonably self-sufficient, but does depend on a few external72programs and libraries. Git can be used without most of them by adding73the approriate "NO_<LIBRARY>=YesPlease" to the make command line or74config.mak file.7576- "zlib", the compression library. Git won't build without it.7778- "ssh" is used to push and pull over the net.7980- A POSIX-compliant shell is required to run many scripts needed81for everyday use (e.g. "bisect", "pull").8283- "Perl" version 5.8 or later is needed to use some of the84features (e.g. preparing a partial commit using "git add -i/-p",85interacting with svn repositories with "git svn"). If you can86live without these, use NO_PERL. Note that recent releases of87Redhat/Fedora are reported to ship Perl binary package with some88core modules stripped away (see http://lwn.net/Articles/477234/),89so you might need to install additional packages other than Perl90itself, e.g. Time::HiRes.9192- "openssl" library is used by git-imap-send to use IMAP over SSL.93If you don't need it, use NO_OPENSSL.9495By default, git uses OpenSSL for SHA1 but it will use it's own96library (inspired by Mozilla's) with either NO_OPENSSL or97BLK_SHA1. Also included is a version optimized for PowerPC98(PPC_SHA1).99100- "libcurl" library is used by git-http-fetch and git-fetch. You101might also want the "curl" executable for debugging purposes.102If you do not use http:// or https:// repositories, you do not103have to have them (use NO_CURL).104105- "expat" library; git-http-push uses it for remote lock106management over DAV. Similar to "curl" above, this is optional107(with NO_EXPAT).108109- "wish", the Tcl/Tk windowing shell is used in gitk to show the110history graphically, and in git-gui. If you don't want gitk or111git-gui, you can use NO_TCLTK.112113- A gettext library is used by default for localizing Git. The114primary target is GNU libintl, but the Solaris gettext115implementation also works.116117We need a gettext.h on the system for C code, gettext.sh (or118Solaris gettext(1)) for shell scripts, and libintl-perl for Perl119programs.120121Set NO_GETTEXT to disable localization support and make Git only122use English. Under autoconf the configure script will do this123automatically if it can't find libintl on the system.124125- Some platform specific issues are dealt with Makefile rules,126but depending on your specific installation, you may not127have all the libraries/tools needed, or you may have128necessary libraries at unusual locations. Please look at the129top of the Makefile to see what can be adjusted for your needs.130You can place local settings in config.mak and the Makefile131will include them. Note that config.mak is not distributed;132the name is reserved for local settings.133134- To build and install documentation suite, you need to have135the asciidoc/xmlto toolchain. Because not many people are136inclined to install the tools, the default build target137("make all") does _not_ build them.138139"make doc" builds documentation in man and html formats; there are140also "make man", "make html" and "make info". Note that "make html"141requires asciidoc, but not xmlto. "make man" (and thus make doc)142requires both.143144"make install-doc" installs documentation in man format only; there145are also "make install-man", "make install-html" and "make146install-info".147148Building and installing the info file additionally requires149makeinfo and docbook2X. Version 0.8.3 is known to work.150151Building and installing the pdf file additionally requires152dblatex. Version 0.2.7 with asciidoc >= 8.2.7 is known to work.153154The documentation is written for AsciiDoc 7, but by default155uses some compatibility wrappers to work on AsciiDoc 8. If you have156AsciiDoc 7, try "make ASCIIDOC7=YesPlease".157158There are also "make quick-install-doc", "make quick-install-man"159and "make quick-install-html" which install preformatted man pages160and html documentation. To use these build targets, you need to161clone two separate git-htmldocs and git-manpages repositories next162to the clone of git itself.163164It has been reported that docbook-xsl version 1.72 and 1.73 are165buggy; 1.72 misformats manual pages for callouts, and 1.73 needs166the patch in contrib/patches/docbook-xsl-manpages-charmap.patch167168Users attempting to build the documentation on Cygwin may need to ensure169that the /etc/xml/catalog file looks something like this:170171<?xml version="1.0"?>172<!DOCTYPE catalog PUBLIC173"-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"174"http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"175>176<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">177<rewriteURI178uriStartString = "http://docbook.sourceforge.net/release/xsl/current"179rewritePrefix = "/usr/share/sgml/docbook/xsl-stylesheets"180/>181<rewriteURI182uriStartString="http://www.oasis-open.org/docbook/xml/4.5"183rewritePrefix="/usr/share/sgml/docbook/xml-dtd-4.5"184/>185</catalog>186187This can be achieved with the following two xmlcatalog commands:188189xmlcatalog --noout \190--add rewriteURI \191http://docbook.sourceforge.net/release/xsl/current \192/usr/share/sgml/docbook/xsl-stylesheets \193/etc/xml/catalog194195xmlcatalog --noout \196--add rewriteURI \197http://www.oasis-open.org/docbook/xml/4.5/xsl/current \198/usr/share/sgml/docbook/xml-dtd-4.5 \199/etc/xml/catalog