From accd9e7b62b263446f2969be6f4915a61f3cfcb9 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <srifenbark@gmail.com>
Date: Mon, 27 Aug 2018 09:14:42 -0700
Subject: dev-manual: Updates to section on multiconfig builds

* Added qualifying text indicating that you can build images or
packages.  In other words, the multiconfig does not necessarily
have to be an image.  It can be a package as well.

* Added qualifying text describing that it is not a requirement
to have separate TMPDIRs for each multiconfig.  I used a build
for two multiconfigs of "qemux86" for different DISTROs as
a case.

(From yocto-docs rev: 6e5ed0d1ab305c3382fea55fc1a2deaac0b7d518)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/dev-manual/dev-manual-common-tasks.xml | 20 +++++++++++++++-----
 1 file changed, 15 insertions(+), 5 deletions(-)

(limited to 'documentation')

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 2a93ce9c2d..cd7a435106 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -5326,9 +5326,9 @@
 
             <para>
                 You can use a single <filename>bitbake</filename> command
-                to build multiple images for different targets where each
-                image requires a different configuration (multiple
-                configuration builds).
+                to build multiple images or packages for different targets
+                where each image or package requires a different configuration
+                (multiple configuration builds).
                 The builds, in this scenario, are sometimes referred to as
                 "multiconfigs", and this section uses that term throughout.
             </para>
@@ -5363,8 +5363,18 @@
                             Minimally, each configuration file must define the
                             machine and the temporary directory BitBake uses
                             for the build.
-                            You must not overlap the temporary directories
-                            used during the build.</para>
+                            Suggested practice dictates that you do not
+                            overlap the temporary directories
+                            used during the builds.
+                            However, it is possible that you can share the
+                            temporary directory
+                            (<ulink url='&YOCTO_DOCS_REF_URL;#var-TMPDIR'><filename>TMPDIR</filename></ulink>).
+                            For example, consider a scenario with two
+                            different multiconfigs for the same
+                            <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>: "qemux86" built for
+                            two distributions such as "poky" and "poky-lsb".
+                            In this case, you might want to use the same
+                            <filename>TMPDIR</filename>.</para>
 
                             <para>Here is an example showing the minimal
                             statements needed in a configuration file for
-- 
cgit v1.2.3-54-g00ecf