Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] using of local dir
Date: Thu, 27 Mar 2008 06:14:17 +0100	[thread overview]
Message-ID: <006901c88fc9$c232b280$070514ac@atmel.com> (raw)
In-Reply-To: 20080327025740.GB5036@cloud.net.au

> On Wed, Mar 26, 2008 at 09:12:03PM +0100, Peter Korsgaard wrote:
>> Well, the local/save/getconfig stuff does seem kinda overengineered -
>> Couldn't we just have a bunch of *_defconfig files under configs/
>> instead with a make %_defconfig target like the kernel has instead?
> 
> As long as you can have several projects built within the same tree. I'm
> using the projects functionality to have several related projects built
> this way.
> 

That is its intended use.

> Mind you I don't like using getconfig/saveconfig; too prone to losing
> changes if you forget to saveconfig. Instead I use "make BOARD=xyz .."
> each time. I will sometime send some patches to improve this method.
> 

The stuff is used to generate the files needed by "make BOARD=xyz"
If you have no need to change the configs after that,then
you can use the BOARD=xyz after that.
Once you think it is frozen, you can submit a new board.

What do you want to change?

> Hamish
> -- 
> Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
> _______________________________________________




Best Regards
Ulf Samuelsson

      reply	other threads:[~2008-03-27  5:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 17:59 [Buildroot] using of local dir Dittmann, Daniel
2008-03-26 18:09 ` Bernhard Fischer
2008-03-26 20:12   ` Peter Korsgaard
2008-03-26 20:36     ` Ulf Samuelsson
2008-03-26 21:41       ` Peter Korsgaard
2008-03-27  2:57     ` Hamish Moffatt
2008-03-27  5:14       ` Ulf Samuelsson [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='006901c88fc9$c232b280$070514ac@atmel.com' \
    --to=ulf.samuelsson@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