From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] Remove the "project" feature
Date: Tue, 08 Sep 2009 08:58:43 +0200 [thread overview]
Message-ID: <1252393123.11390.5.camel@bender> (raw)
In-Reply-To: <20090908082707.18e19d6e@hcegtvedt.norway.atmel.com>
Hi,
On Tue, 2009-09-08 at 08:27 +0200, Hans-Christian Egtvedt wrote:
> On Tue, 8 Sep 2009 00:09:49 +0200
> Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
>
> > The "project" feature was designed to allow to several projects to be
> > built inside the same Buildroot source tree and allowing the toolchain
> > and non-configurable packages to be shared between the different
> > projects on the same architecture. While being interesting in theory,
> > this feature adds a level of complexity to Buildroot, both from an
> > user perspective and from a developer perspective, while one of the
> > main Buildroot strengh is to be simple. Moreover, this feature is only
> > seldomly used by our users.
> >
>
> I use it all the time ;) How do you propose building for multiple
> targets? I would at least like to share the toolchain, preferably also
> libraries.
Same here. We don't currently use the project feature, but mostly
because we didn't find the time yet to try it. We are building several
targets for the same platform and currently we do a full rebuild for
each target, this includes the toolkit. If there was an easy way to at
least share the tool-chain, then I would welcome if it wasn't removed
from buildroot.
Sven
next prev parent reply other threads:[~2009-09-08 6:58 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 [this message]
2009-09-08 7:07 ` Peter Korsgaard
2009-09-08 7:15 ` Sven Neumann
2009-09-08 7:23 ` Peter Korsgaard
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=1252393123.11390.5.camel@bender \
--to=s.neumann@raumfeld.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