Quick Start for CIT Users - Revision history

Brad Berg: /* Set Environment Variables */

2011-06-22T18:27:32Z

Set Environment Variables

← Older revision		Revision as of 18:27, 22 June 2011
Line 28:		Line 28:

	<pre>		<pre>
	Linux Windows OSX		Linux Windows OSX

	gcc2 - gcc version 2.95 cl6 - Microsoft Studio version 6 gcc4 - gcc version 4.2		gcc2 - gcc version 2.95 cl6 - Microsoft Studio version 6 gcc4 - gcc version 4.2
	gcc3 - gcc version 3.4 cl8 - Microsoft Studio version 8 (2005)		gcc3 - gcc version 3.4 cl8 - Microsoft Studio version 8 (2005)
	gcc4 - gcc version 4.1 cl9 - Microsoft Studio version 9 (2008)		gcc4 - gcc version 4.1 cl9 - Microsoft Studio version 9 (2008)
	</pre>		</pre>

Brad Berg: /* Set Environment Variables */

2011-06-22T18:26:48Z

Set Environment Variables

← Older revision		Revision as of 18:26, 22 June 2011
Line 24:		Line 24:


	The '''G_COMPILER''' variable is set to the compiler you want to work with. This may change depending on project requirements. Most projects will build if you set it to '''gcc4''' on Linux and '''cl9''' on Windows. ~~Supported~~ settings are:		The '''G_COMPILER''' variable is set to the compiler you want to work with. This may change depending on project requirements. Most projects will build if you set it to '''gcc4''' on Linux and '''cl9''' on Windows. Note that at Brown gcc version 3.4 is no longer supported on Debian. Current settings are:


	<pre>		<pre>
	Linux Windows		Linux Windows OSX

	gcc2 - gcc version 2.95 cl6 - Microsoft Studio version 6		gcc2 - gcc version 2.95 cl6 - Microsoft Studio version 6 gcc4 - gcc version 4.2
	gcc3 - gcc version 3.4 cl8 - Microsoft Studio version 8 (2005)		gcc3 - gcc version 3.4 cl8 - Microsoft Studio version 8 (2005)
	gcc4 - gcc version 4.1 cl9 - Microsoft Studio version 9 (2008)		gcc4 - gcc version 4.1 cl9 - Microsoft Studio version 9 (2008)
Line 39:		Line 39:

	umask 002		umask 002


			Note that imported software packages may require additional environment variable settings when your project uses them. You will need to read the documentation for each package to see how it is set up.

			The NAG library is supported by tStaff for Linux. If you use the NAG library you will need to set:

			LM_LICENSE_FILE /cfarm/nag/license.dat:/com/nag/license.dat
			NAG_KUSARI_FILE /com/nag/kusari.dat

	== Get the Build System ==		== Get the Build System ==

Brad Berg: /* Get Third Party Software */

2011-06-22T17:49:19Z

Get Third Party Software

← Older revision		Revision as of 17:49, 22 June 2011
Line 106:		Line 106:
	If there is a copy there that looks like one you need you can first try it and if it doesn't work then download and install your own copy. Copy the packages you need from the public area to your own:		If there is a copy there that looks like one you need you can first try it and if it doesn't work then download and install your own copy. Copy the packages you need from the public area to your own:

	> copy -R /research/graphics/tools/linux/import/<Package> /~~map~~/~~gfx0~~/users/$USER/import		> copy -R /research/graphics/tools/linux/import/<Package> /research/graphics/users/$USER/import

	== Build a Project on Windows ==		== Build a Project on Windows ==

Brad Berg: /* Build a Project on Windows */

2011-06-22T17:48:29Z

Build a Project on Windows

