Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Stuff for the next release (2010.11)
Date: Sun, 22 Aug 2010 00:01:59 +0200	[thread overview]
Message-ID: <20100822000159.04f432dc@surf> (raw)
In-Reply-To: <20100821173633.GA27302@merkur.ravnborg.org>

Hello Sam,

On Sat, 21 Aug 2010 19:36:33 +0200
Sam Ravnborg <sam@ravnborg.org> wrote:

> For the record we are working on making the integration
> easier for non-kernel projects utilizing kconfig.

Yes, I've followed parts of the discussion about this, and that's very
good news. I think other projects, such as Crosstool-NG, Busybox,
PTXdist, uClibc and all users of kconfig will greatly benefit from this.

> In headlines that is:
> - Make CONFIG_ prefix configurable at buildtime
>   Basically adding -DCONFIG_=BR2_ will do the trick
> 
> - Use mainmenu entry as headline in the frontends
> 
> - Drop "kernel" from all help texts
>   So there is no longer any "kernel" texts hardcoded
> 
> I guess a few other nits I forgot.
> 
> I hope this is merged in next merge window - but no promises.

Ok. I'll try to update our package/config stuff against the mainline
kernel regularly, so that we can take advantage from this work.

FWIW, we also have other patches to scripts/kconfig besides
s/kernel/Buildroot/ and the change of the prefix. We have some stuff to
support the fact that the .config file and all related generated files
must be in the output directory in the case of an out-of-tree build. I
haven't look at those changes in detail, they were implemented by Peter.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-08-21 22:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21 16:46 [Buildroot] Stuff for the next release (2010.11) Thomas Petazzoni
2010-08-21 17:36 ` Sam Ravnborg
2010-08-21 22:01   ` Thomas Petazzoni [this message]
2010-08-22  0:36 ` Lionel Landwerlin

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=20100822000159.04f432dc@surf \
    --to=thomas.petazzoni@free-electrons.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