Simon Josefsson wrote: > If you invoke the tool as: > > gnulib-tool --create-testdir --dir=/tmp/testdir regex > > It will create an entire new project in /tmp/testdir for the regex > module. Then you can run it again: > > cd /tmp/testdir > gnulib-tool --import --lgpl regex > > After that, you have the sources in lib/ and the required M4 macros in > gl/. You can copy them somewhere else, but you should call gl_EARLY > early in configure.ac, and gl_INIT later on in your configure.ac.
Additionally, if you really don't want the autogenerated Makefile.am's, you can use the low-level accessors that gnulib-tool offers, namely gnulib-tool --extract-filelist regex gnulib-tool --extract-dependencies regex gnulib-tool --extract-autoconf-snippet regex gnulib-tool --extract-automake-snippet regex and integrate them in your package the way it fits you best. > > Julien PUYDT <[EMAIL PROTECTED]> writes: > >> I just need a posix regex library. Gnulib-tool doesn't seem to > >> permit to just get the sources. gnulib no longer provides just *.h and *.c files. It also provides accompanying *.m4 files, an autoconf snippet, and an automake snippet, for each module. If you don't use the *.m4 files, the autoconf snippet, and the automake snippet, you are very likely to encounter problems. The whole thing - *.h and *.c files, *.m4 files, autoconf snippet, and automake snippet - were designed to fit together. Bruno _______________________________________________ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib
