From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Standalone toolchain
Date: Wed, 24 Sep 2008 15:46:35 +0200 [thread overview]
Message-ID: <20080924134635.GA14882@mx.loc> (raw)
In-Reply-To: <48DA3D47.5060204@cetrtapot.si>
On Wed, Sep 24, 2008 at 03:14:47PM +0200, Hinko Kocevar wrote:
>Hi,
>
>Is it possible to create a toolchain and then transfer it to another machine or just another folder, and have it work?
This is supposed to work, yes. The keyword is sysroot support.
Either configure your BR2_STAGING_DIR to e.g. /opt/my-target-tripplet
or just move the staging dir wherever you want and use the proper
--sysroot and -isysroot.
>
>I've experienced the case where I only transferred staging_dir and put it somewhere and when I tried compiling some software compiler was lacking some header files. Creating absolute path link to newly created toolchain dir to point to staging_dir where it was taken from solved the problem..
next prev parent reply other threads:[~2008-09-24 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 13:14 [Buildroot] Standalone toolchain Hinko Kocevar
2008-09-24 13:46 ` Bernhard Reutner-Fischer [this message]
2008-09-26 12:39 ` Hinko Kocevar
2008-09-29 8:49 ` Hinko Kocevar
2008-09-29 9:05 ` Hinko Kocevar
2008-09-29 10:57 ` Hinko Kocevar
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=20080924134635.GA14882@mx.loc \
--to=rep.dot.nop@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