Differences between revisions 30 and 33 (spanning 3 versions)
⇤ ← Revision 30 as of 2012-02-01 11:45:49 →
Size: 2103
Editor: NickSchmansky
Comment:
← Revision 33 as of 2019-02-03 13:16:06 → ⇥
Size: 0
Editor: AndrewHoopes
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Access the read-only CVS source-code repository =
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]].

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 [[ReadOnlyCVSadmin|admin notes]].