From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package: don't default to y for categories
Date: Fri, 14 Nov 2008 11:15:45 +0100 [thread overview]
Message-ID: <20081114111545.3d3d5ca3@surf> (raw)
In-Reply-To: <20081114105226.505aa98b@hcegtvedt>
Le Fri, 14 Nov 2008 10:52:26 +0100,
Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> a ?crit :
> It was more a remark about a general "bug" in the menu system
> generated by kconfig now. Just look at the kernel, if you select a
> driver beneath SPI, then you are not able to deselect the SPI
> category. I think we should do the same with the kconfig in Buildroot.
This is important when enabling a category enables the compilation of a
particular set of code, required for the items available under this
specific category.
In our case, the categories ? Graphical libraries ?, ? Audio stuff ?
and others do not lead to anything being compiled, except if I'm wrong.
So I would say that we shouldn't be able to select/unselect the
categories. They should just be submenus, to organize the options, not
more.
Look at the top of the kernel configuration system. Networking support
can be enabled/disabled as a whole, while Device Drivers is just a
submenu. Our categories should be like Device Drivers, IMO.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-11-14 10:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 19:07 [Buildroot] [PATCH] package: don't default to y for categories Markus Heidelberg
[not found] ` <9060C4F3-5F97-416B-9363-ABF9FFA8E329@valka.is>
2008-11-14 8:57 ` Markus Heidelberg
2008-11-14 9:10 ` Hans-Christian Egtvedt
2008-11-14 9:21 ` Markus Heidelberg
2008-11-14 9:52 ` Hans-Christian Egtvedt
2008-11-14 10:15 ` Thomas Petazzoni [this message]
2008-11-14 10:19 ` Hans-Christian Egtvedt
2008-11-14 11:43 ` Peter Korsgaard
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=20081114111545.3d3d5ca3@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 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.