I'm just wondering - what is the expectation/common use... When I'm building up images, I use "make image" all the time. It's fast, and great when I'm just making some minor changes in the romfs/ directory. When I'm testing things out, I just edit scripts (like /etc/rc) in the romfs/ directory directly, and then just "make image". Works like a charm.
However, a problem occurs if I need to do a 'make' in the dist (to rebuild some missing app), since my vendors/*/*/Makefile includes a: $(ROMFSINST) /etc/rc (like 150 other Makefiles) and romfs-inst.sh clobbers overtop of my local changes in romfs/etc/rc with the one from vendors/*/*/rc I could just stop making changes in the romfs/ directory (and do everything in ./vendors/*/* - which I don't do today - since I don't want to check anything into cvs/svn by mistake - and builds would take longer), or I could add a new flag to romfs-inst.sh (which would not copy the file if it already existed) - which would cause problems for people who expect today's behaviour.... Is ./romfs suppost to be the output of everything? (and people shouldn't be editing things there?) _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
