12
Git installation
34
Normally you can just do "make" followed by "make install", and that
5will install the git programs in your own ~/bin/ directory. If you want
6to do a global install, you can do
78
$ make prefix=/usr all doc info ;# as yourself
9# make prefix=/usr install install-doc install-html install-info ;# as root
1011
(or prefix=/usr/local, of course). Just like any program suite
12that uses $prefix, the built results have some paths encoded,
13which are derived from $prefix, so "make all; make prefix=/usr
14install" would not work.
1516
The beginning of the Makefile documents many variables that affect the way
17git is built. You can override them either from the command line, or in a
18config.mak file.
1920
Alternatively you can use autoconf generated ./configure script to
21set up install paths (via config.mak.autogen), so you can write instead
2223
$ make configure ;# as yourself
24$ ./configure --prefix=/usr ;# as yourself
25$ make all doc ;# as yourself
26# make install install-doc install-html;# as root
2728
If you're willing to trade off (much) longer build time for a later
29faster git you can also do a profile feedback build with
3031
$ make profile-all
32# make prefix=... install
3334
This will run the complete test suite as training workload and then
35rebuild git with the generated profile feedback. This results in a git
36which is a few percent faster on CPU intensive workloads. This
37may be a good tradeoff for distribution packagers.
3839
Note that the profile feedback build stage currently generates
40a lot of additional compiler warnings.
4142
Issues of note:
4344
- Ancient versions of GNU Interactive Tools (pre-4.9.2) installed a
45program "git", whose name conflicts with this program. But with
46version 4.9.2, after long hiatus without active maintenance (since
47around 1997), it changed its name to gnuit and the name conflict is no
48longer a problem.
4950
NOTE: When compiled with backward compatibility option, the GNU
51Interactive Tools package still can install "git", but you can build it
52with --disable-transition option to avoid this.
5354
- You can use git after building but without installing if you want
55to test drive it. Simply run git found in bin-wrappers directory
56in the build directory, or prepend that directory to your $PATH.
57This however is less efficient than running an installed git, as
58you always need an extra fork+exec to run any git subcommand.
5960
It is still possible to use git without installing by setting a few
61environment variables, which was the way this was done
62traditionally. But using git found in bin-wrappers directory in
63the build directory is far simpler. As a historical reference, the
64old way went like this:
6566
GIT_EXEC_PATH=`pwd`
67PATH=`pwd`:$PATH
68GITPERLLIB=`pwd`/perl/blib/lib
69export GIT_EXEC_PATH PATH GITPERLLIB
7071
- Git is reasonably self-sufficient, but does depend on a few external
72programs and libraries. Git can be used without most of them by adding
73the approriate "NO_<LIBRARY>=YesPlease" to the make command line or
74config.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 needed
81for everyday use (e.g. "bisect", "pull").
8283
- "Perl" version 5.8 or later is needed to use some of the
84features (e.g. preparing a partial commit using "git add -i/-p",
85interacting with svn repositories with "git svn"). If you can
86live without these, use NO_PERL.
8788
- "openssl" library is used by git-imap-send to use IMAP over SSL.
89If you don't need it, use NO_OPENSSL.
9091
By default, git uses OpenSSL for SHA1 but it will use it's own
92library (inspired by Mozilla's) with either NO_OPENSSL or
93BLK_SHA1. Also included is a version optimized for PowerPC
94(PPC_SHA1).
9596
- "libcurl" library is used by git-http-fetch and git-fetch. You
97might also want the "curl" executable for debugging purposes.
98If you do not use http:// or https:// repositories, you do not
99have to have them (use NO_CURL).
100101
- "expat" library; git-http-push uses it for remote lock
102management over DAV. Similar to "curl" above, this is optional
103(with NO_EXPAT).
104105
- "wish", the Tcl/Tk windowing shell is used in gitk to show the
106history graphically, and in git-gui. If you don't want gitk or
107git-gui, you can use NO_TCLTK.
108109
- A gettext library is used by default for localizing Git. The
110primary target is GNU libintl, but the Solaris gettext
111implementation also works.
112113
We need a gettext.h on the system for C code, gettext.sh (or
114Solaris gettext(1)) for shell scripts, and libintl-perl for Perl
115programs.
116117
Set NO_GETTEXT to disable localization support and make Git only
118use English. Under autoconf the configure script will do this
119automatically if it can't find libintl on the system.
120121
- Some platform specific issues are dealt with Makefile rules,
122but depending on your specific installation, you may not
123have all the libraries/tools needed, or you may have
124necessary libraries at unusual locations. Please look at the
125top of the Makefile to see what can be adjusted for your needs.
126You can place local settings in config.mak and the Makefile
127will include them. Note that config.mak is not distributed;
128the name is reserved for local settings.
129130
- To build and install documentation suite, you need to have
131the asciidoc/xmlto toolchain. Because not many people are
132inclined to install the tools, the default build target
133("make all") does _not_ build them.
134135
"make doc" builds documentation in man and html formats; there are
136also "make man", "make html" and "make info". Note that "make html"
137requires asciidoc, but not xmlto. "make man" (and thus make doc)
138requires both.
139140
"make install-doc" installs documentation in man format only; there
141are also "make install-man", "make install-html" and "make
142install-info".
143144
Building and installing the info file additionally requires
145makeinfo and docbook2X. Version 0.8.3 is known to work.
146147
Building and installing the pdf file additionally requires
148dblatex. Version 0.2.7 with asciidoc >= 8.2.7 is known to work.
149150
The documentation is written for AsciiDoc 7, but by default
151uses some compatibility wrappers to work on AsciiDoc 8. If you have
152AsciiDoc 7, try "make ASCIIDOC7=YesPlease".
153154
There are also "make quick-install-doc", "make quick-install-man"
155and "make quick-install-html" which install preformatted man pages
156and html documentation. To use these build targets, you need to
157clone two separate git-htmldocs and git-manpages repositories next
158to the clone of git itself.
159160
It has been reported that docbook-xsl version 1.72 and 1.73 are
161buggy; 1.72 misformats manual pages for callouts, and 1.73 needs
162the patch in contrib/patches/docbook-xsl-manpages-charmap.patch
163164
Users attempting to build the documentation on Cygwin may need to ensure
165that the /etc/xml/catalog file looks something like this:
166167
<?xml version="1.0"?>
168<!DOCTYPE catalog PUBLIC
169"-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
170"http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"
171>
172<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
173<rewriteURI
174uriStartString = "http://docbook.sourceforge.net/release/xsl/current"
175rewritePrefix = "/usr/share/sgml/docbook/xsl-stylesheets"
176/>
177<rewriteURI
178uriStartString="http://www.oasis-open.org/docbook/xml/4.5"
179rewritePrefix="/usr/share/sgml/docbook/xml-dtd-4.5"
180/>
181</catalog>
182183
This can be achieved with the following two xmlcatalog commands:
184185
xmlcatalog --noout \
186--add rewriteURI \
187http://docbook.sourceforge.net/release/xsl/current \
188/usr/share/sgml/docbook/xsl-stylesheets \
189/etc/xml/catalog
190191
xmlcatalog --noout \
192--add rewriteURI \
193http://www.oasis-open.org/docbook/xml/4.5/xsl/current \
194/usr/share/sgml/docbook/xml-dtd-4.5 \
195/etc/xml/catalog