Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] using a variable within a buildroot menuconfig
Date: Thu, 27 Jun 2013 14:25:55 +0200	[thread overview]
Message-ID: <87txkj3fl8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <51C9D5C5.4090409@mind.be> (Arnout Vandecappelle's message of "Tue, 25 Jun 2013 19:39:17 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

Hi,

 >> I know that it is not very nice way, but I need to integrate buildroot
 >> with Texas Instruments SDK, which is not very GNU build tools friendy.

 Arnout>  I wonder what you mean with the TI SDK. You probably mean you have to
 Arnout> use _some packages_ that are in the 700MB self-extractor, right?
 Arnout> Because the SDK itself is in fact a replacement for buildroot (or
 Arnout> buildroot is a replacement for the SDK, depending on how you want to
 Arnout> look at it :-).

 Arnout>  Getting that stuff to work is absolute horror, I can testify. I did
 Arnout> that a year and a half ago for the DM365 multimedia codecs, but I
 Arnout> never found a reasonable solution to extract and build individual
 Arnout> packages.

FYI, I'm currently looking at more-or-less the same horror, E.G. the
1.6G ezsdk blob for ti81xx.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-06-27 12:25 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 [this message]
2013-06-29 13:42     ` Danomi Manchego
2013-06-29 13:44       ` Peter Korsgaard
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=87txkj3fl8.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