Lines Matching full:dependency

123   This defines a dependency for this menu entry. If multiple
167   from a direct dependency or with a visible prompt.
198   FOO should imply not only BAZ, but also its dependency BAR::
241 module state. Dependency expressions have the following syntax::
300 the menu entry, e.g. this means the dependency "NET" is added to the
301 dependency list of the config option NETDEVICES.
306 be part of the dependency list and then one of these two conditions
379 dependency, but will not appear under menuconfig M anymore, because
436 This defines an if block. The dependency expression <expr> is appended
507 to describe the dependency on the compiler feature is to use "depends on"
533 If a config symbol has a dependency, but the code controlled by the config
534 symbol can still be compiled if the dependency is not met, it is encouraged to
536 dependency. This is especially useful for drivers for more exotic hardware, as
540 the dependency is not met.
554 driver can be used on. The dependency can be an architecture (e.g. ARM) or
555 platform (e.g. ARCH_OMAP4) dependency. This makes life simpler not only for
559 Such a dependency can be relaxed by combining it with the compile-testing rule
573 The most common way to express this optional dependency in Kconfig logic
580 This means that there is either a dependency on BAR that disallows
585 the same dependency, a helper symbol can be used, like::
594 Much less favorable way to express optional dependency is IS_REACHABLE() within
609 Kconfig recursive dependency limitations
612 If you've hit the Kconfig error: "recursive dependency detected" you've run
613 into a recursive dependency issue with Kconfig, a recursive dependency can be
614 summarized as a circular dependency. The kconfig tools need to ensure that
620 dependency resolution; this has a few implications for Kconfig file writers.
652   b) Match dependency semantics:
662 some dependency criteria, for such cases you can work with solution b).
707 desirable to enable more complex dependency mappings and / or queries,
709 the current known recursive dependency issues. It is not known if this would
711 solver proves too complex or that it cannot address recursive dependency issues