← Older revision		Revision as of 17:48, 22 June 2011
Line 112:		Line 112:
	Windows users need a few Unix utilities installed to build projects. You can check these out of cvs on a Linux computer with:		Windows users need a few Unix utilities installed to build projects. You can check these out of cvs on a Linux computer with:

	> cd /~~map~~/~~gfx0~~/users/$USER		> cd /research/graphics/users/$USER
	> cvs co import/make # Check out the utilities on a Linux computer.		> cvs co import/make # Check out the utilities on a Linux computer.
	:		:
	> ls /~~map~~/~~gfx0~~/users/$USER/import/make/g.utility_1.0/		> ls /research/graphics/users/$USER/import/make/g.utility_1.0/
	CVS/ cp.exe* echo.exe* libiconv2.dll make.exe* mkdir_gnu.exe*		CVS/ cp.exe* echo.exe* libiconv2.dll make.exe* mkdir_gnu.exe*
	READ_ME.txt diff.exe* false.exe* libintl3.dll mkdir.exe* rm.exe*		READ_ME.txt diff.exe* false.exe* libintl3.dll mkdir.exe* rm.exe*

	Now switch to the Windows computer. You will need to add the path to '''g.utility_1.0\''' to the front of your Windows '''PATH''' environment variable. On Windows the path is '''"Y:\~~map~~\~~gfx0~~\users\<User ID>\import\make\g.utility_1.0"''' After it is set verify that you can run these utilities from the command shell of your choosing. The native Windows command shell is '''cmd.exe'''.		Now switch to the Windows computer. You will need to add the path to '''g.utility_1.0\''' to the front of your Windows '''PATH''' environment variable. On Windows the path is '''"Y:\research\graphics\users\<User ID>\import\make\g.utility_1.0"''' After it is set verify that you can run these utilities from the command shell of your choosing. The native Windows command shell is '''cmd.exe'''.

	If you've not already done so, set your Windows environment variables according to the section "Setting Environment Variables". To see if you can build software run the 'cmd.exe' shell and try:		If you've not already done so, set your Windows environment variables according to the section "Setting Environment Variables". To see if you can build software run the 'cmd.exe' shell and try:

	> cd/d Y:\~~map~~\~~gfx0~~\users\<User ID>\common\utility		> cd/d Y:\research\graphics\users\<User ID>\common\utility
	> make all # Build utilities on Windows.		> make all # Build utilities on Windows.
	> make install # Install them to: install_WIN32/		> make install # Install them to: install_WIN32/

	Finally inspect '''Y:\~~map~~\~~gfx0~~\users\<User ID>\install_WIN32''' to ensure it was properly populated.		Finally inspect '''Y:\research\graphics\users\<User ID>\install_WIN32''' to ensure it was properly populated.

Brad Berg: /* Get Third Party Software */

2011-06-22T17:47:22Z

Get Third Party Software

← Older revision		Revision as of 17:47, 22 June 2011
Line 94:		Line 94:
	Many projects depend on downloaded software. Create the '''import/''' directory in your sandbox where downloaded software is installed.		Many projects depend on downloaded software. Create the '''import/''' directory in your sandbox where downloaded software is installed.

	> mkdir /~~map~~/~~gfx0~~/users/$USER/import		> mkdir /research/graphics/users/$USER/import


Line 101:		Line 101:
	To see how the '''import/''' directory is organized and what packages are installed browse the public installations:		To see how the '''import/''' directory is organized and what packages are installed browse the public installations:

	/~~map~~/~~gfx0~~/tools/linux/import/...		/research/graphics/tools/linux/import/...


	If there is a copy there that looks like one you need you can first try it and if it doesn't work then download and install your own copy. Copy the packages you need from the public area to your own:		If there is a copy there that looks like one you need you can first try it and if it doesn't work then download and install your own copy. Copy the packages you need from the public area to your own:

	> copy -R /~~map~~/~~gfx0~~/tools/linux/import/<Package> /map/gfx0/users/$USER/import		> copy -R /research/graphics/tools/linux/import/<Package> /map/gfx0/users/$USER/import


	== Build a Project on Windows ==		== Build a Project on Windows ==

Brad Berg: /* Get Project Code */

2011-06-22T17:46:55Z

Get Project Code

← Older revision		Revision as of 17:46, 22 June 2011
Line 77:		Line 77:
	Project code is kept in CVS under the '''project/''' directory. Note that inside your sandbox project code can be kept in any directory and you can have multiple versions of projects in different directories. If you want to work with a project already in CVS then you can check it out now.		Project code is kept in CVS under the '''project/''' directory. Note that inside your sandbox project code can be kept in any directory and you can have multiple versions of projects in different directories. If you want to work with a project already in CVS then you can check it out now.

	> cd /~~map~~/~~gfx0~~/users/$USER		> cd /research/graphics/users/$USER
	> cvs co project/<Project Name>		> cvs co project/<Project Name>

Line 83:		Line 83:
	If you want to create a new project then make a new directory for it in your sandbox.		If you want to create a new project then make a new directory for it in your sandbox.

	> mkdir -p /~~map~~/~~gfx0~~/users/$USER/project/<Project Name>		> mkdir -p /research/graphics/users/$USER/project/<Project Name>

Brad Berg: /* Get the Build System */

2011-06-22T17:46:28Z

Get the Build System

← Older revision		Revision as of 17:46, 22 June 2011
Line 44:		Line 44:
	The '''common/''' directory has the build make files and shared programs and libraries written at Brown. You only need the '''common/build/''' directory to develop programs, but since you probably will eventually want other common code just check the whole directory out.		The '''common/''' directory has the build make files and shared programs and libraries written at Brown. You only need the '''common/build/''' directory to develop programs, but since you probably will eventually want other common code just check the whole directory out.

	> cd /~~map~~/~~gfx0~~/users/$USER		> cd /research/graphics/users/$USER
	> cvs co common		> cvs co common

Line 50:		Line 50:
	When software is installed (via the "make install" command) it is copied to the install directory. There is an install directory for each platform. Create install directories for Linux and Windows with:		When software is installed (via the "make install" command) it is copied to the install directory. There is an install directory for each platform. Create install directories for Linux and Windows with:

	> mkdir /~~map~~/~~gfx0~~/users/$USER/install_linux		> mkdir /research/graphics/users/$USER/install_linux
	> mkdir /~~map~~/~~gfx0~~/users/$USER/install_WIN32		> mkdir /research/graphics/users/$USER/install_WIN32


Line 63:		Line 63:
	Try a simple build to see that everything is properly set up.		Try a simple build to see that everything is properly set up.

	> cd /~~map~~/~~gfx0~~/users/$USER/common/utility		> cd /research/graphics/users/$USER/common/utility
	> make all # Build the utilities.		> make all # Build the utilities.
	> make install # Install the utilities.		> make install # Install the utilities.
Line 71:		Line 71:
	This should populate the install directory. Take a look with:		This should populate the install directory. Take a look with:

	> ls /~~map~~/~~gfx0~~/users/$USER/install_linux//		> ls /research/graphics/users/$USER/install_linux//

	== Get Project Code ==		== Get Project Code ==

Brad Berg: /* Set Environment Variables */

2011-06-22T17:45:52Z

Set Environment Variables

← Older revision		Revision as of 17:45, 22 June 2011
Line 16:		Line 16:
	Linux Windows		Linux Windows

	CVSROOT /~~map~~/~~gfx0~~/cvsroot Y:\~~map~~\~~gfx0~~\cvsroot		CVSROOT /research/graphics/cvsroot Y:\research\graphics\cvsroot
	GROOT /~~map~~/~~gfx0~~ Y:\~~map~~\~~gfx0~~		GROOT /research/graphics Y:\research\graphics
	G /~~map~~/~~gfx0~~/users/$USER Y:\~~map~~\~~gfx0~~\users\<User ID>		G /research/graphics/users/$USER Y:\research\graphics\users\<User ID>
	GTO /~~map~~/~~gfx0~~/users/$USER Y:\~~map~~\~~gfx0~~\users\<User ID>		GTO /research/graphics/users/$USER Y:\research\graphics\users\<User ID>
	GARCH linux WIN32		GARCH linux WIN32
	</pre>		</pre>

Brad Berg: /* Create your Sandbox */

2011-06-22T17:44:20Z

Create your Sandbox

← Older revision		Revision as of 17:44, 22 June 2011
Line 7:		Line 7:
	> groups		> groups
	graphics grad guest # The first item must be graphics.		graphics grad guest # The first item must be graphics.
	> mkdir /~~map~~/~~gfx0~~/users/$USER		> mkdir /research/graphics/users/$USER

	== Set Environment Variables ==		== Set Environment Variables ==

Brad Berg: /* Get the Build System */

2010-05-06T19:29:11Z

Get the Build System

← Older revision		Revision as of 19:29, 6 May 2010
Line 67:		Line 67:
	> make install # Install the utilities.		> make install # Install the utilities.

			Here is a transcript for [[Building and Installing Common Components]].

	This should populate the install directory. Take a look with:		This should populate the install directory. Take a look with: