From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Passing compile flags to every component
Date: Thu, 14 Jun 2012 00:36:59 +0200 [thread overview]
Message-ID: <4FD9160B.9010306@mind.be> (raw)
In-Reply-To: <4FD8FFB1.2010702@cats-muvva.net>
On 06/13/12 23:01, Nicole wrote:
> Sorry if this is a newbie question. Can anyone give me some directions about how to to pass a set of {C{,XX,PP},LD}FLAGS
> to the build of each and every application that will be put on the disk image?
>
[snip]
> BR2_TARGET_OPTIMIZATION="-pipe"
> BR2_TARGET_LDFLAGS=""
Those are the buildroot config options you want to modify.
It's not 100% guaranteed to work for all packages (some packages do explicit
massaging of the CFLAGS passed to them; the Linux kernel is one of them).
For the -mtune=geode flag, specifically, that should be selected automatically
if you choose geode as the sub-architecture.
PS: Please avoid posting a full config - do a 'make savedefconfig' and post the
resulting defconfig file.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-06-13 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 21:01 [Buildroot] Passing compile flags to every component Nicole
2012-06-13 22:36 ` Arnout Vandecappelle [this message]
2012-06-14 7:19 ` Nicole
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=4FD9160B.9010306@mind.be \
--to=arnout@mind.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox