From d3a849fdb415810e5adb290ef069b98b790cccf2 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 3 Sep 2013 16:32:20 +0300 Subject: ref-manual: Updated DEPENDS and RDEPENDS variable descriptions. I have added more information to both these variables to help explain their use better. Based on email from Paul Eggleton. Each entry now features a simple example. (From yocto-docs rev: 1ec67c639f15259ac67d5591d1d7a23522b0a822) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 61 +++++++++++++++++++++++++++--- 1 file changed, 56 insertions(+), 5 deletions(-) (limited to 'documentation/ref-manual') diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index a07ce4a298..4ffda80b96 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -968,6 +968,28 @@ Core layer for images cannot be removed have been built and have their contents in the appropriate sysroots before the recipe's configure task is executed. + + + Consider this simple example for two recipes named "a" and + "b" that produce similarly named packages. + In this example, the DEPENDS + statement appears in the "a" recipe: + + DEPENDS = "b" + + Here, the dependency is such that the + do_configure task for recipe "a" + depends on the do_populate_sysroot + task of recipe "b". + This means anything that recipe "b" puts into sysroot + is available when recipe "a" is configuring itself. + + + + For information on runtime dependencies, see the + RDEPENDS + variable. + @@ -3750,13 +3772,36 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" RDEPENDS - Lists a package's run-time dependencies (i.e. other packages) + Lists a package's runtime dependencies (i.e. other packages) that must be installed in order for the built package to run correctly. If a package in this list cannot be found during the build, you will get a build error. + + When you use the RDEPENDS variable + in a recipe, you are essentially stating that the recipe's + do_build task depends on the existence + of a specific package. + Consider this simple example for two recipes named "a" and + "b" that produce similarly named packages. + In this example, the RDEPENDS + statement appears in the "a" recipe: + + RDEPENDS_${PN} = "b" + + Here, the dependency is such that the + do_build task for recipe "a" depends + on the do_package_write task + of recipe "b". + This means the package file for "b" must be available when + the output for recipe "a" has been completely built. + More importantly, package "a" will be marked as depending + on package "b" in a manner that is understood by the + package manager in use (i.e. rpm, opkg, or dpkg). + + The names of the packages you list within RDEPENDS must be the names of other @@ -3799,26 +3844,32 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" In many cases you do not need to explicitly add - run-time dependencies using + runtime dependencies using RDEPENDS since some automatic handling occurs: shlibdeps: If - a run-time package contains a shared library + a runtime package contains a shared library (.so), the build processes the library in order to determine other libraries to which it is dynamically linked. The build process adds these libraries to - RDEPENDS when creating the run-time + RDEPENDS when creating the runtime package. pcdeps: If the package ships a pkg-config information file, the build process uses this file to add items to the RDEPENDS - variable to create the run-time packages. + variable to create the runtime packages. + + + For information on build-time dependencies, see the + DEPENDS + variable. + -- cgit v1.2.3-54-g00ecf