On 3/1/10, Simon Josefsson <si...@josefsson.org> wrote: > > It would be nice it gnulib-tool could do it, but I have a hard time > thinking how that would actually be implemented. There are so many > different ways you may want to organize your gnulib directories that > having gnulib-tool support them all is probably going to overload the > poor shell script. Concrete ideas are always welcome, though...
gnulib-tool accepts --source-base and --m4-base as destination for files. it should also accept --source-common and --m4-common which specify the location of modules which are in the "core" of the project, i.e., which can be assumed to be present. So I will write something like: gnulib-tool --source-base=src/gllib --m4-base=src/glm4 foo gnulib-tool --source-common=src/gllib --m4-common=src/glm4 --source-base=modules/syscalls/gllib --m4-base=modules/syscalls/glm4 bar and if bar depends on foo, then foo files will not be added to modules/syscalls/gllib and modules/syscalls/glm4, instead they will be found in src/gllib & src/glm4 by the second invocation of gnulib-tool. -- Sam Steingold <http://sds.podval.org>
