>-----Original Message----- >From: Richard Purdie <[email protected]> >Sent: 04 January 2021 10:28 >To: Diego Sueiro <[email protected]>; openembedded- >[email protected] >Cc: nd <[email protected]> >Subject: Re: [OE-core] [PATCH v2] u-boot: add /boot and ${sysconfdir} to >SYSROOT_DIRS > >On Mon, 2021-01-04 at 08:30 +0000, Diego Sueiro wrote: >> Since do_install is shipping files to /boot and ${sysconfdir}, we can >> include these dirs to SYSROOT_DIRS and allow recipes which depend on >> u-boot to use its installed artifacts from RECIPE_SYSROOT instead of >> DEPLOY_DIR_IMAGE. >> >> Signed-off-by: Diego Sueiro <[email protected]> >> --- >> meta/recipes-bsp/u-boot/u-boot.inc | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/meta/recipes-bsp/u-boot/u-boot.inc b/meta/recipes-bsp/u- >> boot/u-boot.inc index 251178db33..c53bcd05cc 100644 >> --- a/meta/recipes-bsp/u-boot/u-boot.inc >> +++ b/meta/recipes-bsp/u-boot/u-boot.inc >> @@ -266,6 +266,8 @@ FILES_${PN}-env = " \ >> " >> >> FILES_${PN} = "/boot ${datadir}" >> +SYSROOT_DIRS += "/boot ${sysconfdir}" >> + >> RDEPENDS_${PN} += "${PN}-env" >> >> do_deploy () { > >I think I did ask about this on irc but we never managed to discuss. > >I'm a bit worried about this creating confusion about where files are placed >(deploy or sysroot). I particularly want to avoid placing files in both. > >Are these files in /boot normally available in the rootfs at this location? If >so, >the patch probably makes sense but if not, I think its creating disparity >between the target filesystem and the build one and I'm a lot more reluctant >to do that. > >Cheers, > >Richard
Hi Richard, Sorry, I missed your message in the IRC and was on holidays just returning today. For example, in trusted-firmware-a recipe in meta-arm (http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc), we have an option to include the u-boot binary (as BL33) in the FIP image. And this is achieved by passing the DEPLOY_DIR_IMAGE path. The idea for using the SYSROOT_DIRS is to not depend on u-boot:do_deploy in order to be able to use its generated artifacts. I'm just trying to follow the recommendation listed in the manual: https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#new-sharing-files-between-recipes. Note that some of these artifacts are not expected to be included in the filesystem. In meta-arm, we are using the SYSROOT_DIRS approach for other firmware related recipes to share files between them. We had some situations (which I don't remember exactly) where dependency cycles occurred between do_deploy tasks when trying to signing or creating wic images, and by using the combination of SYSROOT_DIRS and DEPENDS we managed to overcome these issues.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#146348): https://lists.openembedded.org/g/openembedded-core/message/146348 Mute This Topic: https://lists.openembedded.org/mt/79420282/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
