git
/
INSTALL
240 строк · 9.8 Кб
1
2Git installation
3
4Normally 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
7
8$ make prefix=/usr all doc info ;# as yourself
9# make prefix=/usr install install-doc install-html install-info ;# as root
10
11(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.
15
16The 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.
19
20Alternatively you can use autoconf generated ./configure script to
21set up install paths (via config.mak.autogen), so you can write instead
22
23$ 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
27
28If you're willing to trade off (much) longer build time for a later
29faster git you can also do a profile feedback build with
30
31$ make prefix=/usr profile
32# make prefix=/usr PROFILE=BUILD install
33
34This 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.
38
39Alternatively you can run profile feedback only with the git benchmark
40suite. This runs significantly faster than the full test suite, but
41has less coverage:
42
43$ make prefix=/usr profile-fast
44# make prefix=/usr PROFILE=BUILD install
45
46Or if you just want to install a profile-optimized version of git into
47your home directory, you could run:
48
49$ make profile-install
50
51or
52$ make profile-fast-install
53
54As a caveat: a profile-optimized build takes a *lot* longer since the
55git tree must be built twice, and in order for the profiling
56measurements to work properly, ccache must be disabled and the test
57suite has to be run using only a single CPU. In addition, the profile
58feedback build stage currently generates a lot of additional compiler
59warnings.
60
61Issues of note:
62
63- Ancient versions of GNU Interactive Tools (pre-4.9.2) installed a
64program "git", whose name conflicts with this program. But with
65version 4.9.2, after long hiatus without active maintenance (since
66around 1997), it changed its name to gnuit and the name conflict is no
67longer a problem.
68
69NOTE: When compiled with backward compatibility option, the GNU
70Interactive Tools package still can install "git", but you can build it
71with --disable-transition option to avoid this.
72
73- You can use git after building but without installing if you want
74to test drive it. Simply run git found in bin-wrappers directory
75in the build directory, or prepend that directory to your $PATH.
76This however is less efficient than running an installed git, as
77you always need an extra fork+exec to run any git subcommand.
78
79It is still possible to use git without installing by setting a few
80environment variables, which was the way this was done
81traditionally. But using git found in bin-wrappers directory in
82the build directory is far simpler. As a historical reference, the
83old way went like this:
84
85GIT_EXEC_PATH=`pwd`
86PATH=`pwd`:$PATH
87GITPERLLIB=`pwd`/perl/build/lib
88export GIT_EXEC_PATH PATH GITPERLLIB
89
90- By default (unless NO_PERL is provided) Git will ship various perl
91scripts. However, for simplicity it doesn't use the
92ExtUtils::MakeMaker toolchain to decide where to place the perl
93libraries. Depending on the system this can result in the perl
94libraries not being where you'd like them if they're expected to be
95used by things other than Git itself.
96
97Manually supplying a perllibdir prefix should fix this, if this is
98a problem you care about, e.g.:
99
100prefix=/usr perllibdir=/usr/$(/usr/bin/perl -MConfig -wle 'print substr $Config{installsitelib}, 1 + length $Config{siteprefixexp}')
101
102Will result in e.g. perllibdir=/usr/share/perl/5.26.1 on Debian,
103perllibdir=/usr/share/perl5 (which we'd use by default) on CentOS.
104
105- Unless NO_PERL is provided Git will ship various perl libraries it
106needs. Distributors of Git will usually want to set
107NO_PERL_CPAN_FALLBACKS if NO_PERL is not provided to use their own
108copies of the CPAN modules Git needs.
109
110- Git is reasonably self-sufficient, but does depend on a few external
111programs and libraries. Git can be used without most of them by adding
112the appropriate "NO_<LIBRARY>=YesPlease" to the make command line or
113config.mak file.
114
115- "zlib", the compression library. Git won't build without it.
116
117- "ssh" is used to push and pull over the net.
118
119- A POSIX-compliant shell is required to run some scripts needed
120for everyday use (e.g. "bisect", "request-pull").
121
122- "Perl" version 5.8.1 or later is needed to use some of the
123features (e.g. sending patches using "git send-email",
124interacting with svn repositories with "git svn"). If you can
125live without these, use NO_PERL. Note that recent releases of
126Redhat/Fedora are reported to ship Perl binary package with some
127core modules stripped away (see https://lwn.net/Articles/477234/),
128so you might need to install additional packages other than Perl
129itself, e.g. Digest::MD5, File::Spec, File::Temp, Net::Domain,
130Net::SMTP, and Time::HiRes.
131
132- git-imap-send needs the OpenSSL library to talk IMAP over SSL if
133you are using libcurl older than 7.34.0. Otherwise you can use
134NO_OPENSSL without losing git-imap-send.
135
136- "libcurl" library is used for fetching and pushing
137repositories over http:// or https://, as well as by
138git-imap-send if the curl version is >= 7.34.0. If you do
139not need that functionality, use NO_CURL to build without
140it.
141
142Git requires version "7.21.3" or later of "libcurl" to build
143without NO_CURL. This version requirement may be bumped in
144the future.
145
146- "expat" library; git-http-push uses it for remote lock
147management over DAV. Similar to "curl" above, this is optional
148(with NO_EXPAT).
149
150- "wish", the Tcl/Tk windowing shell is used in gitk to show the
151history graphically, and in git-gui. If you don't want gitk or
152git-gui, you can use NO_TCLTK.
153
154- A gettext library is used by default for localizing Git. The
155primary target is GNU libintl, but the Solaris gettext
156implementation also works.
157
158We need a gettext.h on the system for C code, gettext.sh (or
159Solaris gettext(1)) for shell scripts, and libintl-perl for Perl
160programs.
161
162Set NO_GETTEXT to disable localization support and make Git only
163use English. Under autoconf the configure script will do this
164automatically if it can't find libintl on the system.
165
166- Python version 2.7 or later is needed to use the git-p4 interface
167to Perforce.
168
169- Some platform specific issues are dealt with Makefile rules,
170but depending on your specific installation, you may not
171have all the libraries/tools needed, or you may have
172necessary libraries at unusual locations. Please look at the
173top of the Makefile to see what can be adjusted for your needs.
174You can place local settings in config.mak and the Makefile
175will include them. Note that config.mak is not distributed;
176the name is reserved for local settings.
177
178- To build and install documentation suite, you need to have
179the asciidoc/xmlto toolchain. Because not many people are
180inclined to install the tools, the default build target
181("make all") does _not_ build them.
182
183"make doc" builds documentation in man and html formats; there are
184also "make man", "make html" and "make info". Note that "make html"
185requires asciidoc, but not xmlto. "make man" (and thus make doc)
186requires both.
187
188"make install-doc" installs documentation in man format only; there
189are also "make install-man", "make install-html" and "make
190install-info".
191
192Building and installing the info file additionally requires
193makeinfo and docbook2X. Version 0.8.3 is known to work.
194
195Building and installing the pdf file additionally requires
196dblatex. Version >= 0.2.7 is known to work.
197
198All formats require at least asciidoc 8.4.1. Alternatively, you can
199use Asciidoctor (requires Ruby) by passing USE_ASCIIDOCTOR=YesPlease
200to make. You need at least Asciidoctor version 1.5.
201
202There are also "make quick-install-doc", "make quick-install-man"
203and "make quick-install-html" which install preformatted man pages
204and html documentation. To use these build targets, you need to
205clone two separate git-htmldocs and git-manpages repositories next
206to the clone of git itself.
207
208The minimum supported version of docbook-xsl is 1.74.
209
210Users attempting to build the documentation on Cygwin may need to ensure
211that the /etc/xml/catalog file looks something like this:
212
213<?xml version="1.0"?>
214<!DOCTYPE catalog PUBLIC
215"-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
216"http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"
217>
218<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
219<rewriteURI
220uriStartString = "http://docbook.sourceforge.net/release/xsl/current"
221rewritePrefix = "/usr/share/sgml/docbook/xsl-stylesheets"
222/>
223<rewriteURI
224uriStartString="http://www.oasis-open.org/docbook/xml/4.5"
225rewritePrefix="/usr/share/sgml/docbook/xml-dtd-4.5"
226/>
227</catalog>
228
229This can be achieved with the following two xmlcatalog commands:
230
231xmlcatalog --noout \
232--add rewriteURI \
233http://docbook.sourceforge.net/release/xsl/current \
234/usr/share/sgml/docbook/xsl-stylesheets \
235/etc/xml/catalog
236
237xmlcatalog --noout \
238--add rewriteURI \
239http://www.oasis-open.org/docbook/xml/4.5/xsl/current \
240/usr/share/sgml/docbook/xml-dtd-4.5 \
241/etc/xml/catalog
242