summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff.email>2022-01-08 11:51:39 +0100
committerJörg Frings-Fürst <debian@jff.email>2022-01-08 11:51:39 +0100
commit2959e59fab3bab834368adefd90bd4b1b094366b (patch)
tree7d0ae09775ea950056193eaa2ca93844299d46f1 /HACKING
parentc78359d9542c86b972aac373efcf7bc7a8a560e5 (diff)
parentbe8efac78d067c138ad8dda03df4336e73f94887 (diff)
Update upstream source from tag 'upstream/1.0'
Update to upstream version '1.0' with Debian dir 4875e7dc9f7277205f0086a63ee21ccdb1d54593
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING58
1 files changed, 48 insertions, 10 deletions
diff --git a/HACKING b/HACKING
index 227e003..fa68a87 100644
--- a/HACKING
+++ b/HACKING
@@ -9,31 +9,31 @@ You will need reasonably recent versions of the build tools:
* A C compiler. Such as GNU GCC.
+ Homepage:
- http://gcc.gnu.org/
+ https://gcc.gnu.org/
- * GNU automake
+ * GNU automake 1.16.4 or newer
+ Homepage:
- http://www.gnu.org/software/automake/
+ https://www.gnu.org/software/automake/
* GNU autoconf
+ Homepage:
- http://www.gnu.org/software/autoconf/
+ https://www.gnu.org/software/autoconf/
* GNU m4
+ Homepage:
- http://www.gnu.org/software/m4/
+ https://www.gnu.org/software/m4/
* GNU gperf
+ Homepage:
- http://www.gnu.org/software/gperf/
+ https://www.gnu.org/software/gperf/
* GNU sed
+ Homepage:
- http://www.gnu.org/software/sed/
+ https://www.gnu.org/software/sed/
* Perl
+ Homepage:
- http://www.perl.org/
+ https://www.perl.org/
* Either an internet connection or a recent copy of GNU gnulib.
In order to work with the HEAD of libunistring development, you need the
@@ -44,11 +44,40 @@ You will need reasonably recent versions of the build tools:
particular version of gnulib which is indicated in the GNULIB_GIT_COMMIT
variable in version.sh.
+ Homepage:
- http://www.gnu.org/software/gnulib/
+ https://www.gnu.org/software/gnulib/
And, of course, the packages listed in the DEPENDENCIES file.
-Then you can run the 'autogen.sh' script
+
+Additional requirements for maintainers
+---------------------------------------
+
+If you are a maintainer, you will want to minimize the number of tests that
+are skipped. To this effect, you need to install a couple of locales, used by
+the tests. By default, only those enabled in /etc/locale.gen are preinstalled.
+
+$ sudo localedef -i ar_SA -f ISO-8859-6 ar_SA.ISO-8859-6
+$ sudo localedef -i fr_FR -f ISO-8859-1 fr_FR.ISO-8859-1
+$ sudo localedef -i fr_FR -f UTF-8 fr_FR.UTF-8
+$ sudo localedef -i ja_JP -f EUC-JP ja_JP.EUC-JP
+$ sudo localedef -i zh_CN -f GB18030 zh_CN.GB18030
+
+
+Building off the Git repository
+===============================
+
+Access to the Git repository is described at
+https://savannah.gnu.org/git/?group=libunistring .
+
+After fetching the sources from the Git repository, peek at the comments in
+autogen.sh, then run
+ ./gitsub.sh pull
+ ./autogen.sh
+Then you can proceed with "./configure" as usual.
+
+Each time you want to update the source, do not only "git pull". Instead do
+ git pull && ./gitsub.sh pull
+ ./autogen.sh
Sources
@@ -72,6 +101,15 @@ To speed up the build:
linking and therefore should certainly not be distributed.
+Continuous integration
+======================
+
+The package is built automatically, at regular intervals. You find the latest
+build results here:
+ https://gitlab.com/gnu-libunistring/ci-distcheck/pipelines
+ https://gitlab.com/gnu-libunistring/ci-distcheck/-/jobs?scope=finished
+
+
Running the testsuite in valgrind
=================================