From: Steve Calfee <stevecalfee@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot in use
Date: Thu, 17 Mar 2011 10:17:16 -0700 [thread overview]
Message-ID: <4D82421C.9020704@gmail.com> (raw)
In-Reply-To: <1D6034426110564DA0DEA9EE9793B3835815B51A9B@NBE-MBX01.americas.swk.pri>
On 03/17/11 06:53, Heyendal, Carl wrote:
> If starting from scratch, downloading and building 2 Buildroots (one for the toolchain, and the other for the rest of the stuff) sounds reasonable. But refining the notion a bit more, if you have already built the entire Buildroot tree like I have done already, is it possible to break off the toolchain leg of the tree and move it somewhere else. Then of course configure the external toolchain option after that.
>
> /carl
>
I believe that the gcc that you have built has a few built-in paths, so
you cannot just move the compiler stuff to another file tree.
What you can do is the second part of my suggestion, just create another
buildroot tree and point its external toolchain to the one you now have
built. It will leave some garbage in the original tree, but disk space
is pretty cheap. In the new tree you will have faster make clean;
make.... cycles since the external toolchain will not be deleted.
Regards, Steve
next prev parent reply other threads:[~2011-03-17 17:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 16:37 [Buildroot] inittab for Busybox Heyendal, Carl
2011-03-15 17:07 ` Thomas Petazzoni
2011-03-15 17:28 ` Charles Krinke
2011-03-15 18:14 ` Heyendal, Carl
2011-03-15 18:22 ` Thomas Petazzoni
2011-03-15 18:32 ` Heyendal, Carl
2011-03-15 20:05 ` Thomas Petazzoni
2011-03-15 20:10 ` Heyendal, Carl
2011-03-16 16:44 ` [Buildroot] Buildroot in use Steve Calfee
2011-03-16 20:08 ` Heyendal, Carl
2011-03-17 12:14 ` William Wagner
2011-03-17 13:53 ` Heyendal, Carl
2011-03-17 17:17 ` Steve Calfee [this message]
2011-03-17 19:42 ` Heyendal, Carl
2011-03-17 21:50 ` Steve Calfee
2011-03-18 16:03 ` Thomas Petazzoni
2011-03-18 16:02 ` Thomas Petazzoni
2011-03-18 16:01 ` Thomas Petazzoni
2011-03-17 20:21 ` Grant Edwards
2011-03-18 15:59 ` [Buildroot] Xtensa support Thomas Petazzoni
2011-03-21 21:18 ` Piet Delaney
2011-09-20 18:35 ` Thomas Petazzoni
2011-09-21 4:01 ` Marc Gauthier
2011-09-21 6:52 ` Thomas Petazzoni
2011-09-21 8:08 ` Piet Delaney
2011-03-27 19:19 ` [Buildroot] Buildroot in use Michael J. Hammel
2011-03-27 23:58 ` Steve Calfee
2011-03-31 17:13 ` Steve Calfee
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=4D82421C.9020704@gmail.com \
--to=stevecalfee@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox