1 All you need to know when hacking (modifying) GNU gettext or when building
2 it off the git repository.
8 You will need reasonably recent versions of the build tools:
10 * A C compiler; on Cygwin or mingw also a C++ compiler. Such as GNU GCC.
14 * GNU automake 1.13 or newer
16 https://www.gnu.org/software/automake/
20 https://www.gnu.org/software/autoconf/
24 https://www.gnu.org/software/m4/
26 * GNU bison 3.0 or newer
28 https://www.gnu.org/software/bison/
32 https://www.gnu.org/software/gperf/
34 * GNU groff 1.17 or newer
36 https://www.gnu.org/software/groff/
40 https://www.gnu.org/software/texinfo/
44 https://www.gnu.org/software/emacs/
45 https://www.xemacs.org/
51 * TeX (for making the doc in .dvi, .ps or .pdf format)
53 https://tug.org/teTeX/
55 * Either an internet connection or a recent copy of GNU gnulib.
57 https://www.gnu.org/software/gnulib/
59 * GNU tar (for creating distributable tarballs)
61 https://www.gnu.org/software/tar/
65 https://www.gnu.org/software/wget/
69 https://tukaani.org/xz/
73 https://www.nongnu.org/lzip/
75 And, of course, the packages listed in the DEPENDENCIES file.
78 Additional requirements for maintainers
79 ---------------------------------------
81 If you are a maintainer, you will want to minimize the number of tests that
82 are skipped. To this effect, you need to install also:
85 + Homepage: https://gcc.gnu.org/
87 * An Objective C compiler
88 + Homepage: https://gcc.gnu.org/
89 + Ubuntu package: gobjc
92 + Homepage: https://www.python.org/
93 + Ubuntu package: python
96 + Homepage: http://clisp.org/
97 + Ubuntu package: clisp
100 + Homepage: http://librep.sourceforge.net/
101 + Ubuntu package: rep
104 + Homepage: https://www.gnu.org/software/guile/
105 + Ubuntu package: guile-2.0
108 + Homepage: http://smalltalk.gnu.org/
109 + Ubuntu package: gnu-smalltalk
112 + Homepage: http://openjdk.java.net/
113 + Ubuntu package: default-jdk
116 + Homepage: https://www.mono-project.com/
117 + Ubuntu package: mono-mcs
120 + Homepage: https://www.gnu.org/software/gawk/
121 + Ubuntu package: gawk
123 * The Free Pascal compiler ppc386 or ppcx64
124 + Homepage: https://www.freepascal.org/
125 + Ubuntu package: fp-compiler
126 * The Free Pascal Free Component Library
127 + Homepage: https://www.freepascal.org/fcl/fcl.var
128 + Ubuntu package: fp-units-fcl
131 + Homepage: https://www.tcl.tk/
132 + Ubuntu package: tcl
135 + Homepage: https://www.perl.org/
136 + Ubuntu package: perl
137 * The Perl packages Locale::Messages and libintl-perl
138 + Homepage: http://search.cpan.org/~guido/libintl-perl/
139 + Ubuntu package: libintl-perl
142 + Homepage: http://www.php.net/
143 + Ubuntu package: php
146 + Homepage: https://www.lua.org/
147 + Ubuntu package: lua5.2 or lua5.1
148 * The lua-gettext package
149 + Homepage: https://gitlab.com/sukhichev/lua-gettext/blob/master/README.us.md
150 + Debian and Ubuntu packages:
151 Download, then install through
152 $ sudo dpkg -i lua-gettext_0.0_amd64.deb
154 * The GNOME/Mozilla JavaScript interpreter
155 + Homepage: https://wiki.gnome.org/Projects/Gjs
156 + Ubuntu packages: gjs gir1.2-gtk-3.0
158 * The GNOME Vala compiler
159 + Homepage: https://wiki.gnome.org/Projects/Vala
160 + Ubuntu package: valac
162 If you want to exercise the sample programs in gettext-tools/examples/, you
163 also need to install:
165 * The Qt GUI toolkit library
166 + Homepage: https://www.qt.io/
167 + Ubuntu package: libqt4-dev
169 * The wxWidgets GUI toolkit library
170 + Homepage: https://www.wxwidgets.org/
171 + Ubuntu package: libwxgtk3.0-dev
173 * The GNUstep toolkit and development environment
174 + Homepage: http://www.gnustep.org/
175 * Ubuntu package: gnustep-devel
177 * The C# System.Windows.Forms implementation
178 + Homepage: https://www.mono-project.com/
179 + Ubuntu package: libmono-system-windows-forms4.0-cil
181 And you need to install a couple of locales, used by the tests.
182 By default, only those enabled in /etc/locale.gen are preinstalled.
184 $ sudo localedef -i de_DE -f ISO-8859-1 de_DE.ISO-8859-1
185 $ sudo localedef -i de_DE -f UTF-8 de_DE.UTF-8
186 $ sudo localedef -i fa_IR -f UTF-8 fa_IR
187 $ sudo localedef -i fr_FR -f ISO-8859-1 fr_FR.ISO-8859-1
188 $ sudo localedef -i fr_FR -f UTF-8 fr_FR.UTF-8
189 $ sudo localedef -i ja_JP -f EUC-JP ja_JP.EUC-JP
190 $ sudo localedef -i tr_TR -f UTF-8 tr_TR.UTF-8
191 $ sudo localedef -i zh_CN -f GB18030 zh_CN.GB18030
194 Building off the Git repository
195 ===============================
197 Access to the Git repository is described at
198 https://savannah.gnu.org/git/?group=gettext .
200 After fetching the sources from the Git repository, peek at the comments in
204 Then you can proceed with "./configure" as usual.
206 Each time you want to update the source, do not only "git pull". Instead do
207 git pull && ./gitsub.sh pull
214 Patches should be sent to bug-gettext@gnu.org, the bug/feature mailing
215 list. You can subscribe to the mailing list, or see the list
216 archives, by following links from
217 https://savannah.gnu.org/mail/?group=gettext .
219 To email a patch you can use a shell command like 'git format-patch
220 -1' to create a file, and then attach the file to your email.
222 GNU gettext development no longer stores descriptions of new changes
223 in ChangeLog files. Instead, a single ChangeLog file is generated
224 from the commit messages when a release is prepared. So changes you
225 commit should not touch any of the ChangeLog files in the repository,
226 but instead should contain the log entries in the commit message.
228 For the style of a ChangeLog entry, see the "Change Logs" section of
229 the GNU coding standards:
231 https://www.gnu.org/prep/standards/html_node/Change-Logs.html