Re: AC_DEFINE_DIR in autoconf (was: Re: SYSCONFDIR: config.h vs. AM_CFLAGS)

2005-03-11 Thread Stepan Kasal
On Wed, Mar 09, 2005 at 08:06:18PM +0100, Baurjan Ismagulov wrote: > What I don't understand is why the manual states that AC_DEFINE_DIR does > not conform with GNU codings standards. > > If I define DATADIR in CPPFLAGS, it is hard-coded into the binary, and > the user can override the prefix duri

Re: AC_DEFINE_DIR in autoconf

2005-03-09 Thread ibr
On Wed, Mar 09, 2005 at 05:55:48PM -0400, Leonardo Boiko wrote: > I don't want to talk about the GNU conformance because I have the same > doubts as you :) but as for having a single file, I often have to > do lots of tests of things defined in config.h, so I usually need > another header anyway.

Re: AC_DEFINE_DIR in autoconf

2005-03-09 Thread Leonardo Boiko
Baurjan Ismagulov wrote: I would ideally prefer to have a single configuration file, namely, config.h. I don't want to talk about the GNU conformance because I have the same doubts as you :) but as for having a single file, I often have to do lots of tests of things defined in config.h, so I usual

AC_DEFINE_DIR in autoconf (was: Re: SYSCONFDIR: config.h vs. AM_CFLAGS)

2005-03-09 Thread Baurjan Ismagulov
[Taking the discussion to the autoconf list.] On Mon, Mar 07, 2005 at 09:57:31AM -0400, Leonardo Boiko wrote: > Isn't config.h created at configure time? AFAIK directory installation > variables should only be defined at make time. See > ``info Autoconf "Installation Directory Variables"''. I ha