Messages in this thread | | | Date | Mon, 28 Apr 2008 09:39:54 +0300 | From | Adrian Bunk <> | Subject | Re: Kconfig 'depend' vs. 'select' |
| |
On Sun, Apr 27, 2008 at 05:45:36PM -0700, David Miller wrote: > > I'm trying to stir up interest in solving a problem that seems to pop > up frequently. :) > > The short story is: > > 1) If you say your driver "depend"s on a subsystem providing a set of > interfaces you need, this doesn't work properly if your driver is > marked built-in and that subsystem you need is modular for some > reason. >...
This should work.
Can you give an example of the problem you are thinking of?
> So if you had, for example: > > config FOO_API > ... > > and then you had two drivers: > > config DRIVER1 > tristate ... > needs FOO_API > > config DRIVER2 > tristate ... > needs FOO_API > > and DRIVER1 was built modular but DRIVER2 was built-in, > the Kconfig system would make sure FOO_API were built-in. > > The "needs" name and syntax is just something arbitrary I came up > with, don't take it too seriously :-)
What about "select"?
That's exactly what it's doing.
cu Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
| |