Hi all,
I'm definitely not an expert in automake/autoconf stuff, but it looks to me
like the code in source forge doesn't use the acconfig.h at all.
http://cvs.sourceforge.net/viewcvs.py/fam/fam/configure.ac?annotate=1.1#8
this line (#8) looks to me like it comments out the only usage of acconfig.h
my understanding of acconfig.h is that it is meant to generate config.h.in.
That is, autoheader will use /usr/local/share/autoconf/acconfig.h (or other
appropriate location) as the basis for the new config.h.in. It will scan
configure.ac looking for things to define, and then it will append anything
in acconfig.h to the end of the new config.h.in.
since we seem to be maintaining config.h.in directly, is there any purpose
in maintaining acconfig.h as well?
thanks
dave
|