Differences between revisions 15 and 31 (spanning 16 versions)
Revision 15 as of 2010-03-02 11:08:00
Size: 1473
Comment:
Revision 31 as of 2012-05-10 12:26:34
Size: 2194
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
First, [[https://surfer.nmr.mgh.harvard.edu/opensourcereg.html|register to receive the password to this repository]]. This registration form includes [[FreeSurferSoftwareLicense|the license terms]]. Note: tkmedit, tksurfer and tkregister2 are covered under [[FreeSurferCorTechsLicense|the CorTechs license]].

You will need about 7GB of disk space, and the download will likely take several hours.
Line 4: Line 7:
Line 7: Line 11:
press Enter when prompted for the password (there isn't one). Then type: You will supply the password received via email after completing the registration form. Then type:
Line 9: Line 14:
cvs -d :pserver:anonymous@fsvm.nmr.mgh.harvard.edu:/usr/fscvsroot checkout dev cvs -d :pserver:anonymous@fsvm.nmr.mgh.harvard.edu:/usr/fscvsroot checkout -P dev
Line 11: Line 16:
This will begin the download of the source-code trunk, creating a directory named 'dev'. This will begin the download of the source-code trunk, creating a directory named 'dev'.  The -P flag will purge the junk files that have been deleted from the repository over the years.
Line 13: Line 18:
To get a copy of the current 'stable' branch (the code used to build the public release), insert '-r stable4' before 'dev' in the second command, like this: To get a copy of the current 'stable' branch (the code used to build the public release but that has been internally updated with bug fixes), insert '-r stable5' before 'dev' in the second command, like this:
Line 15: Line 21:
cvs -d :pserver:anonymous@fsvm.nmr.mgh.harvard.edu:/usr/fscvsroot checkout -r stable4 dev cvs -d :pserver:anonymous@fsvm.nmr.mgh.harvard.edu:/usr/fscvsroot checkout -P -r stable5 dev
Line 17: Line 23:
Note that this will also create a directory named 'dev', so you should probably create a directory named 'stable4', cd to that, and then do the checkout. Note that this will also create a directory named 'dev', so you should probably create a directory named 'stable5', cd to that, and then do the checkout.

If you need the version used in the 5.1 public release, then use 'release_5_1_0' as the revision tag (instead of 'stable5').
Line 20: Line 28:
Line 29: Line 38:
Line 32: Line 42:

Access the read-only CVS source-code repository

First, register to receive the password to this repository. This registration form includes the license terms. Note: tkmedit, tksurfer and tkregister2 are covered under the CorTechs license.

You will need about 7GB of disk space, and the download will likely take several hours.

To check-out a copy of the main 'dev' (development) trunk, type this:

cvs -d :pserver:anonymous@fsvm.nmr.mgh.harvard.edu:/usr/fscvsroot login

You will supply the password received via email after completing the registration form. Then type:

cvs -d :pserver:anonymous@fsvm.nmr.mgh.harvard.edu:/usr/fscvsroot checkout -P dev

This will begin the download of the source-code trunk, creating a directory named 'dev'. The -P flag will purge the junk files that have been deleted from the repository over the years.

To get a copy of the current 'stable' branch (the code used to build the public release but that has been internally updated with bug fixes), insert '-r stable5' before 'dev' in the second command, like this:

cvs -d :pserver:anonymous@fsvm.nmr.mgh.harvard.edu:/usr/fscvsroot checkout -P -r stable5 dev

Note that this will also create a directory named 'dev', so you should probably create a directory named 'stable5', cd to that, and then do the checkout.

If you need the version used in the 5.1 public release, then use 'release_5_1_0' as the revision tag (instead of 'stable5').

Build instructions are found in the DevelopersGuide, but in any case, you will first need to type this:

cd dev
./setup_configure

which will setup the autoconf and automake files for your platform. You need only do this once (or whenever you change configure.in).

The DevelopersGuide will describe how to need to configure, make, and make install.

Remember that cvs will cache the location of CVSROOT (the 'pserver' string from above), so to perform an update, you need only type:

cvs update -d

See also admin notes.