mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Roman Zippel <zippel@linux-m68k.org>,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [rfe] easier customization of kconfig for non-Linux projects
Date: Thu, 24 May 2007 09:23:40 -0400	[thread overview]
Message-ID: <200705240923.42035.vapier@gentoo.org> (raw)
In-Reply-To: <20070524064004.GA28923@uranus.ravnborg.org>

[-- Attachment #1: Type: text/plain, Size: 894 bytes --]

On Thursday 24 May 2007, Sam Ravnborg wrote:
> The intent with this is clear but the solution you suggest albeit simple
> does not really match where we could end up with kconfig.
> Recently Roman added support for options in the kconfig language
> and I would assume we could deal with most of this just using options.

that certainly sounds nicer :)

> One example could be to support options for the mainmenu entrye like this:
>
> mainmenu "Busybow config system"
> 	option project="Busybox"
> 	option version="$VERSION"   <= Where '$' signify an environment variable

this is doable now ?  if so, i'll test it out in uClibc ...

> In this way we could later distribute kconfig as a binary instead
> of building it into the source as today.

not entirely sure how useful that'd be unless you mean as a completely sep 
package that distributions would include ...
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2007-05-24 13:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24  5:17 Mike Frysinger
2007-05-24  6:40 ` Sam Ravnborg
2007-05-24 13:23   ` Mike Frysinger [this message]
2007-05-24 20:32     ` Sam Ravnborg
2007-05-24 21:05   ` [kbuild-devel] " Yann E. MORIN

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=200705240923.42035.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=zippel@linux-m68k.org \
    /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

all inboxes | Powered by JetHome®