bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnulib build/test ?


From: Bruno Haible
Subject: Re: gnulib build/test ?
Date: Wed, 17 May 2017 10:15:23 +0200
User-agent: KMail/5.1.3 (Linux/4.4.0-75-generic; KDE/5.18.0; x86_64; ; )

Hi Tim,

> I put your description with some small amendments into the README.
> Here's the patch.

Thanks for being so pro-active.

-Please see doc/gnulib-readme.texi for basic information about Gnulib.
+Please create and read the docs with
+
+  $ cd doc
+  $ make gnulib.html
+  $ xdg-open gnulib.html
+
+or read the online manual at
+
+  https://www.gnu.org/software/gnulib/manual/gnulib.html

This is OK. Pushed.

+#### Contributor's Quick Start Guide ####

This does not belong in the README. The README is for first-time *users*.
For first-time *contributors*, many GNU packages have a HACKING file,
but gnulib already has a doc section "Contributing to gnulib".

+Note the difference between --dir=../testdir1 and --dir=/tmp/testdir1 : The 
former is on the
+same file system as the gnulib checkout, and uses hard links to the .c and .h 
files; therefore
+for quick edits of only .h and .c files you can do the edits in the testdir

This is not in a state where we could document it: Unfortunately it does not
work with the 'kate' editor (it breaks hard links when saving with backup).
I need to try how it works with symlinks instead.

Bruno




reply via email to

[Prev in Thread] Current Thread [Next in Thread]