Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] How to handle modularity in buildroot?
Date: Wed, 05 Dec 2012 18:14:24 +0100	[thread overview]
Message-ID: <50BF80F0.8050603@mind.be> (raw)
In-Reply-To: <CAE21AQp9tsnrS=uR0BoOuYi15Vew=swx24FapMC7Fyi+W0E3+A@mail.gmail.com>

On 04/12/12 19:18, Charles Manning wrote:
>> >  And then, when you want to do a production build:
>> >
>> >    make clean
>> >    cat mysystem_base_defconfig.frag mysystem_prod_defconfig.frag>  configs/mysystem_prod_defconfig
>> >    make mysystem_prod_defconfig
>> >    make
>> >
>> >  And when you want to do a development build:
>> >
>> >    make clean
>> >    cat mysystem_base_defconfig.frag mysystem_dev_defconfig.frag>  configs/mysystem_dev_defconfig
>> >    make mysystem_dev_defconfig
>> >    make
>> >
>> >  Basically, instead of having Buildroot providing this feature, we rely
>> >  on the simple manipulation of the configuration file.
> This sounds like the right idea.
>
> I will experiment with this a bit and see where it takes me. If there
> is something worth sharing I'll do that.

  If you don't want to clobber your buildroot tree with
configs/mysystem_dev_defconfig, you can instead do:

  make clean
  cat mysystem_base_defconfig.frag mysystem_dev_defconfig.frag > /tmp/mysystem_dev_defconfig
  make defconfig BR2_DEFCONFIG=/tmp/mysystem_dev_defconfig
  make


  And to create the _dev fragment, you can try something like:

make savedefconfig
sort defconfig mysystem_base_defconfig.frag | uniq -u > mysystem_dev_defconfig.frag

(this is just from the top of my head so YMMV).


  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2012-12-05 17:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 22:00 [Buildroot] How to handle modularity in buildroot? Charles Manning
2012-12-03 23:17 ` ANDY KENNEDY
2012-12-03 23:49   ` Charles Manning
2012-12-04  9:01     ` Stephan Hoffmann
2012-12-04  9:10     ` Bjørn Forsman
2012-12-04  9:10     ` Thomas Petazzoni
2012-12-04 18:18       ` Charles Manning
2012-12-05 17:14         ` Arnout Vandecappelle [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=50BF80F0.8050603@mind.be \
    --to=arnout@mind.be \
    --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