From: Joachim Pihl <jpihl@nevion.com>
To: buildroot@busybox.net
Subject: [Buildroot] Where did "project name" go?
Date: Tue, 1 Dec 2009 10:07:56 +0100 [thread overview]
Message-ID: <op.u384zil4yqa4qb@jap> (raw)
In-Reply-To: <87zl63gkl3.fsf@macbook.be.48ers.dk>
On Tue, 01 Dec 2009 09:33:12 +0100, Peter Korsgaard <jacmet@uclibc.org>
wrote:
> Are you refererring to the project_build_<arch>/<project> stuff, that
> could be used to build variants of a given arch/platform? That was
> removed as part of the cleanup work, as it's a fairly specialized setup
> and it added a lot of confusion / complexity to the system.
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.
> You can use an external toolchain to atleast not need to rebuild the
> toolchain (typically the slowest thing to build).
>
> Notice that you can use the O=<path> make argument to put the output
> files somewhere else than ouput, which can be handy when you build for
> several boards from the same tree.
>
> See
> http://git.buildroot.net/buildroot/commit/?id=3b2a803d2842e45a28b58afde6835dc40edb4c52
> for more details.
>
Will look into it.
--
Joachim Pihl
Senior R&D Engineer
Nevion Europe
Tel: +47 33 48 94 66
Fax: +47 33 48 99 98
Mobile: +47 91 33 98 91
jpihl at nevion.com
www.nevion.com
------------------------------------------------------
The Global Video Transport Leader
------------------------------------------------------
next prev parent reply other threads:[~2009-12-01 9:07 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 [this message]
2009-12-01 13:42 ` Thomas Petazzoni
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=op.u384zil4yqa4qb@jap \
--to=jpihl@nevion.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