From: Antonin Godard <antonin.godard@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Antonin Godard <antonin.godard@bootlin.com>,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: [PATCH v3 5/6] ref-manual/variables.rst: document HOST_*_ARCH variables
Date: Thu, 27 Mar 2025 10:07:30 +0100 [thread overview]
Message-ID: <20250327-cc-vars-v3-5-742dbddce008@bootlin.com> (raw)
In-Reply-To: <20250327-cc-vars-v3-0-742dbddce008@bootlin.com>
These variables control the flags for the assembler, compiler and
linker, but depend on the context.
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
documentation/ref-manual/variables.rst | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 4cb416bd0..c3ed1a106 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -3673,6 +3673,20 @@ system and gives an overview of their function and contents.
- mips
- mipsel
+ :term:`HOST_AS_ARCH`
+ Specifies architecture-specific assembler flags.
+
+ Default initialization for :term:`HOST_AS_ARCH` varies depending on what
+ is being built:
+
+ - :term:`TARGET_AS_ARCH` when building for the
+ target
+
+ - :term:`BUILD_AS_ARCH` when building for the build host (i.e.
+ ``-native``)
+
+ - :term:`SDK_AS_ARCH` when building for an SDK (i.e. ``nativesdk-``)
+
:term:`HOST_CC_ARCH`
Specifies architecture-specific compiler flags that are passed to the
C compiler.
@@ -3689,6 +3703,19 @@ system and gives an overview of their function and contents.
- ``BUILDSDK_CC_ARCH`` when building for an SDK (i.e.
``nativesdk-``)
+ :term:`HOST_LD_ARCH`
+ Specifies architecture-specific linker flags.
+
+ Default initialization for :term:`HOST_LD_ARCH` varies depending on what
+ is being built:
+
+ - :term:`TARGET_LD_ARCH` when building for the target
+
+ - :term:`BUILD_LD_ARCH` when building for the build host (i.e.
+ ``-native``)
+
+ - :term:`SDK_LD_ARCH` when building for an SDK (i.e. ``nativesdk-``)
+
:term:`HOST_OS`
Specifies the name of the target operating system, which is normally
the same as the :term:`TARGET_OS`. The variable can
--
2.47.0
next prev parent reply other threads:[~2025-03-27 9:07 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 ` [docs] " Quentin Schulz
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 ` Antonin Godard [this message]
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=20250327-cc-vars-v3-5-742dbddce008@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox