From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Building only toolchain
Date: Fri, 29 May 2009 09:45:23 +0200 [thread overview]
Message-ID: <87k5405p4c.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <330EC2471BF24E48B513AF1A6975EB699D04B5@MAIL-UA.ccs.local> (Teemu Keskinarkaus's message of "Fri\, 29 May 2009 07\:25\:19 +0200")
>>>>> "Teemu" == Teemu Keskinarkaus <Teemu.Keskinarkaus@cc-systems.com> writes:
Teemu> Hi,
Teemu> Is it possible to build only toolchain in buildroot? I tried
Teemu> to search the makefiles, but I couldn?t find a target that
Teemu> would do it.
Sure, simply don't select and packages and no file systems, then it
will only build the toolchain.
Teemu> It seems that there are some absolute paths stored in
Teemu> buildroot toolchain binaries(at least ccache has) so I can?t
Teemu> just copy them to another system. Or can the toolchain be
Teemu> built somehow that it doesn?t store any local information
Teemu> there?
Yes, the BR output is in general not relocatable.
Teemu> I don?t want to build whole system, but just applications so
Teemu> only toolchain is needed and not the whole buildroot. I also
Teemu> like to use the same toolchain that was used in buildroot to
Teemu> prevent any problems that might come from using different
Teemu> toolchain.
No problem, as long as you don't move the toolchain around. We often
build pure toolchains with STAGING_DIR set to something like
/opt/cross/${DATE}, which can then simply be added to the path and
used.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-05-29 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 5:25 [Buildroot] Building only toolchain Teemu Keskinarkaus
2009-05-29 7:21 ` Bjørn Forsman
2009-05-29 15:15 ` Thomas Petazzoni
2009-05-29 7:45 ` Peter Korsgaard [this message]
2009-05-29 12:02 ` Teemu Keskinarkaus
2009-05-29 14:13 ` Peter Korsgaard
2009-05-29 8:53 ` Bernhard Reutner-Fischer
2009-06-01 4:17 ` Teemu Keskinarkaus
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=87k5405p4c.fsf@macbook.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 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.