From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] multiple architectures
Date: Wed, 30 Sep 2009 10:31:37 +0200 [thread overview]
Message-ID: <20090930103137.304aa012@surf> (raw)
In-Reply-To: <5f2b60909300113o53ef97b7j6910562af6ebb8be@mail.gmail.com>
Le Wed, 30 Sep 2009 10:13:22 +0200,
Bj?rn Forsman <bjorn.forsman@gmail.com> a ?crit :
> How about that the default BR output directory contains an arch
> postfix? This would eliminate the need for manually setting O=
> according to the current .config. Instead it would happen
> automatically.
This was the case previously. But I don't think it's a good idea, since
it only solves partially the problem: what if you have several
projects, but all these projects use the same architecture ?
This is even more common than multiple architectures projects: you work
on ARM (for example), but you build different filesystems for different
usages of the device. In that case, a default output-arm/ directory
would not solve the problem.
A possibility would be to add a configuration option to set the output
directory path, instead of passing O=. I don't have a strong opinion on
this, but I'd prefer not to have both solutions. The fact that
Buildroot has multiple solutions to do approximately the same thing is
a large part of the confusion for our new users, and I would like to
reduce this confusion.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-09-30 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 6:26 [Buildroot] multiple architectures Igor Serebryany
2009-09-30 7:01 ` Thomas Petazzoni
2009-09-30 7:26 ` Igor Serebryany
2009-09-30 8:13 ` Bjørn Forsman
2009-09-30 8:31 ` Thomas Petazzoni [this message]
2009-09-30 9:08 ` Peter Korsgaard
2009-09-30 10:20 ` Bjørn Forsman
2009-09-30 11:44 ` Peter Korsgaard
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=20090930103137.304aa012@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 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.