summaryrefslogtreecommitdiff
path: root/recipes-core
diff options
context:
space:
mode:
authorMing Liu <ming.liu@toradex.com>2021-04-16 12:28:25 +0200
committerMax Krummenacher <max.krummenacher@toradex.com>2021-05-24 18:25:16 +0200
commit59e68224cba5579db63aed4f931e7372d04c170a (patch)
treedc91775b1d58546e2765a82cfdfe7de08235701a /recipes-core
parent751a426c155500ac656b6d832c4f62d5c58d21ec (diff)
toradex-sanity.bbclass: introduce bbclass file
I have observed a following OE build issue with the latest dunfell-5.x.y, as follows: ``` ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: TMPDIR changed to include path filtering from the pseudo database. It is recommended to use a clean TMPDIR with the new pseudo path filtering so TMPDIR would need to be removed to continue. ``` this is due to the ABI VERSION changed in OE, usually we should remove the TMPDIR and rebuild when seeing this error, but it's not enough for Toradex builds, since we have split DEPLOY_DIR out of TMPDIR, so we should also check the ABI VERSION change in DEPLOY_DIR, or else it might not comply the OE layer. We should warn the end users about this risk, let's add a toradex sanity check bbclass for that. We can also add some other basic Toradex specific sanity checks, for instance, for fitimage, the end users must inherit toradex-fitimage rather than kernel-fitimage. Related-to: ELB-3944 Signed-off-by: Ming Liu <ming.liu@toradex.com> (cherry picked from commit 943f7da5a1cbbf695c3385b59e33aaea0c87904c)
Diffstat (limited to 'recipes-core')
0 files changed, 0 insertions, 0 deletions