Automated Quick Start: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
* To create your sandbox run this command form any directory: | * To create your sandbox run this command form any directory: | ||
<pre> | |||
% /map/gfx0/tools/linux/install_linux/bin/setup/new.g.user.sh | % /map/gfx0/tools/linux/install_linux/bin/setup/new.g.user.sh | ||
NOTE: Creating a sandbox in the directory: /map/gfx0/users/bluto/ | NOTE: Creating a sandbox in the directory: /map/gfx0/users/bluto/ | ||
| Line 42: | Line 43: | ||
***** The new.g.user.sh script has successfully completed. ***** | ***** The new.g.user.sh script has successfully completed. ***** | ||
</pre> | |||
* To setup your envionment each time you login modify your default login script. First you need to know if you are running the '''tcsh''' or '''bash''' shell. | * To setup your envionment each time you login modify your default login script. First you need to know if you are running the '''tcsh''' or '''bash''' shell. | ||
Revision as of 16:22, 15 September 2010
These are instructions using a script to set up a typical sandbox at Brown using Linux. Even if you intend to develop on a different platform such as Windows you should initially get set up on Linux. If you need more explicit instructions or you want a more complex setup then revert back to the full instructions.
- To create your sandbox run this command form any directory:
% /map/gfx0/tools/linux/install_linux/bin/setup/new.g.user.sh
NOTE: Creating a sandbox in the directory: /map/gfx0/users/bluto/
NOTE: Copying previously installed Brown linux projects ...
NOTE: ... done copying linux projects.
NOTE: Copying previously installed Brown Windows projects ...
NOTE: ... done copying Windows projects.
NOTE: Checking out the common/ directory from CVS ...
NOTE: ... The common/ directory was succefully checked out from CVS.
NOTE: Building the common/utility/ directory ...
NOTE: ... The common/utility/ directory successfully built.
Your work area was created in: /map/gfx0/users/bluto/
Source code for projects you create and any Brown projects
you want to check out from the CVS repository will go here:
drwxrwsr-x 2 bluto graphics 4096 Sep 15 11:18 /map/gfx0/users/bluto/project
Your private copy of shared Brown source code was checked out to:
drwxrwsr-x 15 bluto graphics 4096 Sep 15 11:20 /map/gfx0/users/bluto/common
Your private copy of previously installed programs and libraries
written at Brown are here:
drwxrwsr-x 5 bluto graphics 4096 Sep 15 11:18 /map/gfx0/users/bluto/install_linux
drwxr-sr-x 6 bluto graphics 4096 Sep 15 11:19 /map/gfx0/users/bluto/install_WIN32
Your projects can access third party software that has been
previously downloaded and installed here:
/map/gfx0/tools/linux/import/afni /map/gfx0/tools/linux/import/gsl
/map/gfx0/tools/linux/import/artoolkit /map/gfx0/tools/linux/import/make
/map/gfx0/tools/linux/import/blitz /map/gfx0/tools/linux/import/mricron
/map/gfx0/tools/linux/import/build /map/gfx0/tools/linux/import/nifti
/map/gfx0/tools/linux/import/camino /map/gfx0/tools/linux/import/qt
/map/gfx0/tools/linux/import/cg /map/gfx0/tools/linux/import/scalable
/map/gfx0/tools/linux/import/dtk /map/gfx0/tools/linux/import/sdl
/map/gfx0/tools/linux/import/ftgl /map/gfx0/tools/linux/import/vrpn
/map/gfx0/tools/linux/import/g3d /map/gfx0/tools/linux/import/xerces
/map/gfx0/tools/linux/import/glut /map/gfx0/tools/linux/import/xg3d
***** The new.g.user.sh script has successfully completed. *****
- To setup your envionment each time you login modify your default login script. First you need to know if you are running the tcsh or bash shell.
> finger $USER
The "Shell:" field in the output will be either /bin/tcsh or /bin/bash. If you are running tcsh then edit $HOME/.cshrc and add this line at the end:
source /map/gfx0/tools/linux/install_linux/bin/setup/g.login.csh
If you are running bash then instead edit $HOME/.bashrc and add this line at the end:
source /map/gfx0/tools/linux/install_linux/bin/setup/g.login.sh
You can check your results by logging out and then logging in again. This command will list your environment variables.
> printenv
It will list all your variables, but you should see that these variables are set:
CVSROOT GARCH G GTO GROOT G_IMPORT G_COMPILER