Re: [docs] [PATCH] ref/dev-manual: Update multiconfig documentation

[Marta Rybczynska <rybczynska@gmail.com>]

On Thu, Jun 9, 2022 at 11:40 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> Multiconfigs now work from layers. Update the documentation to match this change.
> Also fix a incorrect reference to different distros working within the same TMPDIR,
> that is incorrect.
>
> [YOCTO #13566]
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
>  documentation/dev-manual/common-tasks.rst | 31 ++++++++++++-----------
>  documentation/ref-manual/variables.rst    |  9 ++++---
>  2 files changed, 21 insertions(+), 19 deletions(-)
>
> diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
> index ca6d59438..7d17f8d65 100644
> --- a/documentation/dev-manual/common-tasks.rst
> +++ b/documentation/dev-manual/common-tasks.rst
> @@ -3704,7 +3704,7 @@ Setting Up and Running a Multiple Configuration Build
>
>  To accomplish a multiple configuration build, you must define each
>  target's configuration separately using a parallel configuration file in
> -the :term:`Build Directory`, and you
> +the :term:`Build Directory` or configuration directory within a layer, and you
>  must follow a required file hierarchy. Additionally, you must enable the
>  multiple configuration builds in your ``local.conf`` file.
>
> @@ -3712,16 +3712,19 @@ Follow these steps to set up and execute multiple configuration builds:
>
>  -  *Create Separate Configuration Files*: You need to create a single
>     configuration file for each build target (each multiconfig).
> -   Minimally, each configuration file must define the machine and the
> -   temporary directory BitBake uses for the build. 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
> -   (:term:`TMPDIR`). For example,
> -   consider a scenario with two different multiconfigs for the same
> +   The configuration definitions are implmentation dependency but often

A typo: implmentation -> implementation

Kind regards,
Marta