From: Kumar Gala <galak@kernel.crashing.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: kbuild question
Date: Fri, 16 Feb 2007 08:14:40 -0600 [thread overview]
Message-ID: <9AF725F4-FE65-4357-B7EB-CC03808C105D@kernel.crashing.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702161121540.14458@scrub.home>
On Feb 16, 2007, at 4:23 AM, Roman Zippel wrote:
> Hi,
>
> On Thu, 15 Feb 2007, Kumar Gala wrote:
>
>> I was wondering if there was some way to make a Kconfig menu
>> either be just a
>> menu or a choice depending on another bool being set or not.
>>
>> What I'm trying to accomplish is if CONFIG_ONLY_HAVE_ONE is set I
>> want it so
>> you can only select on option, however if CONFIG_ONLY_HAVE_ONE is
>> not set you
>> should be able to select multiple options.
>
> Could you please be more specific about the problem you're trying to
> solve, instead of how you're trying to solve it?
> A real example would help a lot to understand the actual problem.
Sure, on powerpc for some of the embedded sub-architectures you can
only select a single board to build for. For a lot of people this is
sufficient, however we are moving towards a world where you can
easily build in support for multiple boards into a single kernel.
I'd like to have it such that if I'm only building support for one
board (CONFIG_ONLY_HAVE_ONE, not going to call it that, but for this
discussion its sufficient), you get a choice menu from Kconfig
enforcing the ability to only select one board. However if !
CONFIG_ONLY_HAVE_ONE than you can select multiple boards to build
into your kernel.
if CONFIG_ONLY_HAVE_ONE is set we can optimize out the runtime checks
that get added for handling the multiple board case.
Hopefully that's clear.
- k
next prev parent reply other threads:[~2007-02-16 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 19:18 kbuild question Kumar Gala
2007-02-15 22:33 ` Sam Ravnborg
2007-02-15 23:44 ` Kumar Gala
2007-02-16 8:50 ` Sam Ravnborg
2007-02-16 10:23 ` Roman Zippel
2007-02-16 14:14 ` Kumar Gala [this message]
2007-02-18 17:16 ` Roman Zippel
2007-02-18 19:25 ` Sam Ravnborg
2007-03-15 15:22 ` Kumar Gala
2011-03-02 21:11 KBuild question Tom Bart
2011-03-02 21:40 ` Sam Ravnborg
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=9AF725F4-FE65-4357-B7EB-CC03808C105D@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.