From: "Swami" <swami310@gmail.com>
To: bitbake-devel@lists.openembedded.org, docs@lists.yoctoproject.org
Cc: michael.opdenacker@rootcommit.com, Swami <swami310@gmail.com>
Subject: [PATCH] bitbake-user-manual: Documenting BB_CMDLINE Add documentation for the internal read-only variable :term:'BB_CMDLINE'. Fixes [Yocto #15746] Signed-off-by: Swaminathan K <swami310@gmail.com>
Date: Wed, 3 Dec 2025 06:53:43 +0530 [thread overview]
Message-ID: <20251203012343.15709-1-swami310@gmail.com> (raw)
---
doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
index 734c7858a..f756c436d 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
@@ -116,6 +116,10 @@ overview of their function and contents.
Specifies if SSL certificates should be checked when fetching. The default
value is ``1`` and certificates are not checked if the value is set to ``0``.
+ :term:`BB_CMDLINE`
+ :term:'BB_CMDLINE' is an internal variable and is read-only.It captures the exact
+ command line used for the current invocation of BitBake.
+
:term:`BB_HASH_CODEPARSER_VALS`
Specifies values for variables to use when populating the codeparser cache.
This can be used selectively to set dummy values for variables to avoid
next reply other threads:[~2025-12-03 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 1:23 Swami [this message]
2025-12-03 8:15 ` [bitbake-devel] [PATCH] bitbake-user-manual: Documenting BB_CMDLINE Add documentation for the internal read-only variable :term:'BB_CMDLINE'. Fixes [Yocto #15746] Signed-off-by: Swaminathan K <swami310@gmail.com> 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=20251203012343.15709-1-swami310@gmail.com \
--to=swami310@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@rootcommit.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.