13968 2020-07-03 04:33:46 +0000 variables in BB_HASHBASE_WHITELIST built from non-whitelisted variables should trigger a warning 2021-04-20 13:08:17 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple RESOLVED WORKSFORME Medium normal 3.4 1 ydirson richard.purdie poky.bs.watcher poky.watcher randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 87678 0 ydirson 2020-07-03 04:33:46 +0000 https://github.com/rockchip-linux/meta-rockchip/ demonstrates the issue: conf/layer.conf:RK_LICENSE_PATH = "${LAYERDIR}/files/custom-licenses" conf/layer.conf:RK_BINARY_LICENSE = "${RK_LICENSE_PATH}/LICENSE.rockchip" conf/layer.conf:LICENSE_PATH += "${RK_LICENSE_PATH}" This causes task hashes to change when building in a different location because RK_LICENSE_PATH then changes. Obviously an oversight, and bitbabke shoule be able to warn about this case. 87724 1 randy.macleod 2020-07-09 07:45:58 +0000 yocto-check-layer does this already. 90022 2 richard.purdie 2021-04-20 13:08:17 +0000 If you run our check-layer script this will be highlighted. It is hard for bitbake to test without having two runs to compare. If you have a proposal on how to make bitbake detect the change generically I'm open to ideas but I can't see an easy way to have this work "out the box". Hard to know what to mark this as in bugzilla, going for worksforme which isn't quite right but...