From: Steve Calfee <stevecalfee@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot in use
Date: Thu, 17 Mar 2011 14:50:03 -0700 [thread overview]
Message-ID: <4D82820B.4010600@gmail.com> (raw)
In-Reply-To: <1D6034426110564DA0DEA9EE9793B3835815BCC604@NBE-MBX01.americas.swk.pri>
On 03/17/11 12:42, Heyendal, Carl wrote:
> Makes sense.
>
> Another thing I have noticed that is frustrating is that a 'make clean' acts more like 'make distclean' and therefore you lose any configuration changes you have previously made.
>
> As a work around, can I copy the relevant .configs before the 'make clean' and add them back once the rebuild is complete (assumed that I need to delete the .stamp_compiled files as well)?
>
> /carl h.
>
Hi Carl,
Please don't top post and trim stuff after your message.
Yes, "make clean" destroys buildroot's .config. I have a "bsp" type
directory with stuff specifically for the project I am working on. I do
a sym-link from configs/beagleboard_defconfig to my bsp config. Then
after a make clean I do a "make beagleboard_defconfig" to copy in my
saved configuration. I also put the linux and u-boot and whatever
configs in my bsp and point to the appropriate config in the buildroot
.config. Dont forget to update your bsp config whenever you change
buildroot with a make menuconfig.
Regards, Steve
next prev parent reply other threads:[~2011-03-17 21:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 16:37 [Buildroot] inittab for Busybox Heyendal, Carl
2011-03-15 17:07 ` Thomas Petazzoni
2011-03-15 17:28 ` Charles Krinke
2011-03-15 18:14 ` Heyendal, Carl
2011-03-15 18:22 ` Thomas Petazzoni
2011-03-15 18:32 ` Heyendal, Carl
2011-03-15 20:05 ` Thomas Petazzoni
2011-03-15 20:10 ` Heyendal, Carl
2011-03-16 16:44 ` [Buildroot] Buildroot in use Steve Calfee
2011-03-16 20:08 ` Heyendal, Carl
2011-03-17 12:14 ` William Wagner
2011-03-17 13:53 ` Heyendal, Carl
2011-03-17 17:17 ` Steve Calfee
2011-03-17 19:42 ` Heyendal, Carl
2011-03-17 21:50 ` Steve Calfee [this message]
2011-03-18 16:03 ` Thomas Petazzoni
2011-03-18 16:02 ` Thomas Petazzoni
2011-03-18 16:01 ` Thomas Petazzoni
2011-03-17 20:21 ` Grant Edwards
2011-03-18 15:59 ` [Buildroot] Xtensa support Thomas Petazzoni
2011-03-21 21:18 ` Piet Delaney
2011-09-20 18:35 ` Thomas Petazzoni
2011-09-21 4:01 ` Marc Gauthier
2011-09-21 6:52 ` Thomas Petazzoni
2011-09-21 8:08 ` Piet Delaney
2011-03-27 19:19 ` [Buildroot] Buildroot in use Michael J. Hammel
2011-03-27 23:58 ` Steve Calfee
2011-03-31 17:13 ` Steve Calfee
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=4D82820B.4010600@gmail.com \
--to=stevecalfee@gmail.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