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.
16 http://www.gnu.org/software/automake/
20 http://www.gnu.org/software/autoconf/
24 http://www.gnu.org/software/m4/
28 http://www.gnu.org/software/gperf/
32 http://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 http://www.gnu.org/software/gnulib/
49 And, of course, the packages listed in the DEPENDENCIES file.
51 Then you can run the 'autogen.sh' script
57 Most of the sources have their origin in gnulib.
63 See the INSTALL file for generic instructions.
65 To speed up the build:
66 1) You can use the configure option --disable-namespacing. The speed up is
67 by a factor of 1.5. The resulting library is not namespace-clean and
68 therefore should not be installed (if you don't want to risk collisions
69 with other libraries) and should certainly not be distributed.
70 2) You can use the configure option --disable-static. The speed up is by
71 a factor of 1.6. The resulting library cannot be used for static
72 linking and therefore should certainly not be distributed.
75 Running the testsuite in valgrind
76 =================================
78 To run the test suite with a memory access checker and leak detector such as
80 1) configure with the options --disable-shared and CFLAGS="-g",
82 3) edit tests/Makefile to uncomment the appropriate definition of the CHECKER