From acdfb5f3cc90e747f06ba655fa1b07e8d878e96e Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 14 Jul 2016 12:31:38 -0700 Subject: ref-manual: Added notes to the DEPENDS variable description. Fixes [YOCTO #9933] Added two notes to help clarify how DEPENDS works with pre-compiled objects. There are some details that trip people up. (From yocto-docs rev: 06917e97adf24816b0aee6fdfdd14aa79d4c6ab2) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 33 ++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) (limited to 'documentation/ref-manual') diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index b876bc3115..e265aa94bd 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -2791,6 +2791,39 @@ task of recipe "b". This means anything that recipe "b" puts into sysroot is available when recipe "a" is configuring itself. + + Notes + + + DEPENDS is a list of + recipe names. + Or, to be more precise, it is a list of + PROVIDES + names, which usually match recipe names. + Putting a package name such as "foo-dev" in + DEPENDS does not make + sense. + Use "foo" instead, as this will put files + from all the packages that make up "foo" - + including those from "foo-dev" - into the + sysroot. + + + Counter intuitively, + DEPENDS is often necessary + even for recipes that install precompiled + components. + For example, if "libfoo" is a precompiled + library that links against "libbar", then + linking against "libfoo" requires both "libfoo" + and "libbar" to be available in the sysroot. + Without a DEPENDS from the + recipe that installs "libfoo" to the recipe + that installs "libbar", other recipes might + fail to link against "libfoo". + + + -- cgit 1.2.3-korg