From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001568]: "make BOARD=xyz menuconfig" / oldconfig etc does not work
Date: Tue, 27 Nov 2007 13:28:49 -0800 [thread overview]
Message-ID: <b55faafb87f5cc5a7566708c821671b2@busybox.net> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=1568
======================================================================
Reported By: hmoffatt
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1568
Category: Other
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 10-31-2007 22:52 PDT
Last Modified: 11-27-2007 13:28 PST
======================================================================
Summary: "make BOARD=xyz menuconfig" / oldconfig etc does not
work
Description:
buildroot allows you to do "make BOARD=xyz world" to compile using the
configuration file in local/xyz/xyz.config, but you can't call menuconfig,
oldconfig etc in this way.
The problem is that the name of the configuration file isn't being passed
to the kconfig tool (package/config/conf). kconfig uses $BUILDROOT_CONFIG,
so all that is needed is to set that environment variable.
Patch attached fixes this so that "make BOARD=xyz oldconfig" works.
======================================================================
----------------------------------------------------------------------
hmoffatt - 11-01-07 18:02
----------------------------------------------------------------------
"make BOARD=xyz world" also fails due to a few more hard-coded references
to .config. br2-board-config2.diff fixes those.
----------------------------------------------------------------------
UlfSamuelsson - 11-27-07 13:28
----------------------------------------------------------------------
Once you have a ".config" file, you can store your board configuration by:
$ make saveconfig
This will store the .config for buildroot, linux, uclibc and busybox.
If the project name is "xyz", then they will be stored in the "local/xyz"
You can retrieve your configuration by:
$ make BOARD=xyz getconfig
It is wrong to make the things depend on BUILDROOT_CONFIG.
They should depend on ".config"
Issue History
Date Modified Username Field Change
======================================================================
10-31-07 22:52 hmoffatt New Issue
10-31-07 22:52 hmoffatt Status new => assigned
10-31-07 22:52 hmoffatt Assigned To => buildroot
10-31-07 22:52 hmoffatt File Added: br-board-config.diff
11-01-07 18:01 hmoffatt File Added: br-board-config2.diff
11-01-07 18:02 hmoffatt Note Added: 0002885
11-27-07 13:28 UlfSamuelsson Note Added: 0002977
======================================================================
next reply other threads:[~2007-11-27 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 21:28 bugs at busybox.net [this message]
2007-12-11 6:28 ` [Buildroot] [buildroot 0001568]: "make BOARD=xyz menuconfig" / oldconfig etc does not work Hamish Moffatt
2007-12-13 20:28 ` [Buildroot] [buildroot 0001568]: "make BOARD=xyz menuconfig"/ " Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2007-11-02 1:02 [Buildroot] [buildroot 0001568]: "make BOARD=xyz menuconfig" / " 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=b55faafb87f5cc5a7566708c821671b2@busybox.net \
--to=bugs@busybox.net \
--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