Bruno Haible <br...@clisp.org> writes: > Simon Josefsson wrote: >> No, I just invoke 'gnulib-tool --import' once in the top-level >> directory. Gnulib-tool notices the gnulib directories beneath lib/ as >> well, and will import files to lib/. ... >> >> How do I stop gnulib-tool from importing gnulib files in lib/, so I can >> invoke gnulib-tool a second time in that directory? > > You do this by specifying "gnulib-tool --m4-base=... --import".
This will require several gnulib-tool invocations in some projects, but I guess I can write a script to do it. > gnulib-tool searches for all gnulib directories only when no --m4-base > option was specified. That is what caused this problem -- what do you think about making gnulib-tool avoid automatically adding gnulib directories under any directory with a configure.ac? Perhaps it can be combined with gnulib-tool recognizing AC_CONFIG_SUBDIRS and invoking gnulib-tool from these sub-directories. But maybe it is too fragile? /Simon
