Closed hnez closed 11 months ago
The seond one you could also check by inspecting the DEPENDS
variable in the output of bitbake -e emmc-image
.
Edit: Ah, the do_genimage[depends] += "${GENIMAGE_ROOTFS_IMAGE}:do_image_complete"
should do the trick, as long as the do_image_complete
task in lxatac-core-image-base creates the ext4 image.
Seeing the core
and base
in the image name always irks me a little bit, as it is not very core-y or base-y with all the development tools.
We should define an actual minimal image in the future and derive our full image with all the tools from there.
(But that's not something we should do or discuss here)
As it turns out the rootfs was not resized to match the partition as we wanted it to.
Newer systemd
versions ship a systemd-growfs-root.service
that can help us here, so I've backported it for now.
Hopefully we can throw away the backport very soon.
This PR does three things:
partition end
workaround that was removed in #62 (but without changing other things like addingfill=true
)..tar
.Things I am not too sure about:
lxatac-core-image-base-lxatac.ext4
in thegenimage.config
?lxatac-core-image-base-lxatac.ext4
being present. The first version of this PR usedGENIMAGE_ROOTFS_IMAGE
to specify this dependency. This is not quite correct. Thegenimage.bbclass
documentation states quite clearly that this variable is intended for.tar
images that should be unpacked and re-packed into a filesystem image (thx @ejoerns ). Instead I've now set up the dependencies explicitly.The last one I can test, for the rest I would be glad about some feedback.
¹ Which is the end of the image but has nothing to do with the end of the device the image is written to, where the header should be.