From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <antonin.godard@bootlin.com>, <docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 1/4] ref-manual/variables.rst: add missing documentation for BUILD_* variables
Date: Mon, 17 Mar 2025 18:01:58 +0100 [thread overview]
Message-ID: <D8IPBEJQM2F1.3PQZI1N1TTMJT@bootlin.com> (raw)
In-Reply-To: <20250317-cc-vars-v1-1-25edbadfd054@bootlin.com>
On Mon Mar 17, 2025 at 5:03 PM CET, 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 (FC and READELF).
>
> 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 | 107 +++++++++++++++++++++++++
> 1 file changed, 107 insertions(+)
>
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 861b04eaa..24b3f7db9 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -985,6 +985,24 @@ 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 archiver for the build host,
> + derived in part from :term:`BUILD_PREFIX`::
> +
> + BUILD_AR = "${BUILD_PREFIX}ar"
> +
> + When building in the ``-native`` context, :term:`AR` is set to the value
> + of this variable by default.
> +
> + :term:`BUILD_AS`
> + Specifies the architecture-specific assembler for the build host,
> + derived in part from from :term:`BUILD_PREFIX`::
> +
> + BUILD_AS = "${BUILD_PREFIX}ar"
Should be "${BUILD_PREFIX}as", will fix in v2.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-03-17 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 16:03 [PATCH 0/4] Document missing toolchain related variables Antonin Godard
2025-03-17 16:03 ` [PATCH 1/4] ref-manual/variables.rst: add missing documentation for BUILD_* variables Antonin Godard
2025-03-17 17:01 ` Antonin Godard [this message]
2025-03-21 16:22 ` [docs] " Quentin Schulz
2025-03-26 9:17 ` Antonin Godard
2025-03-26 9:49 ` Quentin Schulz
2025-03-26 10:33 ` Antonin Godard
2025-03-26 11:39 ` Quentin Schulz
2025-03-17 16:03 ` [PATCH 2/4] ref-manual/variables.rst: document missing SDK_*_ARCH variables Antonin Godard
2025-03-17 16:03 ` [PATCH 3/4] ref-manual/variables.rst: document HOST_*_ARCH variables Antonin Godard
2025-03-21 16:25 ` [docs] " Quentin Schulz
2025-03-17 16:03 ` [PATCH 4/4] ref-manual/variables.rst: HOST_CC_ARCH: fix wrong SDK reference Antonin Godard
2025-03-21 16:28 ` [docs] " Quentin Schulz
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=D8IPBEJQM2F1.3PQZI1N1TTMJT@bootlin.com \
--to=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.