Hi,

I've been thinking about the macro definitions problem.
I think I've found a more simple solution than what we discussed previously.

The idea would be to keep a config_auto.h.in file, but hand-written, with only the macros that are necessary to have the header compile correctly, and another file, corresponding to the current config_auto.h.in, name config.h, placed in src, auto-generated by configure, and included only in the implementation files.
This way the more problematic macros (PACKAGE, VERSION...) wouldn't pollute the headers.


This could be a temporary solution, easy to do, before completely removing all those macros.

I can try to make a patch if you want.

Regards,

Christophe



Reply via email to