Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001568]: "make BOARD=xyz menuconfig"/	oldconfig etc does not work
Date: Thu, 13 Dec 2007 21:28:56 +0100	[thread overview]
Message-ID: <028301c83dd2$66d59900$dcc4af0a@atmel.com> (raw)
In-Reply-To: 20071211062833.GA8833@cloud.net.au

> I mean no offense when I ask, is project support well-supported by the
> buildroot community over all? Is it your work originally Ulf with little
> support from the others? Some things like the above don't work as I
> expect them, so it feels a bit rough. In the case of my patch in this
> bug report, you could apply it and make me happy without any detriment
> to the way you work (with getconfig/saveconfig).
> 

No, you destroy the original intent by making certain things depend
on the stuff in local/<proj>/*.config

We do not depend on the different "defconfigs" as well.
We copy them to .config and then we depend on .config

A good way to fix your problem could be to have a 

make BOARD=xyz reconfig

which would 

* make BOARD=$(BOARD) getconfig
* make menuconfig
* make saveconfig

Best Regards
Ulf Samuelsson

  reply	other threads:[~2007-12-13 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 21:28 [Buildroot] [buildroot 0001568]: "make BOARD=xyz menuconfig" / oldconfig etc does not work bugs at busybox.net
2007-12-11  6:28 ` Hamish Moffatt
2007-12-13 20:28   ` Ulf Samuelsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-02  1:02 bugs at busybox.net
2007-11-01  5:52 bugs at busybox.net

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='028301c83dd2$66d59900$dcc4af0a@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