archive mirror
 help / color / mirror / Atom feed
From: Paul Eggleton <>
Subject: [PATCH 1/3] bitbake-user-manual: document BB_CACHEDIR
Date: Sat, 22 Apr 2023 15:05:21 +1200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

New variable for 2.4.

Signed-off-by: Paul Eggleton <>
 .../bitbake-user-manual-ref-variables.rst                    | 5 +++++
 1 file changed, 5 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 25620fdda1..1cf37d5fcd 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
@@ -99,6 +99,11 @@ overview of their function and contents.
       the path of the build. BitBake's output should not (and usually does
       not) depend on the directory in which it was built.
+   :term:`BB_CACHEDIR`
+      Specifies the code parser cache directory (distinct from :term:`CACHE`
+      and :term:`PERSISTENT_DIR` although they can be set to the same value
+      if desired). The default value is "${TOPDIR}/cache".
       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``.

  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 ` Paul Eggleton [this message]
2023-04-22  3:05 ` [PATCH 2/3] bitbake-user-manual: add addpylib and BB_GLOBAL_PYMODULES Paul Eggleton
2023-04-22  3:05 ` [PATCH 3/3] bitbake-user-manual: add BB_HASH_CODEPARSER_VALS Paul Eggleton
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).