Closed asac closed 6 months ago
well, that is for generating rockchip specified update image. you can remove it(and some other later functions as well)
well, that is for generating rockchip specified update image. you can remove it(and some other later functions as well)
OK, I think https://github.com/JeffyCN/meta-rockchip/commit/a74e2fa9934279d27fc6b223cae8ac43fa63ef6f fixes this one as well. Thanks!
In scartgap, when building initramfs the machine conf level POSTPROCESS command:
IMAGE_POSTPROCESS_COMMAND:append = " link_rootfs_image;" link_rootfs_image() { ln -sf "${IMAGE_LINK_NAME}.${RK_ROOTFS_TYPE}" \ "${IMGDEPLOYDIR}/rootfs.img" }
Creates a conflict in deploy dir with the actual images (e.g. core-image-minimal).
Is that link really necessary? Who is the consumer of that rootfs.img file? (I couldnt find one in meta-*). Can we do without this rootfs.img or prefix it with the image name?
I guess the same will be seen later with update.img and maybe the /latest dir link.