On Sun, 2026-08-02 at 21:52 +0200, Adrian Freihofer via lists.openembedded.org wrote: > From: Adrian Freihofer <[email protected]> > > There seems to be still some corner cases where the qemuboot.conf file > is not deployed reliably. > > Previously do_write_qemuboot_conf wrote its output into IMGDEPLOYDIR, > which is shared with do_image_complete. The conf file only reached > DEPLOY_DIR_IMAGE when do_image_complete ran, so for example running: > > bitbake <image> -c write_qemuboot_conf --force > > had no visible effect on the deployed conf. > > Introduce a dedicated QEMUBOOTCONFDEPLOYDIR and register > do_write_qemuboot_conf as a proper SSTATE task with its own > sstate-inputdirs/sstate-outputdirs pair pointing at DEPLOY_DIR_IMAGE. > A matching do_write_qemuboot_conf_setscene task handles sstate restores.
Which issue is this fixing? I think this should be running after do_image, before do_image_complete, which is when the files in IMGDEPLOYDIR are captured/handled and that is probably the real bug/slightly easier fix... Making that change would make it match the other image artefact generation pieces. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#242587): https://lists.openembedded.org/g/openembedded-core/message/242587 Mute This Topic: https://lists.openembedded.org/mt/120567641/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
