Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment
Date: Tue, 26 Jun 2012 15:48:14 +0000 (UTC)	[thread overview]
Message-ID: <jsclju$7qc$1@dough.gmane.org> (raw)
In-Reply-To: 20120626171906.5ea51e6a@skate

On 2012-06-26, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Le Tue, 26 Jun 2012 17:05:59 +0200,
> Aleksandar Zivkovic <Aleksandar.Zivkovic@rt-rk.com> a ??crit :
>
>> I'm trying to extract the toolchain generated by Buildroot in order to 
>> use it on other machines without Buildroot environment. Thought this is 
>> simple and did the following way:
>> * generate toolchain outside Buildroot (BR2_HOST_DIR="$(TOPDIR)/../host")
>> * use files from $(TOPDIR)/../host on other machine
>
> Did you install them at the exact same location on the other machine?
>
> For the moment, the toolchains generated by Buildroot are not
> relocatable, so they must be installed on the other machine at the
> same location they were generated on the initial build machine.

Toolchains built with crosstool-ng can be moved anywhere, but all you
end up with is the basic "libc" libraries.  You'll have to copy the
libraries built by buildroot manually if you want to use them on the
other hosts.

-- 
Grant Edwards               grant.b.edwards        Yow! The PILLSBURY DOUGHBOY
                                  at               is CRYING for an END to
                              gmail.com            BURT REYNOLDS movies!!

  reply	other threads:[~2012-06-26 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 15:05 [Buildroot] Using Buildroot generated toolchain on different machine without Buildroot environment Aleksandar Zivkovic
2012-06-26 15:19 ` Thomas Petazzoni
2012-06-26 15:48   ` Grant Edwards [this message]
2012-06-26 15:58     ` Thomas Petazzoni
2012-06-27 22:03       ` Aleksandar Zivkovic

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='jsclju$7qc$1@dough.gmane.org' \
    --to=grant.b.edwards@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