Bruno Haible <[EMAIL PROTECTED]> writes: > This setup just won't work in the long run.(*) If you use multiple gnulib-tool > invocations, you also need multiple configure files. > > Two setups that will work are: > 1) Completely separate directories for the two gnulib-tool invocations, > Neither of the two will use the other directory.
I'm using this in GNU SASL, but it has other disadvantages -- e.g., autoreconf+configure takes even longer, and making static libraries is impossible due to colliding gnulib symbols -- so I'm trying to defer making this change for as long as I can. It is not clear to me that the current problems (e.g., none reported) are worse than the solution. > 2) The GPLed directory can use the LGPLed directory through -I and -L > options. But you have to ensure that the GPL'ed config.h starts out with > #include "../lgl/config.h" > to include the other config.h first. In this case you can use the --avoid > option to drop redundant modules from the GPLed directory. I have tried variations of this before, but always ran into some problem, e.g., the GPL module AC_REQUIRE some LGPL module that runs AC_LIBOBJ or similar that fails in a split setup. It would be useful if gnulib-tool would be able to do something more intelligent here, but I don't know what it should be. /Simon
