On Mon, Feb 10, 2020 at 11:22 AM Nicolas Dechesne <[email protected]> wrote: > you use do_install() to install any content that you need to be added to your > rootfs/image, as you said. the content of $D will end up in a binary package > (rpm, deb, or ipk), and that package might eventually be installed into an > image, which means that the content of $D will be 'added' to an image. > > do_deploy() does not exist by default, you need inherit deploy class. > You use do_deploy() to 'install' files/content in $DEPLOY_DIR_IMAGE, e.g. the > same folder where your image is deployed. There is for example a do_deploy() > task for an image recipe. When you use > do_deploy() you do not create a binary package, but directly copy content in > $DEPLOY_DIR_IMAGE. You should use $DEPLOYDIR is your recipe, which is a > 'local' folder for your recipe to copy the content you want to deploy. OE > will take care of the copy from $DEPLOYDIR to $DEPLOY_DIR_IMAGE (it's > optimized to work with sstate-cache).
Thanks, that destinction makes it a lot clearer and sounds pretty clear to me. It also explains why we saw do_deploy a lot last week since we we're working with our bootloaders, which generally need to end up next to the image (same with e.g. U-Boot tools). Best regards, Olli
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48327): https://lists.yoctoproject.org/g/yocto/message/48327 Mute This Topic: https://lists.yoctoproject.org/mt/71133874/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
