This page will explain the 3 main steps to setting up
SFA: environment, check out, and compilation. Enjoy!
Environment and Path
The first thing you will need to do is set up several
environment variables and your path. The following is from a small
file that I source every time I log in:
setenv CVSROOT :ext:mruser@grainland.cs.uregina.ca:/u/mruser/CVSHOME
setenv SFAHOME <path to sfa home directory
on your machine>
setenv MRHOME $SFAHOME/MR.1.4.3
setenv MRPATH $MRHOME/etc
set path = ( $path $SFAHOME/bin $MRHOME/bin )
Your SFAHOME should be where SFA is located on your machine.
CVSROOT, MRHOME and MRPATH should be OK the way I have them listed here.
They are crucial for getting SFA to work properly.
Checking out/Updating SFA files.
This is a fairly simple process. Once you have access to the CVS server, go to the directory you will be using for your copy and type the following:
cvs checkout ui
cvs checkout rewrite
If you already have SFA and need to update your files...type:
cvs update ui
cvs update rewrite
Pretty straight forward, huh?
Compilation:
The main issue in compilation is as to whether or not you will be using the MR setup. In each of the makefiles there is a line near the stating:
# MR_ISOLATE=TRUE
If you uncomment this line in each of the makefiles and
rebuild everything MR will NOT be compiled in with SFA.
The logic in the makefiles that decides wehter or not
to compile in MR uses gmake logic. If
you are not already using gmake to build SFA
you will need to switch.
etc.
So by now you should have a) your environment and paths set up AND b) two directories of SFA files: rewrite and ui. Now, you will need to go into each directory and compile SFA.
*** NOTE *** Make sure you compile the rewrite directory FIRST since it creates a library that the ui code will link to!!!
Please take heed of the notes on compilation pertaining to gmake and MR. Once everything is compiled...go into the ui directory and type: sfa-ui (the name of the executable). You should be ready to go. Have fun!!