Working With Multiple Sandboxes - Revision history

Brad Berg at 18:46, 23 November 2010

2010-11-23T18:46:40Z

@@ Line 2: / Line 2: @@
 Note that you do not need multiple sandboxes to work on multiple versions of a project.  Program development directories (under '''project/''' and '''common/''') can be located anywhere and there can have replicated variations.  In this case the variants all share the same '''install/''' and '''import/''' directories.
 You can create a new sandbox in an arbitrary directory with by running the following command.  Note that this has to be run from a Linux system, but will establish a sandbox for Windows as well.
@@ Line 24: / Line 21: @@
 The '''GTO''' variable determines where software developed at Brown is installed and accessed.  If you want to have totally independent sandboxes then you need to set it to the value of '''G''' for the active sandbox.  You can also have multiple install directories for a single sandbox.  In this case '''GTO''' can be changed to point to one of several target install directories.

Brad Berg at 18:26, 23 November 2010

2010-11-23T18:26:57Z

← Older revision		Revision as of 18:26, 23 November 2010
Line 23:		Line 23:
	In order to switch between sandboxes you can designate the active one by setting the '''G''' environment variable to the active sandbox. This variable is used to access the '''install_linux/''' directory and the make files in '''common/build/make'''. Rather than switching the '''G''' variable it is probably more convenient to open two terminal windows each with different settings for '''G'''.		In order to switch between sandboxes you can designate the active one by setting the '''G''' environment variable to the active sandbox. This variable is used to access the '''install_linux/''' directory and the make files in '''common/build/make'''. Rather than switching the '''G''' variable it is probably more convenient to open two terminal windows each with different settings for '''G'''.

	The '''GTO''' variable determines where software is installed. If you want to have totally ~~separate~~ sandboxes then you need to set it to the value of '''G''' for the active sandbox. You can also have multiple install directories for a single sandbox. In this case '''GTO''' can be changed to point to one of several target install directories.		The '''GTO''' variable determines where software developed at Brown is installed and accessed. If you want to have totally independent sandboxes then you need to set it to the value of '''G''' for the active sandbox. You can also have multiple install directories for a single sandbox. In this case '''GTO''' can be changed to point to one of several target install directories.

Brad Berg at 18:25, 23 November 2010

2010-11-23T18:25:28Z

← Older revision		Revision as of 18:25, 23 November 2010
Line 19:		Line 19:


	Third party software for all platforms will be accessed for all sandboxes from: '''/~~map~~/~~gfx0~~/tools/linux/import/'''		Third party software for all platforms will be accessed for all sandboxes from: '''/research/graphics/tools/linux/import/'''

	In order to switch between sandboxes you can designate the active one by setting the '''G''' environment variable to the active sandbox. This variable is used to access the '''install_linux/''' directory and the make files in '''common/build/make'''. Rather than switching the '''G''' variable it is probably more convenient to open two terminal windows each with different settings for '''G'''.		In order to switch between sandboxes you can designate the active one by setting the '''G''' environment variable to the active sandbox. This variable is used to access the '''install_linux/''' directory and the make files in '''common/build/make'''. Rather than switching the '''G''' variable it is probably more convenient to open two terminal windows each with different settings for '''G'''.

Brad Berg at 18:24, 23 November 2010

2010-11-23T18:24:51Z

← Older revision		Revision as of 18:24, 23 November 2010
Line 8:		Line 8:
	You can create a new sandbox in an arbitrary directory with by running the following command. Note that this has to be run from a Linux system, but will establish a sandbox for Windows as well.		You can create a new sandbox in an arbitrary directory with by running the following command. Note that this has to be run from a Linux system, but will establish a sandbox for Windows as well.

	> /~~map~~/~~gfx0~~/tools/linux/install_linux/bin/setup/new.g.user.sh <Sandbox/>		> /research/graphics/tools/linux/install_linux/bin/setup/new.g.user.sh <Sandbox/>

Brad Berg at 17:20, 22 July 2010

2010-07-22T17:20:35Z

← Older revision		Revision as of 17:20, 22 July 2010
Line 22:		Line 22:

	In order to switch between sandboxes you can designate the active one by setting the '''G''' environment variable to the active sandbox. This variable is used to access the '''install_linux/''' directory and the make files in '''common/build/make'''. Rather than switching the '''G''' variable it is probably more convenient to open two terminal windows each with different settings for '''G'''.		In order to switch between sandboxes you can designate the active one by setting the '''G''' environment variable to the active sandbox. This variable is used to access the '''install_linux/''' directory and the make files in '''common/build/make'''. Rather than switching the '''G''' variable it is probably more convenient to open two terminal windows each with different settings for '''G'''.

			The '''GTO''' variable determines where software is installed. If you want to have totally separate sandboxes then you need to set it to the value of '''G''' for the active sandbox. You can also have multiple install directories for a single sandbox. In this case '''GTO''' can be changed to point to one of several target install directories.


