-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Bruno Haible on 1/2/2007 1:55 PM: > Hi, > > Several modules already define a C macro that indicates the presence of the > particular module: > ... > > Some more new modules need the same pattern as well. So I'm adding this > automatic definition of macros to gnulib-tool; the macros will be defined > through config.h.
Sounds reasonable to me. > > In the presence of multiple gnulib-tool invocations from the same directory > with the same configure.ac file, such macros may indicate the wrong thing > (because if you build libgnuA.a and libgnuB.a, the module may be compiled > into libgnuA but not into libgnuB). But I think that judicious use of > library dependencies can avoid most of the problems; and as a last resort, > the remaining problems can be solved by splitting the configure.ac file. What about reusing gnulib-tool --macro-prefix, then using sed to convert GNULIB_ into the correct prefix while copying files into place? Is it worth this level of separation to allow cleaner use of competing gnulib libraries in the same config.h? - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFmzhr84KuGfSFAYARAkbfAKDX0YQBAfI5W3lVhdnisbtjTZtZ4gCfYtiE I+6JDV3LBIMQqQGAPV9yOB8= =OQK5 -----END PGP SIGNATURE-----
