From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Report from the Buildroot Meeting in Berlin
Date: Fri, 21 Oct 2016 11:05:26 +0200 [thread overview]
Message-ID: <20161021110526.7829792f@free-electrons.com> (raw)
In-Reply-To: <51578cf5-58ba-38ce-6fee-6535784bd150@mind.be>
Hello,
On Fri, 21 Oct 2016 10:57:28 +0200, Arnout Vandecappelle wrote:
> > That being said, what matters to me is that we improve the code to make
> > it clear which flags go in the wrapper and which flags do not. Having a
> > TARGET_WRAPPER_CFLAGS separate from TARGET_EXTRA_CFLAGS will make this
> > very clear, which TARGET_CFLAGS being set to $(TARGET_WRAPPER_CFLAGS)
> > $(TARGET_EXTRA_CFLAGS).
>
> +1 to the naming. Although I think I'll call it TARGET_FLAGS because we will
> use them for LDFLAGS and CXXFLAGS and FCFLAGS as well.
Yes, absolutely. I had forgotten about that, but I continue to agree
with TARGET_FLAGS, which is then used to set all of CFLAGS, CXXFLAGS,
LDFLAGS and FCFLAGS.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-21 9:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 20:10 [Buildroot] Report from the Buildroot Meeting in Berlin Thomas Petazzoni
2016-10-20 16:39 ` Arnout Vandecappelle
2016-10-21 8:25 ` Thomas Petazzoni
2016-10-21 8:57 ` Arnout Vandecappelle
2016-10-21 9:05 ` Thomas Petazzoni [this message]
2016-10-24 12:02 ` Peter Korsgaard
2016-10-24 12:19 ` Vicente Olivert Riera
2016-10-24 12:28 ` Thomas Petazzoni
2016-10-24 13:05 ` Arnout Vandecappelle
2016-10-24 14:52 ` Vicente Olivert Riera
2016-10-24 14:57 ` Thomas Petazzoni
2016-10-24 15:47 ` [Buildroot] Toolchain wrapper CFLAGS [was: Re: Report from the Buildroot Meeting in Berlin] Arnout Vandecappelle
2016-10-24 12:39 ` [Buildroot] Report from the Buildroot Meeting in Berlin Peter Korsgaard
2016-10-24 0:54 ` Sam Bobroff
2016-10-24 7:25 ` Thomas Petazzoni
2016-10-25 2:21 ` Sam Bobroff
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=20161021110526.7829792f@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.