Hi Erich, >>If you change the config, the safest way (I'm going from memory here, I >>didn't double-check this) would be to do >> >>$ ./buildtool.pl srcclean busybox >>$ ./buildtool.pl build busybox > > > I am afraid this will erase my modifications. No, it won't, unless you're making the modifications in the extracted sources (instead of in your apps-checkout). If you make your changes in the checkout of "apps", no buildtool command will be able to erase those. If you're talking about changes that you are currently making (because you're still working on it), then yes, you're right - but for those kinds of changes, not being able to track upstream changes is no big deal (since, you would copy them to your apps checkout after you've confirmed that things work - that's exactly why buildtool has that "don't overwrite files" config-setting - it's extremely annoying to have buildtool trash a file that one has just spent all evening on...).
One thing to keep in mind - do not make changes to the extracted sources (since yes, those will be deleted/overwritten with buildtool). Whatever changes you need to make, make them either in the files dowloaded (if, for example, it's a config file stored in CVS) or via a patch, that's applied via the buildtool.mk file. Directly messing with the config-files/makefiles/whatever is exactly what buildtool is meant to avoid (since it's hard to reproduce those changes). I agree that it makes things a little harder while developing, but that's the way it is. What I usually do is to make the changes I need directly in the extracted source, generate a patch from that, add the patch to buildtool.cfg and buildtool.mk and run "srcclean" and "build". Smaller changes can also be done directly from the buildtool.mk file, using perl or sed hacks. Martin _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
