Quick Start for Linux in CIT - Revision history

Brad Berg at 16:35, 19 April 2010

2010-04-19T16:35:19Z

← Older revision		Revision as of 16:35, 19 April 2010
Line 1:		Line 1:
	These are terse instructions for setting up a typical Linux sandbox at Brown. If you need more explicit instructions or you want a more complex setup then revert back to the full instructions.		These are terse instructions for setting up a typical Linux sandbox at Brown. 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.

	== Create your Sandbox ==		== Create your Sandbox ==
Line 10:		Line 10:
	== Environment Variables ==		== Environment Variables ==

	Setup your environment variables in your ~~login~~ shell.		Setup your environment variables in the login script for your shell.

	CVSROOT /map/gfx0/cvsroot		CVSROOT /map/gfx0/cvsroot

Brad Berg: /* Get Third Party Software */

2010-04-19T14:54:25Z

Get Third Party Software

← Older revision		Revision as of 14:54, 19 April 2010
Line 79:		Line 79:
	The packages you need are determined by the projects you are working on. Project documentation is the first place to check for required software. Copies of some packages are installed in a shared public area, however the public area may not have the versions your projects require and the installations may change over time without notice. The only sure fire method is to download and install the software.		The packages you need are determined by the projects you are working on. Project documentation is the first place to check for required software. Copies of some packages are installed in a shared public area, however the public area may not have the versions your projects require and the installations may change over time without notice. The only sure fire method is to download and install the software.

	To see how the import directory is organized and what packages are installed ~~look in~~ 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/...		/map/gfx0/tools/linux/import/...

Brad Berg: /* Get Project Code */

2010-04-19T14:53:13Z

Get Project Code

← Older revision		Revision as of 14:53, 19 April 2010
Line 66:		Line 66:


	You are free to organize your project within the new directory as you wish. For instructions on writing make files visit: ~~https://sourceforge.net/apps/mediawiki/vrg3d/index.php?title=Writing_Make_Files~~		You are free to organize your project within the new directory as you wish. For instructions on writing make files visit:

			https://sourceforge.net/apps/mediawiki/vrg3d/index.php?title=Writing_Make_Files

	== Get Third Party Software ==		== Get Third Party Software ==

Brad Berg: /* Get the Build System */

2010-04-19T14:52:51Z

Get the Build System

← Older revision		Revision as of 14:52, 19 April 2010
Line 42:		Line 42:


	Try to build ~~something~~ 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 /map/gfx0/users/$USER/common/utility
	> make all #		> make all #
	> make install		> make install


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

			> ls /map/gfx0/users/$USER/install_linux//

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

Brad Berg: /* Environment Variables */

2010-04-19T14:46:38Z

Environment Variables

← Older revision		Revision as of 14:46, 19 April 2010
Line 13:		Line 13:

	CVSROOT /map/gfx0/cvsroot		CVSROOT /map/gfx0/cvsroot
	~~GARCH~~ ~~linux~~		GROOT /map/gfx0
	G /map/gfx0/users/$USER		G /map/gfx0/users/$USER
	GTO /map/gfx0/users/$USER		GTO /map/gfx0/users/$USER
	~~GROOT~~ ~~/map/gfx0~~		GARCH linux


Line 22:		Line 22:

	umask 002		umask 002



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

Brad Berg: /* Get the Build System */

2010-04-19T14:43:57Z

Get the Build System

← Older revision		Revision as of 14:43, 19 April 2010
Line 43:		Line 43:
	install_linux/include/<Project Name>/*.h		install_linux/include/<Project Name>/*.h


			Try to build something to see that everything is properly set up.

			> cd /map/gfx0/users/$USER/common/utility
			> make all #
			> make install

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

Brad Berg: New page: These are terse instructions for setting up a typical Linux sandbox at Brown. If you need more explicit instructions or you want a more complex setup then revert back to the full instruct...

2010-04-19T14:39:41Z

New page: These are terse instructions for setting up a typical Linux sandbox at Brown. If you need more explicit instructions or you want a more complex setup then revert back to the full instruct...

New page

These are terse instructions for setting up a typical Linux sandbox at Brown. If you need more explicit instructions or you want a more complex setup then revert back to the full instructions.

== Create your Sandbox ==

Create a user directory for yourself in the groups work area. Be sure to use your login name as the directory name.

> mkdir /map/gfx0/users/$USER

== Environment Variables ==

Setup your environment variables in your login shell.

CVSROOT /map/gfx0/cvsroot
GARCH linux
G /map/gfx0/users/$USER
GTO /map/gfx0/users/$USER
GROOT /map/gfx0

Also set your umask in your login shell to 002:

umask 002

== Get the Build System ==

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
> cvs co common

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 the install directory for Linux with:

> mkdir /map/gfx0/users/$USER/install_linux

The install directories are organized like this:

install_linux/lib/<Project Name>/lib*.a
install_linux/bin/<Project Name>/<Program>
install_linux/include/<Project Name>/*.h

== Get Project Code ==

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
> cvs co project/<Project Name>

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>

You are free to organize your project within the new directory as you wish. For instructions on writing make files visit: https://sourceforge.net/apps/mediawiki/vrg3d/index.php?title=Writing_Make_Files

== Get Third Party Software ==

Many projects depend on downloaded software. Create the '''import''' directory in your sandbox where downloaded software is installed.

> mkdir /map/gfx0/users/$USER/import

The packages you need are determined by the projects you are working on. Project documentation is the first place to check for required software. Copies of some packages are installed in a shared public area, however the public area may not have the versions your projects require and the installations may change over time without notice. The only sure fire method is to download and install the software.

To see how the import directory is organized and what packages are installed look in the public installations:

/map/gfx0/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:

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