From: Paul Eggleton <bluelightning@bluelightning.org>
To: bitbake-devel@lists.openembedded.org
Cc: michael.opdenacker@bootlin.com
Subject: [PATCH 3/3] bitbake-user-manual: add BB_HASH_CODEPARSER_VALS
Date: Sat, 22 Apr 2023 15:05:23 +1200 [thread overview]
Message-ID: <91ed713bc9a00b7ae5ea2994a8a7431025392902.1682131637.git.bluelightning@bluelightning.org> (raw)
In-Reply-To: <cover.1682131637.git.bluelightning@bluelightning.org>
New variable for 2.4.
Signed-off-by: Paul Eggleton <bluelightning@bluelightning.org>
---
.../bitbake-user-manual-ref-variables.rst | 11 +++++++++++
1 file changed, 11 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 fc7cb88238..6ccf58b212 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
@@ -108,6 +108,17 @@ 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_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
+ the codeparser cache growing on every parse. Variables that would typically
+ be included are those where the value is not significant for where the
+ codeparser cache is used (i.e. when calculating variable dependencies for
+ code fragments.) The value is space-separated without quoting values, for
+ example::
+
+ BB_HASH_CODEPARSER_VALS = "T=/ WORKDIR=/ DATE=1234 TIME=1234"
+
:term:`BB_CONSOLELOG`
Specifies the path to a log file into which BitBake's user interface
writes output during the build.
--
2.34.1
next prev parent reply other threads:[~2023-04-22 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 3:05 [PATCH 0/3] BitBake user manual updates for 2.4 Paul Eggleton
2023-04-22 3:05 ` [PATCH 1/3] bitbake-user-manual: document BB_CACHEDIR Paul Eggleton
2023-04-22 3:05 ` [PATCH 2/3] bitbake-user-manual: add addpylib and BB_GLOBAL_PYMODULES Paul Eggleton
2023-04-22 3:05 ` Paul Eggleton [this message]
2023-04-22 9:33 ` [bitbake-devel] [PATCH 0/3] BitBake user manual updates for 2.4 Richard Purdie
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=91ed713bc9a00b7ae5ea2994a8a7431025392902.1682131637.git.bluelightning@bluelightning.org \
--to=bluelightning@bluelightning.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=michael.opdenacker@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;
as well as URLs for NNTP newsgroup(s).