[Buildroot] [PATCH 0/7] Introduce the _AVAILABLE mechanism
Thomas Petazzoni
thomas.petazzoni at free-electrons.com
Wed Oct 17 19:30:40 UTC 2012
Arnout,
On Tue, 16 Oct 2012 07:39:52 +0200, Arnout Vandecappelle wrote:
> Originally I was in favour of having the BR2_PACKAGE_PYTHON
> conditionals, but it _would_ probably make life simpler if we only
> had dependencies on toolchain options...
>
> Yann, what do you think, would it make suboption handling simpler
> if there was no 'depends on BR2_PACKAGE_PYTHON'?
The real problem with _AVAILABLE is not caused by Python/X.org packages
being under a big "if" condition. The big problem we hadn't really seen
is that we don't only need to add _AVAILABLE options for each package,
but also for each package sub-options that does a select on another
package. This means that the number of _AVAILABLE kconfig options to
add is a lot bigger than we expected, at a point that probably makes
the _AVAILABLE solution relatively impractical.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
More information about the buildroot
mailing list