blob: 6e94e3f36ef61ee48f5d75f77d298e951d874fdf (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
All you need to know when hacking (modifying) GNU gettext or when building
it off the git repository.
Requirements
============
You will need reasonably recent versions of the build tools:
* A C compiler; on Cygwin or mingw also a C++ compiler. Such as GNU GCC.
+ Homepage:
http://gcc.gnu.org/
* GNU automake
+ Homepage:
http://www.gnu.org/software/automake/
* GNU autoconf
+ Homepage:
http://www.gnu.org/software/autoconf/
* GNU m4
+ Homepage:
http://www.gnu.org/software/m4/
* GNU bison
+ Homepage:
http://www.gnu.org/software/bison/
* GNU gperf
+ Homepage:
http://www.gnu.org/software/gperf/
* GNU groff 1.17 or newer
+ Homepage:
http://www.gnu.org/software/groff/
* GNU texinfo
+ Homepage:
http://www.gnu.org/software/texinfo/
* GNU emacs or XEmacs
+ Homepage:
http://www.gnu.org/software/emacs/
http://www.xemacs.org/
* Perl
+ Homepage:
http://www.perl.org/
* TeX (for making the doc in .dvi, .ps or .pdf format)
+ Homepage:
http://tug.org/teTeX/
* Either an internet connection or a recent copy of GNU gnulib.
+ Homepage:
http://www.gnu.org/software/gnulib/
* GNU tar (for creating distributable tarballs)
+ Homepage:
http://www.gnu.org/software/tar/
And, of course, the packages listed in the DEPENDENCIES file.
Building off the git repository
===============================
Access to the git repository is described at
http://savannah.gnu.org/git/?group=gettext
After fetching the sources from the repository, peek at the comments in
autogen.sh, then run "./autogen.sh"; then you can proceed with "./configure"
as usual.
|