Line 28:		Line 30:
	The environment variable settings for a legacy sandbox do not conflict with the current build system. After setting up the new sandbox and the legacy sandbox the directories under $G should be:		The environment variable settings for a legacy sandbox do not conflict with the current build system. After setting up the new sandbox and the legacy sandbox the directories under $G should be:

	WIN32/ Legacy Windows utilities		WIN32/ Legacy Windows utilities.
	bin/ Legacy installed programs		bin/ Legacy installed programs.
	lib/ Legacy installed libraries		lib/ Legacy installed libraries.
	src/ Legacy source code checked out from CVS		src/ Legacy source code checked out from CVS.
	help/ Legacy help information		help/ Legacy help information.
	tools/ Legacy administrative tools		tools/ Legacy administrative tools.

	install_linux/ Installed copies of Linux software developed at Brown.		install_linux/ Installed copies of Linux software developed at Brown.

Brad Berg at 17:12, 22 July 2010

2010-07-22T17:12:03Z

← Older revision		Revision as of 17:12, 22 July 2010
Line 25:		Line 25:

	* '''Working with the legacy build system.'''		* '''Working with the legacy build system.'''

			The environment variable settings for a legacy sandbox do not conflict with the current build system. After setting up the new sandbox and the legacy sandbox the directories under $G should be:

			WIN32/ Legacy Windows utilities
			bin/ Legacy installed programs
			lib/ Legacy installed libraries
			src/ Legacy source code checked out from CVS
			help/ Legacy help information
			tools/ Legacy administrative tools

			install_linux/ Installed copies of Linux software developed at Brown.
			install_WIN32/ Installed copies of Windows software developed at Brown.
			common/ The most recent common code checked out from CVS.
			project/ An empty directory for your project code.

Brad Berg at 18:57, 21 July 2010

2010-07-21T18:57:51Z

← Older revision		Revision as of 18:57, 21 July 2010
Line 2:		Line 2:

	Note that you do not need multiple sandboxes to work on multiple versions of a project. Program development directories (under '''project/''' and '''common/''') can be located anywhere and there can have replicated variations. In this case the variants all share the same '''install/''' and '''import/''' directories.		Note that you do not need multiple sandboxes to work on multiple versions of a project. Program development directories (under '''project/''' and '''common/''') can be located anywhere and there can have replicated variations. In this case the variants all share the same '''install/''' and '''import/''' directories.


	* '''Setting up an additional sandbox.'''		* '''Setting up an additional sandbox.'''

Brad Berg at 18:57, 21 July 2010

2010-07-21T18:57:35Z

← Older revision		Revision as of 18:57, 21 July 2010
Line 3:		Line 3:
	Note that you do not need multiple sandboxes to work on multiple versions of a project. Program development directories (under '''project/''' and '''common/''') can be located anywhere and there can have replicated variations. In this case the variants all share the same '''install/''' and '''import/''' directories.		Note that you do not need multiple sandboxes to work on multiple versions of a project. Program development directories (under '''project/''' and '''common/''') can be located anywhere and there can have replicated variations. In this case the variants all share the same '''install/''' and '''import/''' directories.

	* Setting up an additional sandbox.		* '''Setting up an additional sandbox.'''

	You can create a new sandbox in an arbitrary directory with by running the following command. Note that this has to be run from a Linux system, but will establish a sandbox for Windows as well.		You can create a new sandbox in an arbitrary directory with by running the following command. Note that this has to be run from a Linux system, but will establish a sandbox for Windows as well.
Line 23:		Line 23:


	* Working with the legacy build system.		* '''Working with the legacy build system.'''

Brad Berg at 18:57, 21 July 2010

2010-07-21T18:57:05Z

← Older revision		Revision as of 18:57, 21 July 2010
Line 5:		Line 5:
	* Setting up an additional sandbox.		* Setting up an additional sandbox.

	You can create a new sandbox in an arbitrary directory with:		You can create a new sandbox in an arbitrary directory with by running the following command. Note that this has to be run from a Linux system, but will establish a sandbox for Windows as well.

	> /map/gfx0/tools/linux/install_linux/bin/setup/new.g.user.sh <Sandbox/>		> /map/gfx0/tools/linux/install_linux/bin/setup/new.g.user.sh <Sandbox/>
Line 18:		Line 18:


	Third party software will be accessed for all sandboxes from: '''/map/gfx0/tools/linux/import/'''		Third party software for all platforms will be accessed for all sandboxes from: '''/map/gfx0/tools/linux/import/'''

	In order to switch between sandboxes you can designate the active one by setting the '''G''' environment variable to the active sandbox. This variable is used to access the '''install_linux/''' directory and the make files in '''common/build/make'''. Rather than switching the '''G''' variable it is probably more convenient to open two terminal windows each with different settings for '''G'''.		In order to switch between sandboxes you can designate the active one by setting the '''G''' environment variable to the active sandbox. This variable is used to access the '''install_linux/''' directory and the make files in '''common/build/make'''. Rather than switching the '''G''' variable it is probably more convenient to open two terminal windows each with different settings for '''G'''.

Brad Berg at 18:54, 21 July 2010

2010-07-21T18:54:03Z

← Older revision		Revision as of 18:54, 21 July 2010
Line 12:		Line 12:
	The '''Sandbox/''' directory will now contain:		The '''Sandbox/''' directory will now contain:

	install_linux/ Installed copies of software developed at Brown.		install_linux/ Installed copies of Linux software developed at Brown.
	common/ The most recent common code from CVS.		install_WIN32/ Installed copies of Windows software developed at Brown.
			common/ The most recent common code checked out from CVS.
	project/ An empty directory for your project code.		project/ An empty directory for your project code.