1 All you need to know when hacking (modifying) GNU libunistring or when building
8 You will need reasonably recent versions of the build tools:
10 * A C compiler. Such as GNU GCC.
14 * GNU automake 1.16.4 or newer
16 https://www.gnu.org/software/automake/
20 https://www.gnu.org/software/autoconf/
24 https://www.gnu.org/software/m4/
28 https://www.gnu.org/software/gperf/
32 https://www.gnu.org/software/sed/
38 * Either an internet connection or a recent copy of GNU gnulib.
39 In order to work with the HEAD of libunistring development, you need the
40 HEAD of the gnulib development.
41 In order to work with the version of libunistring at a given date, you need
42 the version of gnulib of the same date.
43 In order to work with a released tarball of libunistring, you need the
44 particular version of gnulib which is indicated in the GNULIB_GIT_COMMIT
45 variable in version.sh.
47 https://www.gnu.org/software/gnulib/
49 And, of course, the packages listed in the DEPENDENCIES file.
52 Additional requirements for maintainers
53 ---------------------------------------
55 If you are a maintainer, you will want to minimize the number of tests that
56 are skipped. To this effect, you need to install a couple of locales, used by
57 the tests. By default, only those enabled in /etc/locale.gen are preinstalled.
59 $ sudo localedef -i ar_SA -f ISO-8859-6 ar_SA.ISO-8859-6
60 $ sudo localedef -i fr_FR -f ISO-8859-1 fr_FR.ISO-8859-1
61 $ sudo localedef -i fr_FR -f UTF-8 fr_FR.UTF-8
62 $ sudo localedef -i ja_JP -f EUC-JP ja_JP.EUC-JP
63 $ sudo localedef -i zh_CN -f GB18030 zh_CN.GB18030
66 Building off the Git repository
67 ===============================
69 Access to the Git repository is described at
70 https://savannah.gnu.org/git/?group=libunistring .
72 After fetching the sources from the Git repository, peek at the comments in
76 Then you can proceed with "./configure" as usual.
78 Each time you want to update the source, do not only "git pull". Instead do
79 git pull && ./autopull.sh
86 Most of the sources have their origin in gnulib.
92 See the INSTALL file for generic instructions.
94 To speed up the build:
95 1) You can use the configure option --disable-namespacing. The speed up is
96 by a factor of 1.5. The resulting library is not namespace-clean and
97 therefore should not be installed (if you don't want to risk collisions
98 with other libraries) and should certainly not be distributed.
99 2) You can use the configure option --disable-static. The speed up is by
100 a factor of 1.6. The resulting library cannot be used for static
101 linking and therefore should certainly not be distributed.
104 Continuous integration
105 ======================
107 The package is built automatically, at regular intervals. You find the latest
109 https://gitlab.com/gnu-libunistring/ci-distcheck/pipelines
110 https://gitlab.com/gnu-libunistring/ci-distcheck/-/jobs?scope=finished
113 Running the testsuite in valgrind
114 =================================
116 To run the test suite with a memory access checker and leak detector such as
118 1) configure with the options --disable-shared and CFLAGS="-g",
120 3) edit tests/Makefile to uncomment the appropriate definition of the CHECKER