Lines Matching full:dependency

52 6. Any dependency of the +select+ form
114 * Use a +select+ type of dependency for dependencies on
120 The +select+ keyword expresses the dependency with a backward
123 * Use a +depends on+ type of dependency when the user really needs to
124 be aware of the dependency. Typically, Buildroot uses this type of
125 dependency for dependencies on target architecture, MMU support and
128 The +depends on+ keyword expresses the dependency with a forward
133 dependency semantics are not internally linked. Therefore, it may be
158 Note that these two dependency types are only transitive with the
193 the dependency of +Package B+ on +Package A+. Therefore, in such a
194 situation, the transitive dependency has to be added explicitly:
211 Note that such dependencies will ensure that the dependency option
213 so, the dependency also needs to be expressed in the +.mk+ file of the
243 If there is a dependency on a config option in that same file (typically
248 The general format of a dependency +comment+ for package foo is:
274 ** Dependency symbol: +BR2_powerpc+, +BR2_mips+, ... (see +arch/Config.in+)
278 ** Dependency symbol: +BR2_USE_MMU+
284 different sizes, one dependency symbol is available for each size:
285 ** Dependency symbol: +BR2_TOOLCHAIN_HAS_SYNC_1+ for 1 byte,
292 ** Dependency symbol: +BR2_TOOLCHAIN_HAS_ATOMIC+.
296 ** Dependency symbol: +BR2_TOOLCHAIN_HEADERS_AT_LEAST_X_Y+, (replace
302 ** Dependency symbol: +BR2_TOOLCHAIN_GCC_AT_LEAST_X_Y+, (replace
308 ** Dependency symbol: +BR2_HOST_GCC_AT_LEAST_X_Y+, (replace
315 ** Dependency symbol: +BR2_TOOLCHAIN_USES_GLIBC+,
322 ** Dependency symbol: +BR2_INSTALL_LIBSTDCPP+
326 ** Dependency symbol: +BR2_TOOLCHAIN_HAS_DLANG+
330 ** Dependency symbol: +BR2_TOOLCHAIN_HAS_FORTRAN+
334 ** Dependency symbol: +BR2_TOOLCHAIN_HAS_THREADS+
339 ** Dependency symbol: +BR2_TOOLCHAIN_HAS_THREADS_NPTL+
343 ** Dependency symbol: +BR2_TOOLCHAIN_HAS_NATIVE_RPC+
347 ** Dependency symbol: +BR2_USE_WCHAR+
351 ** Dependency symbol: +!BR2_STATIC_LIBS+
358 Config.in file to express this dependency, similar to dependencies on
365 If there is a dependency on both toolchain options and the Linux
381 If there is a dependency on both toolchain options and udev /dev