2 @section Building gnulib
4 If you wish to help the gnulib development effort with build logs for
5 your favorite platform, you may perform these steps:
9 @item Prerequisites tools
11 Install the proper development tools. To build and test all of
12 Gnulib, you will need development tools for the programming languages
13 C, C++, Python, and Perl, along with standard POSIX utilities such
14 as @command{awk}, @command{make}, and @command{sh}. You will also need
15 development tools that include Autoconf, Automake, Bison, Gettext,
16 Git, GNU M4, Gperf, Libtool, and Texinfo. Some of these tools are
17 needed only by some modules. More details can be found in Gnulib's
18 @file{DEPENDENCIES} file.
22 See @url{https://www.gnu.org/software/gnulib/} for how to get the
23 current Gnulib sources via Git.
25 @item Create gnulib directory
27 On a machine with GNU development tools installed and with a gnulib
31 gnulib-tool --create-testdir --with-tests --dir=...
34 Alternatively, pick a small set of modules and run
37 gnulib-tool --create-megatestdir --with-tests --dir=... autobuild MODULES
41 (You can't do this with all of Gnulib at once: @code{gnulib-tool} would run
42 for a week and produce a directory that takes more than 100 GB, maybe even 1 TB,
45 @item Transfer gnulib directory
47 Transfer this directory to a build machine (HP-UX, Cygwin, or
48 whatever). Often it is easier to transfer one file, and this can be
49 achieved by running, inside the directory the following commands:
56 And then transferring the @file{dummy-0.tar.gz} file.
60 On the build machine, run ./do-autobuild (or "nohup ./do-autobuild").
61 It creates a directory @file{logs/} with a log file for each module.