From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] add pre-build script
Date: Thu, 14 Feb 2013 08:56:04 +0100 [thread overview]
Message-ID: <20130214085604.52619b06@skate> (raw)
In-Reply-To: <CAEBucnA1BebDBHWb4PcQBGiUpyiAcT0=vs3Tu4D+LVw1YdN0_A@mail.gmail.com>
Dear Spenser Gilliland,
On Wed, 13 Feb 2013 19:04:30 -0600, Spenser Gilliland wrote:
> I have a use case for this. In Microblaze builds, it would be nice to
> generate optimal cflags from the dts/mhs for use in all software.
> This could be accomplished by a pre script.
Do you have the example of pre-build script that does this? Changing
the CFLAGS requires changing some internal Buildroot make variables, so
I'm not sure how you're doing this from a pre-build script.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-14 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 13:54 [Buildroot] [PATCH] add pre-build script Joe Halpin
2013-02-13 22:24 ` Arnout Vandecappelle
2013-02-14 1:04 ` Spenser Gilliland
2013-02-14 7:56 ` Thomas Petazzoni [this message]
2013-02-14 16:28 ` Spenser Gilliland
2013-02-14 17:04 ` Thomas Petazzoni
2013-02-14 22:10 ` Arnout Vandecappelle
2013-02-15 5:09 ` Thomas Petazzoni
2013-02-15 20:50 ` Spenser Gilliland
[not found] ` <05255DE50A102443A25D42F2CCAC151FA58C27@LUMEXCH.luminatorusa.com>
[not found] ` <511CF47A.7050004@mind.be>
2013-02-14 14:29 ` [Buildroot] [PATCH] add pre-build script. Patch v2 Joe Halpin
2013-02-14 15:08 ` [Buildroot] [PATCH] add pre-build scrip. Patch V2 Joe Halpin
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=20130214085604.52619b06@skate \
--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.