\input texinfo @c -*-texinfo-*-
-@comment $Id: gnulib.texi,v 1.25 2006-07-14 09:32:13 jas Exp $
+@comment $Id: gnulib.texi,v 1.27 2006-09-19 13:42:41 karl Exp $
@comment %**start of header
@setfilename gnulib.info
@settitle GNU Gnulib
@syncodeindex pg cp
@comment %**end of header
-@set UPDATED $Date: 2006-07-14 09:32:13 $
+@set UPDATED $Date: 2006-09-19 13:42:41 $
@copying
This manual is for GNU Gnulib (updated @value{UPDATED}),
@chapter Gnulib
This manual contains some bare-bones documentation, but not much more.
-It's mostly been a place to store notes until someone (you?)@ gets
-around to writing a coherent manual.
+It's mostly a place to store notes until someone (you?)@ gets around
+to writing a coherent manual.
Getting started:
* Regular expressions::
* Windows sockets::
* Libtool and Windows::
+* License Texinfo sources::
@end menu
AC_LIBTOOL_WIN32_DLL
@end example
-in your @file{configure.ac}.
-
-The effect of this is that the names of the @code{OBJDUMP},
-@code{DLLTOOL}, and @code{AS} tools are set up correct.
+in your @file{configure.ac}. This sets the correct names for the
+@code{OBJDUMP}, @code{DLLTOOL}, and @code{AS} tools for the build.
If you are building a library, you will also need to pass
-@code{-no-undefined} to make sure Libtool produce a DLL for your
+@code{-no-undefined} to make sure Libtool produces a DLL for your
library. From a @file{Makefile.am}:
@example
libgsasl_la_LDFLAGS += -no-undefined
@end example
+
+@node License Texinfo sources
+@section License Texinfo sources
+
+Gnulib provides copies of the GNU GPL, GNU LGPL, and GNU FDL licenses
+in Texinfo form. (The master location is
+@url{http://www.gnu.org/licenses/}). These Texinfo documents have
+various node names and structures built into them; for your manual,
+you might like to change these. It's ok to do this, and a convenient
+way to do so is to use a context diff and the @option{--local-dir}
+option to @command{gnulib-tool}.
+
+Of course the license texts themselves should not be changed at all.
+
+
@include gnulib-tool.texi