The devtool add
command attempts to
detect build-time dependencies and map them to other recipes
in the system.
During this mapping, the command fills in the names of those
recipes as part of the
DEPENDS
variable within the recipe.
If a dependency cannot be mapped, devtool
places a comment in the recipe indicating such.
The inability to map a dependency can result from naming not
being recognized or because the dependency simply is not
available.
For cases where the dependency is not available, you must use
the devtool add
command to add an
additional recipe that satisfies the dependency.
Once you add that recipe, you need to update the
DEPENDS
variable in the original recipe
to include the new recipe.
If you need to add runtime dependencies, you can do so by adding the following to your recipe:
RDEPENDS_${PN} += "dependency1 dependency2 ...
"
devtool add
command often cannot
distinguish between mandatory and optional dependencies.
Consequently, some of the detected dependencies might
in fact be optional.
When in doubt, consult the documentation or the configure
script for the software the recipe is building for further
details.
In some cases, you might find you can substitute the
dependency with an option that disables the associated
functionality passed to the configure script.