From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Where did "project name" go?
Date: Tue, 1 Dec 2009 14:42:00 +0100 [thread overview]
Message-ID: <20091201144200.7ef450f0@surf> (raw)
In-Reply-To: <op.u384zil4yqa4qb@jap>
Le Tue, 1 Dec 2009 10:07:56 +0100,
Joachim Pihl <jpihl@nevion.com> a ?crit :
> That is the part I was referring to. It does make building the same
> system for multiple targets easy (from a user perspective), though,
> and that is now lost. I guess I'm just not the average user.
The solution for this, as mentionned by Peter, is to build out-of-tree
using O=/path/to/output/directory.
Then you can easily switch between several projects without problem.
They share the same Buildroot source code, but they have different
configurations and different output directories.
The old "project" stuff was just duplicating this feature. We had to
make a choice between both, and the choice of O= was the one that
allowed to make simplifications in Buildroot that make it much easier
to use for less advanced users.
Don't hesitate to ask if you have any question or find any limitation
with the O= scheme.
Sincerly,
Thomas.
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2009-12-01 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 8:36 [Buildroot] Where did "project name" go? Joachim Pihl
2009-12-01 8:33 ` Peter Korsgaard
2009-12-01 9:07 ` Joachim Pihl
2009-12-01 13:42 ` Thomas Petazzoni [this message]
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=20091201144200.7ef450f0@surf \
--to=thomas.petazzoni@free-electrons.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