What about the danger of the compile lines becoming too long (i.e.,
exceeding a system limit) eventually?
Greg Hudson <ghudson@MIT.EDU> writes:
> Karl wrote, in a commit log:
> > Put -I../.. into include path, and #include "config.h".
>
> I usually eschew config.h and let my compile lines become long,
> because using config.h means you have to maintain an acconfig.h, add
> the top-level build directory to the include path, and run autoheader
> when you make changes to configure.in. Better to have a simple build
> system with mildly ugly output than a complicated build system with
> pretty output, in my opinion. But this is not a strong opinion.
>
> > Note: I don't see any reason to conditionalize the include, as in
>
> I don't understand why the examples do that either. Just leave @DEFS@
> out of the Makefile.in and #include "config.h" unconditionally;
> there's no reason to do otherwise.
Received on Sat Oct 21 14:36:14 2006