In the e16 case above config.h.in is generated from configure.in without any acconfig.h being involved.On Friday, 09 January 2004, at 19:40:56 (+0100), Kim Woelders wrote:
Quoting config.h.in for e16 generated on RH-7.2 (auto{conf,header}-2.13):
"/* config.h.in. Generated automatically from configure.in by autoheader. */"
In my experience, things that aren't in the default autoheader files don't end up in config.h.in unless they're in acconfig.h. In fact, you get errors instead.
config.h.in is autogenerated from acconfig.h *and* configure.in.
I believe it does require that the third parameter to AC_DEFINE is used, as in
AC_DEFINE(USE_IMLIB2, 1, [Imlib2 support])
which is just what Ibokun suggested.
/Kim
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
