Hi Dave, Dave Festing wrote: > Juergen Beisert <jbe@...> writes: > > Where should it include it? Into the "<platform-name>/root" or into > > the images which PTXdist can create for the NAND or an SD card? > > > > Are these files part of the "rootfs"-package? About what files do > > you talk here exactly? > > Into platform-mini2440/root > > Files in daves_rootfs as per the example in 8.26 > > Should I expect ptxdist clean rootfs to also clean out my daves_rootfs > files? > > As it now doesn't work on both machines I suspect I am not doing > something I should.
Ah, the "daves_rootfs" rule file. If you want PTXdist to re-do this package and to copy your changed files again to the root filesystem you must clean this package. So, a "ptxdist clean daves_rootfs; ptxdist go" will do the expected job. PTXdist saves the project state on a per package manner. "ptxdist clean root" (where 'root' here is a special keyword and not a package name) takes effect on all package's "targetinstall" stages in the project. That is why PTXdist then goes again through all package's targetinstall stages when you type the next "ptxdist go". "ptxdist clean daves_rootfs" just removes the results of your own local package with this name. As a result, the next "ptxdist go" just re-do *all* stages in the "daves_rootfs.make" (it is faster than doing it for all packages). If you just want PTXdist to copy the files again, or to update them into an image, you also can drop the targetinstall stage of the corresponding package. "ptxdist drop daves_rootfs.targetinstall" only removes the targetinstall stage of the daves_rootfs package. The next "ptxdist go" then will *only* re-do all the steps in your daves_rootfs.make's targetinstall stage (it is the fastest way to do the job you want PTXdist to do). Hope this complicated instruction helps you to understand what happens inside PTXdist to do its job. Regards, Juergen -- Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
