Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Swami <swami310@gmail.com>
Cc: michael.opdenacker@rootcommit.com,
	bitbake-devel@lists.openembedded.org,
	docs@lists.yoctoproject.org
Subject: Re: [PATCH v4] bitbake-user-manual: Documenting BB_CMDLINE
Date: Wed,  3 Dec 2025 14:36:31 +0000 (UTC)	[thread overview]
Message-ID: <25d80654-678d-45e6-898e-bc79b7aeb75d@rootcommit.com> (raw)
In-Reply-To: <20251203113900.31314-1-swami310@gmail.com>

Hi Swami

Thanks for the update and your patience :)

On 12/3/25 12:39, Swami wrote:
> Add documentation for the internal read-only variable :term:`BB_CMDLINE`.
> Fixes [YOCTO #15746]
> Signed-off-by: Swaminathan K <swami310@gmail.com>
> ---
>   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..f49ce0f9f 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


Looks all good to me.
Reviewed-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>

-- 
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/



  reply	other threads:[~2025-12-03 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 11:39 [PATCH v4] bitbake-user-manual: Documenting BB_CMDLINE Swami
2025-12-03 14:36 ` Michael Opdenacker [this message]
2025-12-03 15:54 ` [bitbake-devel] " 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=25d80654-678d-45e6-898e-bc79b7aeb75d@rootcommit.com \
    --to=michael.opdenacker@rootcommit.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=swami310@gmail.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