Lines Matching full:dependencies

49 3. Any dependencies on the target in +depends on+ form
50 4. Any dependencies on the toolchain in +depends on+ form
51 5. Any dependencies on other packages in +depends on+ form
78   dependencies of one or more target packages. In this case, add
111 dependencies are enabled. Typically, Buildroot uses the following
114 * Use a +select+ type of dependency for dependencies on
115   libraries. These dependencies are generally not obvious and it
117   dependencies are selected. For example, the _libgtk2_ package uses
125   dependency for dependencies on target architecture, MMU support and
126   toolchain options (see xref:dependencies-target-toolchain-options[]),
127   or for dependencies on "big" things, such as the X.org system.
134 possible to select a package, whom one of its dependencies/requirement
159 dependencies of the same kind.
189   +Package B+, it will not check for the dependencies of +Package B+,
208 Overall, for package library dependencies, +select+ should be
211 Note that such dependencies will ensure that the dependency option
219 [[dependencies-target-toolchain-options]]
220 ==== Dependencies on target and toolchain options
227 These dependencies have to be expressed with the appropriate 'depends
228 on' statements in the Config.in file. Additionally, for dependencies on
231 Dependencies on target architecture or MMU support should not be
234 dependencies explicitly.
237 be visible when the toolchain option dependencies are met. This means
238 that all other dependencies of the package (including dependencies on
354 ==== Dependencies on a Linux kernel built by buildroot
358 Config.in file to express this dependency, similar to dependencies on
372 ==== Dependencies on udev /dev management
388 ==== Dependencies on features provided by virtual packages