Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Multiprojects
Date: Tue, 11 Sep 2007 00:14:28 +0200	[thread overview]
Message-ID: <007c01c7f3f8$d4c49340$2d03310a@atmel.com> (raw)
In-Reply-To: D61182AC8012EA4EBC531B3AF23BE1093F12CE@tranzeo-mail2.12stewart.tranzeo.com

----- Original Message ----- 
From: "Darcy Watkins" <DWatkins@tranzeo.com>
To: <buildroot@uclibc.org>
Sent: Monday, September 10, 2007 10:51 PM
Subject: [Buildroot] Multiprojects


> Hello,
> 
> Newbie question here...
> 
> To support multiple projects, I can change the project name using
> menuconfig and save the updated .config.
> 
> If I save them as proj1.config, proj2.config, etc. is there a command
> line option or variable name I can set when invoking make to tell it to
> choose the correct project's file?
> 

Yes, and No ...
I sent in an RFC for such a patch


$ make saveconfig

will save project in 
project/<board>/<board>.config

$ make BOARD=<board> 

will use

project/<board>/<board>.config

instead of 

.config

I am thinking of using another directory than "project" though.

Search the archives for mails from me during the last two weeks.


> ...or do I just have to load up the file into menuconfig and save it as
> .config and then run make for each case?
> 
> Thanks
> 
> Darcy
> 

Best Regards
Ulf Samuelsson

  parent reply	other threads:[~2007-09-10 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10 20:51 [Buildroot] Multiprojects Darcy Watkins
2007-09-10 21:42 ` Roderick Taylor
2007-09-10 22:14 ` Ulf Samuelsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-11 17:47 Darcy Watkins
2007-09-11 21:56 ` Ulf Samuelsson
2007-09-11 18:36 Darcy Watkins

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='007c01c7f3f8$d4c49340$2d03310a@atmel.com' \
    --to=ulf@atmel.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