From: Quentin Schulz <quentin.schulz@cherry.de>
To: antonin.godard@bootlin.com, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH v3 3/6] ref-manual/variables.rst: add missing documentation for BUILD_* variables
Date: Fri, 28 Mar 2025 14:43:30 +0100 [thread overview]
Message-ID: <d7dd4348-8e44-47a7-ae86-d55caab98dc8@cherry.de> (raw)
In-Reply-To: <20250327-cc-vars-v3-3-742dbddce008@bootlin.com>
Hi Antonin,
On 3/27/25 10:07 AM, Antonin Godard via lists.yoctoproject.org wrote:
> These toolchain variables are used in a native context. Some of the
> BUILD_* variables missed documentation. Also, some of the base commands
> were also not there so document them.
>
> Some of existing BUILD_* variable documentation were missing the note
> about their usage in a native context, so add it too so that all BUILD_*
> variables are documented the same way.
>
> [YOCTO #15719]
>
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
> documentation/ref-manual/variables.rst | 250 ++++++++++++++++++++++++++++++---
> 1 file changed, 230 insertions(+), 20 deletions(-)
>
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index d98721818..0516c1816 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -986,55 +986,165 @@ system and gives an overview of their function and contents.
> variable is a useful pointer in case a bug in the software being
> built needs to be manually reported.
>
> + :term:`BUILD_AR`
> + Specifies the architecture-specific :manpage:`archiver <ar(1)>` for the
> + build host, and its default definition is derived in part from
> + :term:`BUILD_PREFIX`::
> +
> + BUILD_AR = "${BUILD_PREFIX}ar"
> +
> + When building a :ref:`ref-classes-native` recipe, :term:`AR` is set to the
> + value of this variable by default.
> +
> + The :term:`BUILD_AR` variable should not be set manually, and is rarely
> + used in recipes as :term:`AR` contains the appropriate value depending on
> + the context (native or target recipes). Exception be made for target
> + recipes that need to use the :manpage:`archiver <ar(1)>` from the build
> + host at some point during the build.
> +
> :term:`BUILD_ARCH`
> Specifies the architecture of the build host (e.g. ``i686``). The
> OpenEmbedded build system sets the value of :term:`BUILD_ARCH` from the
> machine name reported by the ``uname`` command.
>
> + :term:`BUILD_AS`
> + Specifies the architecture-specific :manpage:`assembler <as(1)>` for the
> + build host, and its default definition is derived in part from
> + :term:`BUILD_PREFIX`::
> +
> + BUILD_AS = "${BUILD_PREFIX}as"
> +
It actually is
${BUILD_PREFIX}as ${BUILD_AS_ARCH}
With that change:
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Thanks!
Quentin
next prev parent reply other threads:[~2025-03-28 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 9:07 [PATCH v3 0/6] Document missing toolchain related variables Antonin Godard
2025-03-27 9:07 ` [PATCH v3 1/6] documentation/conf.py: define a manpage url Antonin Godard
2025-03-27 15:35 ` [docs] " Mark Hatle
2025-03-31 15:01 ` Antonin Godard
2025-03-28 13:21 ` Quentin Schulz
2025-03-27 9:07 ` [PATCH v3 2/6] ref-manual/variables.rst: add manpage links for toolchain variables Antonin Godard
2025-03-28 13:23 ` [docs] " Quentin Schulz
2025-03-27 9:07 ` [PATCH v3 3/6] ref-manual/variables.rst: add missing documentation for BUILD_* variables Antonin Godard
2025-03-28 13:43 ` Quentin Schulz [this message]
2025-03-27 9:07 ` [PATCH v3 4/6] ref-manual/variables.rst: document missing SDK_*_ARCH variables Antonin Godard
2025-03-27 9:07 ` [PATCH v3 5/6] ref-manual/variables.rst: document HOST_*_ARCH variables Antonin Godard
2025-03-27 9:07 ` [PATCH v3 6/6] ref-manual/variables.rst: HOST_CC_ARCH: fix wrong SDK reference Antonin Godard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d7dd4348-8e44-47a7-ae86-d55caab98dc8@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.