Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Any way to override .config settings?
Date: Thu, 20 Dec 2012 01:20:44 +0100	[thread overview]
Message-ID: <50D259DC.7090509@mind.be> (raw)
In-Reply-To: <CAE21AQrTh=bTke7awGUDfp+SfJJx5K1L6HVVhMs5F4eXAaZaTA@mail.gmail.com>

On 20/12/12 01:13, Charles Manning wrote:
> On Thu, Dec 20, 2012 at 1:04 PM, Arnout Vandecappelle<arnout@mind.be>  wrote:
>> On 19/12/12 23:20, Charles Manning wrote:
>>>
>>> I need to be able to build a system from an svn repository using a
>>> bunch of different revisions for different elements. For example, I
>>> might want to use the kernel at r 1234, u-boot at r 4567 and the
>>> rootfs+apps at r 3344.
>>
>>
>>   Uh? Sounds like a horrible idea to me.
>
> Why does it sound like a terrible idea?

  I thought you meant the buildroot directories would be at different 
versions. But you just want to override the 
BR2_LINUX_KERNEL_CUSTOM_GIT_VERSION, that's OK of course.

[snip]
>>> 1) Is there a built in mechanism in buildroot to include extra symbols
>>> and override those in .config?
>>
>>
>>   Yes, the package override file: BR2_PACKAGE_OVERRIDE_FILE, defaults to
>> $(TOPDIR)/local.mk. I use this to include a bunch of project-specific .mk
>> files that add packages without requiring a Config.in.
>
> In a separate thread to this, I submitted a patch that follows the
> package overriding idea to override the config

  Since it does exactly the same as BR2_PACKAGE_OVERRIDE_FILE, I don't 
see the point... Unless you want to start overriding toolchain configs.

  Actually, I don't see much point to override the .config - why not just 
save a different .config?


  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-20  0:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 22:20 [Buildroot] Any way to override .config settings? Charles Manning
2012-12-20  0:04 ` Arnout Vandecappelle
2012-12-20  0:13   ` Charles Manning
2012-12-20  0:20     ` Arnout Vandecappelle [this message]
2012-12-20  0:26       ` Steve Calfee
     [not found]         ` <CAE21AQpTYPzOG-M1W_ERLJjX6DijJyt4eXWeu-qg0A1=cXNPJQ@mail.gmail.com>
2012-12-20  1:00           ` Steve Calfee
2012-12-20  1:12             ` Charles Manning

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=50D259DC.7090509@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