Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Where did "project name" go?
Date: Tue, 01 Dec 2009 09:33:12 +0100	[thread overview]
Message-ID: <87zl63gkl3.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <op.u383h9jpyqa4qb@jap> (Joachim Pihl's message of "Tue\, 1 Dec 2009 09\:36\:06 +0100")

>>>>> "Joachim" == Joachim Pihl <jpihl@nevion.com> writes:

Hi,

 Joachim> There is no longer an option "Project name" under target
 Joachim> options. Why was this removed for 2009.11? It seems to me that
 Joachim> some essential functionality is lost due to this when you
 Joachim> target multiple platforms. It seems to me that I have to run
 Joachim> make distclean, then make xconfig, when switching target
 Joachim> configurations for the next target to build cleanly.

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.

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.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-12-01  8:33 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 [this message]
2009-12-01  9:07   ` Joachim Pihl
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=87zl63gkl3.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