Hi Joshua, Sorry for the delay.
> FYI, I started working on this in oe-contrib/jpew/spdx-deploy > (https://git.openembedded.org/openembedded-core-contrib/log/?h=jpew/spdx-deploy) > if you can try it out and make sure it will allow you to do what you > want, I would appreciate it I've done some tests, and it does solve these cases mostly. However, I got errors in the case of Heteorenous Multi-Processing. Some packages are built for both cores, and the build tries to generate two SBOMs with the same name. For instance, on the Verdin AM62 the U-Boot recipe fails because U-Boot is built for both the Cortex A53 and Cortex R5, and both SBOMs are named u-boot-toradex-deploy-sbom.spdx.json: ERROR: mc:k3r5:u-boot-toradex-1_mainline-r0 do_create_deploy_sbom: Recipe u-boot-toradex is trying to install files into a shared area when those files already exist. The files and the manifests listing them are: build/deploy/images/verdin-am62/u-boot-toradex-deploy-sbom.spdx.json (not matched to any task) Please adjust the recipes so only one recipe provides a given file. This could be solved if each recipe could define a custom name for its deploy SBoM. Then the name could be altered for different cortexes in the same build I made a small patch on top of your branch, adding a SPDX_DEPLOY_SBOM_NAME variable that allows this (similar to the existing SPDX_RECIPE_SBOM_NAME), I'll send it in reply to this email. Let me know what you think. Kind regards, Leonardo
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#238368): https://lists.openembedded.org/g/openembedded-core/message/238368 Mute This Topic: https://lists.openembedded.org/mt/119502448/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
