From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Not Using Saved Config for Linux
Date: Tue, 06 Jan 2009 19:31:48 +0100 [thread overview]
Message-ID: <1231266708.32308.211.camel@elrond.atmel.com> (raw)
In-Reply-To: <BAY124-W25B0802FB150D5566BD194D2E10@phx.gbl>
m?n 2009-01-05 klockan 15:11 -0800 skrev Quick X:
> I can't get buildroot to use the "local\MYPROJECT
> \linux-2.6.24.3.config" file no matter what. It always uses the
> "project_build_arm/at91sam9261ek/linux-2.6.24.3/.config" file, or
> creates a new one if it doesn't exsist.
>
> Steps I do to test:
> make linux26-menuconfig
> make saveconfig
> make linux26-menuconfig (EDIT SOMETHING ELSE)
> make BOARD=MYPROJECT
>
IIRC, The way saveconfig works is that it copies the current
$(TOPDIR)/.config to the loacl/$(PROJECT) directory
and then edits the paths for certain variables.
It does not modify the ?$(TOPDIR)/.config file,so you
will still be using the same paths.
If you want to use the new board stuff, you have to to
$ make BOARD=MYPROJECT getconfig
which do:
cp $(LOCAL)/$(PROJECT)/$(PROJECT).config .config
and after that, you should be using the BOARD files.
Note that you can set BUILDROOT_LOCAL to whatever in
your shell environment so you can store your project
files outside the buildroot source tree.
Best Regards
Ulf Samuelsson.
next prev parent reply other threads:[~2009-01-06 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 23:11 [Buildroot] Buildroot Not Using Saved Config for Linux Quick X
2009-01-06 1:34 ` [Buildroot] Cups compile problem Daniel
2009-01-06 4:24 ` [Buildroot] _Cups_compile_problem Daniel
2009-01-06 18:31 ` Ulf Samuelsson [this message]
2009-01-06 20:40 ` [Buildroot] Buildroot Not Using Saved Config for Linux Quick X
2009-01-06 22:43 ` Quick X
2009-01-07 10:30 ` Ulf Samuelsson
2009-01-07 20:51 ` Quick X
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=1231266708.32308.211.camel@elrond.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