From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] using a variable within a buildroot menuconfig
Date: Sat, 29 Jun 2013 15:44:02 +0200 [thread overview]
Message-ID: <87k3ldxc9p.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CANxTyt5QFrhLW__jV4+HKPGjDvvZwfh9KMcwWP1JK6bpB-oHEA@mail.gmail.com> (Danomi Manchego's message of "Sat, 29 Jun 2013 09:42:15 -0400")
>>>>> "Danomi" == Danomi Manchego <danomimanchego123@gmail.com> writes:
Danomi> On Thu, Jun 27, 2013 at 8:25 AM, Peter Korsgaard?<jacmet@uclibc.org>?wrote:
Danomi> FYI, I'm currently looking at more-or-less the same horror, E.G. the
Danomi> 1.6G ezsdk blob for ti81xx.
Danomi> I too am a victim of the ti81xx EZSDK horror. ?I've been
Danomi> compiling the EZSDK on its own, doing a "make install
Danomi> EXEC_DIR=/some/place", and then using a script to selectively
Danomi> pull stuff out of the created install tree into something like
Danomi> a target skeleton overlay that gets installed into staging as
Danomi> well. ?It works, but stinks for source control. ?(Check in the
Danomi> whole 1.6G, most of which is worthless and takes a long time to
Danomi> compile, or check in the resulting overlay, which feels hacky?)
Yeah, I would like to be able to clean it up enough to get it added to
mainline Buildroot, but I've only now started looking..
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-06-29 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 7:58 [Buildroot] using a variable within a buildroot menuconfig Jan Pohanka
2013-06-25 17:39 ` Arnout Vandecappelle
2013-06-27 12:25 ` Peter Korsgaard
2013-06-29 13:42 ` Danomi Manchego
2013-06-29 13:44 ` Peter Korsgaard [this message]
2013-06-25 19:41 ` Thomas Petazzoni
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=87k3ldxc9p.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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