On Jun 15, 2001, "Steve M. Robbins" <[EMAIL PROTECTED]> wrote:
> I normally want the program-specific flags _in addition_ to the
> generic flags. So I *always* have $(LDADD) in $foo_LDADD.
But consider the case of not wanting $(LDADD) in foo_LDADD. Or
consider cases in which the order matters,
On Thu, Jun 14, 2001 at 06:51:09PM -0600, Tom Tromey wrote:
> > "Steve" == Steve M Robbins <[EMAIL PROTECTED]> writes:
>
> Steve> Given the following Makefile.am
> Steve>bin_PROGRAMS = foo
> Steve>foo_SOURCES = foo.c sub/foo2.c
> Steve> it turns out that "foo.c" is compiled us
> "Steve" == Steve M Robbins <[EMAIL PROTECTED]> writes:
Steve> The upshot is that "foo.c" is compiled using AM_CFLAGS but NOT
Steve> foo_CFLAGS, while "foo2.c" is compiled NOT using AM_CFLAGS but using
Steve> foo_CFLAGS.
I'm checking in a fix for this.
Tom
> "Steve" == Steve M Robbins <[EMAIL PROTECTED]> writes:
Steve> Given the following Makefile.am
Steve> bin_PROGRAMS = foo
Steve> foo_SOURCES = foo.c sub/foo2.c
Steve> it turns out that "foo.c" is compiled using $(COMPILE), and hence
Steve> includes AM_CFLAGS. However, "foo2.c" is compiled
Hi,
I'm quite confused by the behaviour of CVS automake and AM_CFLAGS.
Given the following Makefile.am
bin_PROGRAMS = foo
foo_SOURCES = foo.c sub/foo2.c
it turns out that "foo.c" is compiled using $(COMPILE), and hence
includes AM_CFLAGS. However, "foo2.c" is compiled *without
