From 425e00fb99b29b1ad772829647465ab79671e318 Mon Sep 17 00:00:00 2001 From: Paul Eggleton Date: Wed, 10 Oct 2012 14:24:15 -0700 Subject: documentation: poky-ref-manual - New PACKAGECONFIG glossary entry. Add a description of the PACKAGECONFIG variable to the variable glossary. (From yocto-docs rev: 07d08314d3151de7073567a7800156f69fdb549e) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/poky-ref-manual/ref-variables.xml | 33 +++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/documentation/poky-ref-manual/ref-variables.xml b/documentation/poky-ref-manual/ref-variables.xml index 916366e88e..7d60758226 100644 --- a/documentation/poky-ref-manual/ref-variables.xml +++ b/documentation/poky-ref-manual/ref-variables.xml @@ -1605,6 +1605,39 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" + PACKAGECONFIG + + + This variable provides a means of enabling or disabling features of a recipe + on a per-recipe basis. + The PACKAGECONFIG + variable itself specifies a space-separated list of the features + to enable, while the named flags set on the variable specify + for each feature the additional build dependencies + (DEPENDS) + that should be added if the feature is enabled, and any extra arguments + that should be added to the configure script argument list + (EXTRA_OECONF) + if the feature is enabled or disabled. + + + For example, the following taken from the librsvg + recipe will add --with-croco to the + configure script arguments and libcroco to + DEPENDS + by default. + However, if "croco" is removed from PACKAGECONFIG + (for example, by using a .bbappend file in another layer), then + --without-croco will be added to the configure + script arguments instead: + + PACKAGECONFIG ??= "croco" + PACKAGECONFIG[croco] = "--with-croco,--without-croco,libcroco" + + + + + PACKAGES The list of packages to be created from the recipe. -- cgit v1.2.3-54-g00ecf