On 17 Aug 2013, at 10:44, Juha Manninen wrote: > On Sat, Aug 17, 2013 at 3:40 AM, waldo kitty <wkitt...@windstream.net> wrote: >> FWIW: i learned a while back (from the lazarus list i think) to perform >> "make clean" before "svn up" because the make files may have changed and the >> new ones may not know where the old files resided... >> >> performing "make clean" first clears the existing directories... then "svn >> up" followed (possibly with another "make clean" and then) by your normal >> build flow should result in a truly clean build flow without the possibility >> of lingering old .o and/or .a build files... > > I don't think the extra "make clean" before "svn up" will really help > because the generated object files are not under revision control.
"make clean" is not about the source files. Waldo is right: you should always "make clean" (or even better: "make distclean") before updating from svn, because files may move around and then "make clean" will only clean their object and ppu files in the new locations. Jonas_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
