qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Ronan Keryell <Ronan.Keryell@enstb.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] CPPFLAGS+= in Makefile.target
Date: Mon, 28 Jan 2008 11:35:00 +0000	[thread overview]
Message-ID: <20080128113500.GA23119@networkno.de> (raw)
In-Reply-To: <87ir1egvtl.fsf@an-dro.enstb.org>

Ronan Keryell wrote:
> >>>>> On Fri, 25 Jan 2008 14:39:57 +0000, Paul Brook <paul@codesourcery.com> said:
> 
>     >> Saying CPPFLAGS+= is much more convenient if for any reason the
>     >> external build environment would like to pass unusual CPPFLAGS.
> 
>     Paul> No. This doesn't do what you thing it does.  The most common way
>     Paul> of overriding these variables is to pass them on the
>     Paul> commandline, i.e. "make CPPFLAGS=-blah". This overrides all
>     Paul> assignments to that variable including +=.
> 
> By the way, it is possible to improve the GNU make weirdness :-) by
> playing with stuff like:
> 
> override CFLAGS += -g
> 
> Cf section 6.7 of the documentation.

IIRC the documentation warns against careless use of overrides.

> Hmmm... GNU make evolves more rapidly than my brain... :-)

It's only a decade old or so. :-)


Thiemo

      reply	other threads:[~2008-01-28 11:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 14:18 [Qemu-devel] [PATCH] CPPFLAGS+= in Makefile.target Ian Jackson
2008-01-25 14:39 ` Paul Brook
2008-01-25 14:44   ` Ian Jackson
2008-01-25 14:48     ` Ian Jackson
2008-01-25 15:36       ` Paul Brook
2008-01-25 15:37         ` Ian Jackson
2008-01-25 15:53           ` Paul Brook
2008-01-25 16:03             ` Ian Jackson
2008-01-25 16:03           ` Paul Brook
2008-01-25 16:12             ` Ian Jackson
2008-01-25 16:22               ` Paul Brook
2008-01-25 16:29                 ` Ian Jackson
2008-01-28  9:09   ` Ronan Keryell
2008-01-28 11:35     ` Thiemo Seufer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080128113500.GA23119@networkno.de \
    --to=ths@networkno.de \
    --cc=Ronan.Keryell@enstb.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).