Demi Marie Obenour <demiobenour@gmail.com> writes:
I spent hours figuring out why files were not found in the VMs. Turns out that 'make' was no rerunning the script to rebuild the root filesystem.
Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com> --- img/app/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/img/app/Makefile b/img/app/Makefile index f818e914908038cdf14532d1b7b44a1c37c1b270..d81337f99e2e83cf03ac73b9fc96fae6ce118537 100644 --- a/img/app/Makefile +++ b/img/app/Makefile @@ -71,7 +71,7 @@ build/fifo: build/empty: mkdir -p $@
-build/rootfs.erofs: ../../scripts/make-erofs.sh $(VM_FILES) $(VM_BUILD_FILES) build/empty build/fifo +build/rootfs.erofs: ../../scripts/make-erofs.sh $(VM_FILES) $(VM_BUILD_FILES) build/empty build/fifo Makefile ( \ cat $$PACKAGES ;\ for file in $(VM_FILES) $(VM_LINKS); do printf '%s\n%s\n' $$file $$file; done ;\
I'm not sure about this one — there's no reason this target in particular needs to depend on the Makefile, but others don't. A change to the Makefile could cause any target to be outdated. I think it's just a normal part of working with make that you have to do a clean build after changing the Makefile.