Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] Remove the "project" feature
Date: Tue, 08 Sep 2009 09:23:26 +0200	[thread overview]
Message-ID: <87d461528h.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1252394155.13520.2.camel@bender> (Sven Neumann's message of "Tue\, 08 Sep 2009 09\:15\:55 +0200")

>>>>> "Sven" == Sven Neumann <s.neumann@raumfeld.com> writes:

Hi,

 >> We have that already with the external toolchain support. I also don't
 >> use it yet (we're doing like you), but will start to use it soon.

 Sven> So how would I go about reusing the buildroot supplied tool-chain
 Sven> for multiple targets? I imagine that one basic target would build
 Sven> the tool-chain and the other targets would then use that as their
 Sven> external tool-chain? Could you give an example or a quick
 Sven> introduction on how to set this up? Or just point me to the docs
 Sven> if I just missed that such documentation exists. That would be
 Sven> much appreciated.

Yes, something like that. Have you read
http://buildroot.net/buildroot.html#external_toolchain ? As I said
before, I haven't actually used it yet, maybe Thomas can fill in the
blanks?

It might be an idea to get the toolchain build to write out a .config
snippet that can get included when using it to ensure we have the
various toolchain settings correct.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-09-08  7:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 22:09 [Buildroot] [RFC] [PATCH 0/5] Buildroot cleanup Thomas Petazzoni
2009-09-07 22:09 ` [Buildroot] [PATCH 1/5] Remove the "project" feature Thomas Petazzoni
2009-09-08  6:27   ` Hans-Christian Egtvedt
2009-09-08  6:58     ` Sven Neumann
2009-09-08  7:07       ` Peter Korsgaard
2009-09-08  7:15         ` Sven Neumann
2009-09-08  7:23           ` Peter Korsgaard [this message]
2009-09-08  7:31             ` Thomas Petazzoni
2009-09-08  7:43               ` Peter Korsgaard
2009-09-08  7:49                 ` Thomas Petazzoni
2009-09-08  6:59     ` Peter Korsgaard
2009-09-08  7:16     ` Thomas Petazzoni
2009-09-08  7:06   ` Peter Korsgaard
     [not found]     ` <20090908092408.787e9cf7@surf>
2009-09-08  7:31       ` Peter Korsgaard
2009-09-07 22:09 ` [Buildroot] [PATCH 2/5] Remove the BOARD/LOCAL feature Thomas Petazzoni
2009-09-07 22:09 ` [Buildroot] [PATCH 3/5] By default, put the output in an output/ directory Thomas Petazzoni
2009-09-09 10:19   ` Peter Korsgaard
2009-09-09 11:28     ` Thomas Petazzoni
2009-09-07 22:09 ` [Buildroot] [PATCH 4/5] Remove BR2_TOPDIR_PREFIX and BR2_TOPDIR_SUFFIX Thomas Petazzoni
2009-09-09 17:35   ` Bernhard Reutner-Fischer
2009-09-10  6:30     ` Thomas Petazzoni
2009-09-10  7:33       ` Peter Korsgaard
2009-09-07 22:09 ` [Buildroot] [PATCH 5/5] Rename the output directories Thomas Petazzoni
2009-09-09  7:02   ` Peter Korsgaard
2009-09-09  7:22     ` Thomas Petazzoni
2009-09-09  7:37       ` Peter Korsgaard
2009-09-08 17:03 ` [Buildroot] [RFC] [PATCH 0/5] Buildroot cleanup Will Newton
2009-09-08 19:13   ` Jonathan dumaresq
2009-09-08 21:20   ` Peter Korsgaard
2009-09-09  9:36     ` Will Newton

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=87d461528h.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox