Re: Kconfig Q: expressing a modularity dependency

[Tilman Schmidt <tilman@imap.cc>]

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

/me wrote, four months ago:
> My current attempts to port the Gigaset driver from isdn4linux
> to CAPI require the following Kconfig dependency:
> 
> - If isdn4linux or kernelcapi or both are built as a module
>   (CONFIG_ISDN_I4L=m || CONFIG_ISDN_CAPI=m)
>   then gigaset can only be built as a module
>   (CONFIG_ISDN_DRV_GIGASET depends on m).
> 
> - If neither isdn4linux nor kernelcapi ar built as a module
>   (CONFIG_ISDN_I4L!=m && CONFIG_ISDN_CAPI!=m),
>   including the case that neither is being built at all
>   (CONFIG_ISDN_I4L=n && CONFIG_ISDN_CAPI=n),
>   then gigaset may be built statically or as a module
>   (all three tristate settings for CONFIG_ISDN_DRV_GIGASET are
>   legal).
> 
> How is that best expressed in Kconfig?

Judging from the complete silence following that question, the
answer is, apparently: not at all.

So I'll just put a notice in the help text then, warning people
not to set CONFIG_ISDN_DRV_GIGASET=y if their ISDN subsystem
is built as a module. If anybody has a better idea I'll be
glad to hear it.

Thx
T.

-- 
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]