\input texinfo @c -*-texinfo-*-
-@comment $Id: gnulib.texi,v 1.13 2005-07-16 19:41:33 jas Exp $
+@comment $Id: gnulib.texi,v 1.15 2005-07-30 13:47:19 karl Exp $
@comment %**start of header
@setfilename gnulib.info
@settitle GNU Gnulib
@syncodeindex pg cp
@comment %**end of header
-@set UPDATED $Date: 2005-07-16 19:41:33 $
+@set UPDATED $Date: 2005-07-30 13:47:19 $
@copying
This manual is for GNU Gnulib (updated @value{UPDATED}),
* inet_ntoa::
* Out of memory handling::
* Library version handling::
+* Regular expressions::
@end menu
@end example
+@node Regular expressions
+@section Regular expressions
+
+Gnulib supports many different types of regular expressions; although
+the underlying features are the same or identical, the syntax used
+varies. The descriptions given here for the different types are
+generated automatically.
+
+@include regexprops-generic.texi
+
+
@node Invoking gnulib-tool
@chapter Invoking gnulib-tool
@end example
Finally, you have to add compiler and linker flags in the appropriate
-source directories, so that you can make use
-of the gnulib library. For example:
+source directories, so that you can make use of the gnulib library.
+Since some modules (@samp{getopt}, for example) may copy files into
+the build directory, @file{top_builddir/lib} is needed as well
+as @file{top_srcdir/lib}. For example:
@example
...
-AM_CPPFLAGS = -I$(top_srcdir)/lib
+AM_CPPFLAGS = -I$(top_srcdir)/lib -I$(top_builddir)/lib
...
LIBADD = lib/libgnu.a
...