Re: AC_DEFINE_DIR in autoconf

so I usually need another header anyway. If config.h has a "#define HAVE_FOO", I'll need to do "#ifndef HAVE_FOO ". I put all these tests in a "system.h" file. In your case, I'd make "system.h" include "" and "datadir.h". -- Leonardo Boiko signature.asc Description: OpenPGP digital signature

Re: SYSCONFDIR: config.h vs. AM_CFLAGS

ed at configure time? AFAIK directory installation variables should only be defined at make time. See ``info Autoconf "Installation Directory Variables"''. Maybe you could use instead a dedicated header, created through the Makefile. See ``info Autoconf "Defining Directo

cross-reference: nobase_include_HEADERS vs. mumbledir; mumble_HEADERS

base_include_HEADERS, and also allow the header directory in $srcdir ($src_headers) to be named something else than the package name. I don't know if all that sounded silly or obvious, but if not, may I suggest a cross-reference from the "An Alternative Approach..." node to the &q

Re: Variable substitution @libexecdir@

ne of the suggestions is substituting through sed at make time, similar to what you did. -- Leonardo Boiko signature.asc Description: OpenPGP digital signature

Re: Clean folders

t could conflict with a possible ``clean-local'' in the Makefile.am. Any ideas? -- Leonardo Boiko signature.asc Description: OpenPGP digital signature

Re: svn copy conflicts with autotools ?

ebian for the autotools-dev Debian package, and that made my life better. I recommend it for anyone interested in this issue. Thank you, Henrique. -- Leonardo Boiko signature.asc Description: OpenPGP digital signature

Re: svn copy conflicts with autotools ?

like "config.guess" are kept in "aux". If a developer wants to compile without using autotools, he should use a distribution tarball (generated by "make dist"), not the subversion sources. It works :) -- Leonardo Boiko signature.asc Description: OpenPGP digital signature

Re: RFC for new FAQ entry: Flag Variables Ordering

D is not from the user. Thus LDADD and LIBADD are entirely different from the *FLAGS variables. Is that correct? It may sound obvious, but I find it confusing =) -- Leonardo Boiko signature.asc Description: OpenPGP digital signature

Re: simple example

Michael Cook wrote: Makefile.am: The usual way to define `CC' is to add `AC_PROG_CC' [...] but what about the others? in particular, automake tells me to add AC_PROC_CC to configure.in, but if i do that, autoconf complains: It's AC_PROG_CC, not AC_PROC_CC ;) ^ -- Leonardo Boiko