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