Re: Suggestion: AC_DEFINE -> m4_pattern_allow

2006-05-31 Thread Akim Demaille
Le 31 mai 06 à 18:38, Stepan Kasal a écrit : Hello, * Akim Demaille wrote on Wed, May 31, 2006 at 04:26:17PM CEST: I suggest that Automake provide the same feature for AM_CONDITIONAL: well, you already implemented it, granting Alexandre one point for his hint: http://lists.gnu.org/archive

Re: Noobie question about doing "src" dirs

2006-05-31 Thread Thomas Dickey
On Wed, 31 May 2006, Stepan Kasal wrote: Hello, On Wed, May 31, 2006 at 12:14:28PM -0700, Douglas Phillipson wrote: The autoconf tutorial states that either a configure.ac or a configure.in can be used initially. What is the difference and why would you use the configure.ac over the configure

Re: Noobie question about doing "src" dirs

2006-05-31 Thread Stepan Kasal
Hello, On Wed, May 31, 2006 at 12:27:42PM -0700, Douglas Phillipson wrote: > You no longer need these anymore?? > > AC_INIT(src/hello.c) > AM_INIT_AUTOMAKE(hello,1.1) > AC_PROG_CC > AC_PROG_INSTALL Of course you do. We were not just speaking about the tail of configure.ac; you start with AC_INI

Re: Noobie question about doing "src" dirs

2006-05-31 Thread Douglas Phillipson
Harlan Stenn wrote: configure.in is the old name, configure.ac is the new name. I prefer: AC_CONFIG_FILES(Makefile) AC_CONFIG_FILES(src/Makefile) AC_OUTPUT and run 'autoreconf -vfi'. H You no longer need these anymore?? AC_INIT(src/hello.c) AM_INIT_AUTOMAKE(hello,1.1) AC_PROG_CC AC_

Re: Noobie question about doing "src" dirs

2006-05-31 Thread Stepan Kasal
Hi, On Wed, May 31, 2006 at 07:21:34PM +, Harlan Stenn wrote: > I prefer: > > AC_CONFIG_FILES(Makefile) > AC_CONFIG_FILES(src/Makefile) > AC_OUTPUT others prefer AC_CONFIG_FILES([ Makefile src/Makefile ]) AC_OUTPUT Stepan

Re: Noobie question about doing "src" dirs

2006-05-31 Thread Stepan Kasal
Hello, On Wed, May 31, 2006 at 12:14:28PM -0700, Douglas Phillipson wrote: > The autoconf tutorial states that either a configure.ac or a > configure.in can be used initially. What is the difference and why > would you use the configure.ac over the configure.in? the only difference is that con

Re: Noobie question about doing "src" dirs

2006-05-31 Thread Harlan Stenn
configure.in is the old name, configure.ac is the new name. I prefer: AC_CONFIG_FILES(Makefile) AC_CONFIG_FILES(src/Makefile) AC_OUTPUT and run 'autoreconf -vfi'. H

Re: Noobie question about doing "src" dirs

2006-05-31 Thread Douglas Phillipson
Tyler MacDonald wrote: Douglas Phillipson <[EMAIL PROTECTED]> wrote: I have: Makefile.am: SUBDIRS = srcbin_PROGRAMS = hello Those two should not be on the same line :-) It's creating the Makefile.in in the "src" dir, but not the top level dir. What Am I doing wrong? Everything else look

Re: Noobie question about doing "src" dirs

2006-05-31 Thread Douglas Phillipson
Tyler MacDonald wrote: Douglas Phillipson <[EMAIL PROTECTED]> wrote: I have: Makefile.am: SUBDIRS = srcbin_PROGRAMS = hello Those two should not be on the same line :-) It's creating the Makefile.in in the "src" dir, but not the top level dir. What Am I doing wrong? Everything else look

Re: Noobie question about doing "src" dirs

2006-05-31 Thread Tyler MacDonald
Douglas Phillipson <[EMAIL PROTECTED]> wrote: > I have: > Makefile.am: > SUBDIRS = srcbin_PROGRAMS = hello Those two should not be on the same line :-) > It's creating the Makefile.in in the "src" dir, but not the top level > dir. What Am I doing wrong? Everything else looks good!

Re: Noobie question about doing "src" dirs

2006-05-31 Thread Douglas Phillipson
Tyler MacDonald wrote: Douglas Phillipson <[EMAIL PROTECTED]> wrote: SUBDIRS = src My top level configure.in: AC_INIT(src/hello.c) AM_INIT_AUTOMAKE(hello,1.1) AC_PROG_CC AC_PROG_INSTALL AC_OUTPUT(Makefile src/Makefile) What else needs to go in src? and What should it contain? Yo

Re: Suggestion: AC_DEFINE -> m4_pattern_allow

2006-05-31 Thread Stepan Kasal
Hello, > * Akim Demaille wrote on Wed, May 31, 2006 at 04:26:17PM CEST: > > I suggest that Automake provide the same feature for AM_CONDITIONAL: well, you already implemented it, granting Alexandre one point for his hint: http://lists.gnu.org/archive/html//bug-automake/2004-12/msg00090.html http

Re: Suggestion: AC_DEFINE -> m4_pattern_allow

2006-05-31 Thread Ralf Wildenhues
Hi Akim, * Akim Demaille wrote on Wed, May 31, 2006 at 04:26:17PM CEST: > >>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes: > > Some time ago I sent this message for which I had no answer. > > I suggest that the AC_DEFINE family explicitly allow its $1. Not true, your request has been de

Re: Suggestion: AC_DEFINE -> m4_pattern_allow

2006-05-31 Thread Akim Demaille
>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes: Hi! Some time ago I sent this message for which I had no answer. > I have this package at hand, say FooBar, which installs a prefixed > form of config.h. Its own macros are, of course, named FB_*, which is > m4_pattern_forbidden. But t

Re: Compilation flags and variables

2006-05-31 Thread Ralf Wildenhues
Hi Guillaume, * Guillaume Rousse wrote on Wed, May 31, 2006 at 10:38:42AM CEST: > I read the automake and autoconf manual several times, but I'm still a > bit uncertain at how to manage compilation flags properly, meaning: > - which flags to use > - where to use them You're going from specialized

Compilation flags and variables

2006-05-31 Thread Guillaume Rousse
I read the automake and autoconf manual several times, but I'm still a bit uncertain at how to manage compilation flags properly, meaning: - which flags to use - where to use them First, you have per-primary targets options (discarding non-C language ones): foo_CPPFLAGS foo_CFLAGS foo_(LIBADD|LDA