From 859d36b1309ccb41d0218bfad11c4cfceebcd980 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 5 Sep 2018 09:31:24 -0700 Subject: bitbake: bitbake-user-manual: Added BBMULTICONFIG support The BBMULTICONFIG variable is a variable used for BitBake and was not documented in the BitBake Manual glossary. I added the definition. I also added the variable to the example in the section describing how to execute builds for multiple configurations. (Bitbake rev: 836f994ec530ba82c935cb41e006d1f128885dc2) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../bitbake-user-manual-intro.xml | 26 +++++++++++---- .../bitbake-user-manual-ref-variables.xml | 39 ++++++++++++++++++++++ 2 files changed, 58 insertions(+), 7 deletions(-) (limited to 'bitbake/doc') diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml index 1dbf141c9e..47c8d5d89b 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml @@ -769,11 +769,23 @@ Aside from separate configuration files for each - target, you have to enable BitBake to perform multiple - configuration builds by enabling it in the local + target, you must also enable BitBake to perform multiple + configuration builds. + Enabling is accomplished by setting the + BBMULTICONFIG + variable in the local.conf configuration file. - Enabling is accomplished through a variable specific - to the build environment. + As an example, suppose you had configuration files + for target1 and + target2 defined in the build + directory. + The following statement in the + local.conf file both enables + BitBake to perform multiple configuration builds and + specifies the two multiconfigs: + + BBMULTICONFIG = "target1 target2" + @@ -785,10 +797,10 @@ $ bitbake [multiconfig:multiconfigname:]target [[[multiconfig:multiconfigname:]target] ... ] Here is an example for two multiconfigs: - Target_1 and - Target_2: + target1 and + target2: - $ bitbake multiconfig:Target_1:target multiconfig:Target_2:target + $ bitbake multiconfig:target1:target multiconfig:target2:target diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml index 0313359d98..b5a793649c 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml @@ -1205,6 +1205,45 @@ + BBMULTICONFIG + + BBMULTICONFIG[doc] = "Enables BitBake to perform multiple configuration builds and lists each separate configuration (multiconfig)." + + + + + Enables BitBake to perform multiple configuration builds + and lists each separate configuration (multiconfig). + You can use this variable to cause BitBake to build + multiple targets where each target has a separate + configuration. + Define BBMULTICONFIG in your + conf/local.conf configuration file. + + + + As an example, the following line specifies three + multiconfigs, each having a separate configuration file: + + BBMULTIFONFIG = "configA configB configC" + + Each configuration file you use must reside in the + build directory within a directory named + conf/multiconfig (e.g. + build_directory/conf/multiconfig/configA.conf). + + + + For information on how to use + BBMULTICONFIG in an environment that + supports building targets with multiple configurations, + see the + "Executing a Multiple Configuration Build" + section. + + + + BBPATH -- cgit v1.2.3-54-g00ecf