All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] preserve toolchain
Date: Tue, 14 Sep 2010 18:45:19 +0000 (UTC)	[thread overview]
Message-ID: <i6ofrv$tec$1@dough.gmane.org> (raw)
In-Reply-To: 4C8FBA92.1020006@googlemail.com

On 2010-09-14, Marcus Osdoba <marcus.osdoba@googlemail.com> wrote:

> For a shorter development cycle I like to preserve the toolchain 
> generated by buildroot for the next run.

I used to try to do that, and had many problems with it.  As a result,
I switched to using crosstool-ng to build the toolchain.

> I naivly copied the output/toolchain to some other directory and set
> the toolchain directory in the buildroot config. The bin-directory
> does not include the gcc-binaries. Do I have to create links in the
> bin-directory to the gccs?
>
> Is it possible to take the same toolchain for package build the next 
> time?

I managed to do it, but it required a number of customizations to the
external toolchain makefile, and there were still some minor issues
that required work-arounds in a shell-script that I was using to do
builds.  I eventually gave up and heeded the advice of the
maintainers: now I use crosstool-ng to build my external toolchain.

> Can I recycle the toolchain generated by buildroot?

Using crosstool-ng to build an external toolchain is the normal way of
accomplishing what you want to accomplish.

-- 
Grant Edwards               grant.b.edwards        Yow! Make me look like
                                  at               LINDA RONSTADT again!!
                              gmail.com            

  reply	other threads:[~2010-09-14 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14 18:10 [Buildroot] preserve toolchain Marcus Osdoba
2010-09-14 18:45 ` Grant Edwards [this message]
2010-09-14 19:49   ` Marcus Osdoba

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='i6ofrv$tec$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 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.