public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com
Cc: adriaan.schmidt@siemens.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 6/7] signatures: exclude TOPDIR from signatures
Date: Wed,  4 May 2022 13:41:08 +0200	[thread overview]
Message-ID: <20220504114109.3411005-7-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20220504114109.3411005-1-felix.moessbauer@siemens.com>

The TOPDIR variable contains the absolute path to the build directory.
As the general build environment must not depend on the path
where the build is executed from, we can safely exclude the
variable from the signatures.

This finally make the build-dir relocatable and improves caching.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/conf/bitbake.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 9fce7c1c..a05bd909 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -102,7 +102,7 @@ BB_HASHBASE_WHITELIST ?= "TMPDIR FILE PATH PWD BB_TASKHASH BBPATH BBSERVER DL_DI
     WORKDIR STAMPCLEAN PKGDATA_DIR BUILD_ARCH SSTATE_PKGARCH \
     BB_WORKERCONTEXT BB_LIMITEDDEPS DEPLOY_DIR BUILDCHROOT_DIR \
     REPO_ISAR_DIR REPO_ISAR_DB_DIR REPO_BASE_DIR REPO_BASE_DB_DIR LAYERDIR_core \
-    SCRIPTSDIR"
+    SCRIPTSDIR TOPDIR"
 BB_HASHCONFIG_WHITELIST ?= "${BB_HASHBASE_WHITELIST} DATE TIME SSH_AGENT_PID \
     SSH_AUTH_SOCK PSEUDO_BUILD BB_ENV_EXTRAWHITE DISABLE_SANITY_CHECKS \
     BB_NUMBER_THREADS BB_ORIGENV BB_INVALIDCONF BBINCLUDED \
-- 
2.30.2


  parent reply	other threads:[~2022-05-04 11:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 11:41 [PATCH 0/7] Further improve cachability of ISAR Felix Moessbauer
2022-05-04 11:41 ` [PATCH 1/7] signatures: exclude path to core layer from bb hashes Felix Moessbauer
2022-05-04 11:41 ` [PATCH 2/7] signatures: whitelist external SCRIPTSDIR Felix Moessbauer
2022-05-04 11:41 ` [PATCH 3/7] signatures: exclude BITBAKEDIR from WIC Felix Moessbauer
2022-05-04 11:41 ` [PATCH 4/7] signatures: use TOPDIR instead of BUILDDIR in wic Felix Moessbauer
2022-05-04 11:41 ` [PATCH 5/7] signatures: unify WKS_* variable exclusions with OE Felix Moessbauer
2022-05-04 11:41 ` Felix Moessbauer [this message]
2022-05-04 11:41 ` [PATCH 7/7] signatures: do not expand SRC_URI Felix Moessbauer
2022-05-16  9:29 ` [PATCH 0/7] Further improve cachability of ISAR Anton Mikanovich

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=20220504114109.3411005-7-felix.moessbauer@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=isar-users@googlegroups.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