> mkdir ~/develop > cd ~/develop > cvs co source > cvs co lib/windows
> cd ~/develop/source > foreach i (`find . -name '*\.ds?'`) > echo $i > to_dos $i $i > endSometimes you want to get updated project files from cvs:
> cd ~/develop/source > foreach i (`find . -name '*\.ds?'`) > echo $i > rm $i > cvs update $i > to_dos $i $i > end
> cd ~/develop/source > make debugIf you only want to recompile part of blender you can speed things up by doing:
> cd ~/develop/source > (cd blender/src ; make debug) && make debuglinkIf you want to speed thing up further, make sure that NAN_OBJDIR points to a local disk:
> setenv NAN_OBJDIR //nana04/cygwin/home/frank/obj - or - > setenv NAN_OBJDIR //win2k/unix/home/frank/obj
Because we don't want Visual to compile blender for us, we have to change some settings:
Press Alt-F7 Press the Debug tab make sure that 'Executable for debug session' points to the blenderdynamic.exe you created from within cygwin (typically: $NAN_OBJDIR/windows/debug/blenderdynamic.exe)When you start a debug session with F5, Visual asks you if you want to rebuild certain files. Select no and start debugging.
WARNING: Visual C++ writes dos-formatted text files. Convert them before you do a cvs commit by doing a:
> to_unix myfile.c myfile.cSometimes you lose debugging information because you removed a directory from cvs and did a cvs update. What helps is:
> ssh server (fw-adm) > cd develop/source > rm `find . -name 'vc60.*'`) > logout > telnet win2k (nana04) > rm -rf $NAN_OBJDIR/windows > cd develop/source > make debug