From BlenderWiki

Jump to: navigation, search

[edit] Obtaining CVS

[edit] Windows specific instructions for obtaining CVS

If you are using Windows you should download a Windows specific CVS client:

  • TortoiseCVS is a good choice as it is a Windows Explorer (shell) extension.
    Once you have installed TortoiseCVS you will want to add it to your path. To do this right click My Computer, then click Properties. Click the Advanced tab and then click Environment Variables. Add ;c:\Program Files\TortoiseCVS to the PATH variable.
  • CvsGui aka WinCVS Runs on Windows, Mac, and any Free Unix. If you want a fully featured front end, this is the one to choose.
  • cvsnt for Windows cmd command line.
  • cvs under Cygwin generally works but Cygwin users should beware of file permission issues.
    (In Windows executables are designated by filename extension. Programs not native to Windows (eg, Cygwin) may not trigger Windows Explorer (the Windows shell) to mark the file as an executable. This is true for Subversion under Cygwin also. To mark a file as an executable, copy it in Windows Explorer. Caveat Emptor.)

Windows users may also want to obtain gnupatch. TortiseCVS includes a patch program. Unfortunately, some of the build systems under Windows can have issues with long pathnames. This used to be true of Scons. It is recomended you create a directory C:\bf-blender and checkout the modules inside of this directory. The blender source code does not need to reside on the C:\ drive, so put it wherever you like, just keep the initial path short (and without spaces).

[edit] CVS GUI options on other platforms

Notable CVS options on other platforms include:

  • XCode on Mac OS X integrates CVS and you can now generate XCode blender projects with CMake!
  • KDevelop3 for KDE also handles CVS.
  • CvsGui aka WinCVS If you want a fully featured front end, this is the one to choose. CvsGUI, has versions for Windows, Gnome/Linux and OSX
  • Cervisia, a KDE CVS Client

See CVS Usage for instructions on using CVS


[edit] Checking out the bf-blender source tree

Once you have CVS installed, it is time to cvs checkout the source. Navigate to http://projects.blender.org and click on the Offical Blender Release project. This is where most of the development happens. Click on the CVS tab at the top of the page. It has directions for logging into the blender CVS server and checking out the blender modules.

Check out the bf-blender/blender module and only the relevant part of the bf-blender/lib module, unless you plan to cross compile. If you check out the other platform directories in the lib directory, you'll just waste about 70MiB of disk space. Use the ViewCVS link to see what platform subdirectories are under the bf-blender/lib module and select the match for your platform. Or just look at the possibly outdated list below.

  • The bf-blender/blender module contains the blender source code proper.
  • The bf-blender/lib module contains external, platform specific, library dependencies in binary form for easy compiling.

On Windows you will want to use bf-blender/lib/windows. Mac OS X users should check out the relevant darwin-<version> directories.

So, for Windows: (Notice the path separator change because of Windows: / to \) 

 mkdir c:\bf-blender
 cd c:\bf-blender

Then, checkout the sources with CVS using the following commands: 

 cvs -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender login
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co blender
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co lib/windows

For Mac OS X on PowerPC, open Terminal (Applications > Utilities > Terminal): 

 mkdir ~/Projects/bf-blender
 cd ~/Projects/bf-blender

Then checkout the blender sources with the following commands: 

 cvs -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender login
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co blender
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co lib/darwin-6.1-powerpc
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co lib/darwin-8.0.0-powerpc
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co lib/darwin-8.7.0-powerpc
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co lib/darwin-8.8.0-powerpc

For Mac OS X on Intel, open Terminal (Applications > Utilities > Terminal): 

 mkdir ~/Projects/bf-blender
 cd ~/Projects/bf-blender

Then checkout the blender sources with the following commands: 

 cvs -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender login
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co blender
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co lib/darwin-8.x.i386

For Linux you will need to know what version of glibc/libc your system is using. To find out what version of libc/glibc, at a shell prompt, type: 

 /lib/libc.so.6

Once you know the version, use that to check out the appropriate bf-blender/lib/linux* directory: 

 mkdir ~/Projects/bf-blender
 cd ~/Projects/bf-blender

Then checkout the sources with the following commands: 

 cvs -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender login
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co blender
 cvs -z3 -d:pserver:anonymous@cvs.blender.org:/cvsroot/bf-blender co lib/linux-glibc$VERSION-$ARCH

For reference, the current directories in bf-blender/lib/: 

darwin-6.1-powerpc/
darwin-8.0.0-powerpc/
darwin-8.7.0-powerpc/
darwin-8.8.0-powerpc/
darwin-8.x.i386/
irix-6.5-mips/
linux-glibc2.2.5-i386/
linux-glibc2.3.1-i386/
linux-glibc2.3.1-powerpc/
solaris-2.8-sparc/
tests/
windows/

[edit] CVS Usage

There are all kinds of great tutorials on using CVS. If one of the CVS Mini Tutorials, online help: man cvs, or cvs help does not answer your question refer to the canonical reference manual for CVS. CVS commands you will use quite frequently are:

  • cvs update: Use this to bring your tree up to date with the main tree. It will also

summarize what files have changed in your working directory if any. Common options for cvs update are cvs -q update -d which causes update to behave more like checkout (it still merges and honors your local changes, but will replace missing files).

  • cvs diff: Use this to look at differences between files.
  • cvs commit: Once you become an offical blender developer, you use this command to commit your changes to the main bf-blender tree. Until then, create patches and submit those patches to the Patch Tracker. You will probably want to promote your patch on irc.freenode.net #blendercoders, or on the mailing lists.

It's also useful to create a .cvsrc file to alias CVS commands. Your .cvsrc file contains common flags you will want to pass to the various cvs commands.

Retrieved from "http://wiki.blender.org/index.php/Attic:Dev:Doc/Managing_CVS"