Bruno Haible <[EMAIL PROTECTED]> writes:
> I would love to replace
>
> DEFS += -DLIBDIR=\"$(libdir)\"
>
> with
>
> localcharset_CPPFLAGS = $(AM_CPPFLAGS) -DLIBDIR=\"$(libdir)\"
That would certainly be an improvement, but it sounds like a bit of a
pain to manage all the foo_CPPFLAGS vari
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> Hello Bruno, Mark,
>
> * 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($e
Ralf Wildenhues wrote:
> > 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
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
> > wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> Hello Bruno,
>
> * Bruno Haible wrote on Fri, Aug 25, 2006 at 03:07:26PM CEST:
> >
> > I would love to replace
> >
> > DEFS += -DLIBDIR=\"$(libdir)\"
> >
> > with
> >
> > localcharset_CPPFLA
Hello Bruno,
* Bruno Haible wrote on Fri, Aug 25, 2006 at 03:07:26PM CEST:
>
> I would love to replace
>
> DEFS += -DLIBDIR=\"$(libdir)\"
>
> with
>
> localcharset_CPPFLAGS = $(AM_CPPFLAGS) -DLIBDIR=\"$(libdir)\"
>
> but does automake support per-object-file settings?
No. You can
Paul Eggert wrote:
> Currently, in-place builds for coreutils generte output that looks
> like this:
>
> gcc -std=gnu99 -DHAVE_CONFIG_H -DLIBDIR=\"/usr/local/lib\" -I. -I. -I.
> -g -O2 -c allocsa.c
> gcc -std=gnu99 -DHAVE_CONFIG_H -DLIBDIR=\"/usr/local/lib\" -I. -I. -I.
> -g -O2 -c bas
