[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: compilation flags per object file

From: Ralf Wildenhues
Subject: Re: compilation flags per object file
Date: Fri, 25 Aug 2006 18:27:27 +0200
User-agent: Mutt/1.5.12 (2006-08-10)

Hello Bruno, Mark,

* Bruno Haible wrote on Fri, Aug 25, 2006 at 03:53:35PM CEST:
> Ralf Wildenhues wrote:
> > You should note that object file
> > names are an internal Automake detail, so the naming of the respective
> > *_CPPFLAGS variable is not clear, for starters.  Above would conflict
> > with a program named localcharset.
> I wouldn't mind if the specification were per source file:
>   localcharset_c_CPPFLAGS = $(AM_CPPFLAGS) -DLIBDIR=\"$(libdir)\"

That's a possibility, but it runs contrary of the notion of per-target
flags.  More than one object may be created from one source file.

* Mark D. Baushke wrote on Fri, Aug 25, 2006 at 06:01:03PM CEST:
> There should be no ambiguity if you add the $(ext) to the
> makefile macro name:
> localcharset.o_CPPFLAGS = $(AM_CPPFLAGS) -DLIBDIR=\"$(libdir)\"
> and then use $($*$(ext)_CPPDFLAGS) in rules that need it.

It would be so nice, except that IRIX make doesn't grok it:
| UX:make: ERROR: Unmatched closing curly braces or parenthesis in line 
|         $(FOO_$*).

I wonder whether that is the only `make' which has problems with this...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]