Shared Public Directory Structure - Revision history

Tom Sgouros: typos

2014-05-01T16:02:16Z

typos

← Older revision		Revision as of 16:02, 1 May 2014
Line 1:		Line 1:
	The graphics group has developed a system over many years that allows easy development of a large, shared base of software. We give the whole thing the nickname <tt>[[$G]]</tt> ("dollar gee"), named after the environment variable that represents the root of the source tree.		The graphics group has developed a system over many years that allows easy development of a large, shared base of software. We give the whole thing the nickname <tt>[[$G]]</tt> ("dollar gee"), named after the environment variable that represents the root of the source tree.

	~~There~~ source code our group has created is modified and backed up through a source control system called CVS (Concurrent Versioning System). You must have CVS set up properly in order to develop with our shared codebase.		The source code our group has created is modified and backed up through a source control system called CVS (Concurrent Versioning System). You must have CVS set up properly in order to develop with our shared codebase.

	Source control works by allowing an individual user to make structured copies of the master versions of files (this process is called "checking out" the files). The user then modifies his or her personal copies of the files, and then "checks in" the changes once they're certain that the code compiles and runs properly. The location where a user modifies a personal copy of shared code is called a "sandbox", because it is in some sense walled off from the master copy: destructive changes to the code in the sandbox do not affect the master copy, provided the user doesn't check them in.		Source control works by allowing an individual user to make structured copies of the master versions of files (this process is called "checking out" the files). The user then modifies his or her personal copies of the files, and then "checks in" the changes once they're certain that the code compiles and runs properly. The location where a user modifies a personal copy of shared code is called a "sandbox", because it is in some sense walled off from the master copy: destructive changes to the code in the sandbox do not affect the master copy, provided the user doesn't check them in.
Line 45:		Line 45:
	a detailed overview of the environment variables and directories.		a detailed overview of the environment variables and directories.

	At any given time there are several active versions of our software. Students need to be aware of what version is appropriate for ~~thier~~ work and set up their workspace to reflect this.		At any given time there are several active versions of our software. Students need to be aware of what version is appropriate for their work and set up their workspace to reflect this.

	* The latest source checked into CVS		* The latest source checked into CVS

Brad Berg at 14:49, 4 April 2012

2012-04-04T14:49:18Z

← Older revision		Revision as of 14:49, 4 April 2012
Line 21:		Line 21:

	* '''tools/linux/install_WIN32''': Shared copies of pre-built Windows projects.		* '''tools/linux/install_WIN32''': Shared copies of pre-built Windows projects.

			* '''tools/public/yesterday''': Browse recent common and project directories.

			* '''tools/public/raw_notes''': Unedited notes on a variety of development topics.

	* '''cvsroot''': The CVS repository. The files in here are only for administrators to access. Students should only access the repository through CVS commands.		* '''cvsroot''': The CVS repository. The files in here are only for administrators to access. Students should only access the repository through CVS commands.

Brad Berg at 18:51, 2 February 2012

2012-02-02T18:51:57Z

← Older revision		Revision as of 18:51, 2 February 2012
Line 32:		Line 32:

	* '''project''': Project software.		* '''project''': Project software.


			A copy of the '''common''' and '''project''' directories for you to browse is updated nightly at:
			/research/graphics/tools/public/yesterday

Brad Berg at 17:57, 3 December 2010

2010-12-03T17:57:51Z

← Older revision		Revision as of 17:57, 3 December 2010
Line 37:		Line 37:
	a detailed overview of the environment variables and directories.		a detailed overview of the environment variables and directories.

	At any given time there are several active versions of our software.		At any given time there are several active versions of our software. Students need to be aware of what version is appropriate for thier work and set up their workspace to reflect this.
	Students need to be aware of what version is appropriate for thier work
	and set up their workspace to reflect this.

	* The latest source checked into CVS		* The latest source checked into CVS

	* The version in a students project directory at the time they last		* The version in a students project directory at the time they last checked it out or changed it.
	checked it out or changed it.

	* The version installed in a students sandbox the last time they built		* The version installed in a students sandbox the last time they built and installed it.
	and installed it.

	* The public installed copy at: /research/graphics/tools/linux/install_$GARCH		* The public installed copy at: /research/graphics/tools/linux/install_$GARCH

	* The copy used for cloning at: /research/graphics/tools/public/clone		* The copy used for cloning at: /research/graphics/tools/public/clone

Brad Berg at 17:57, 3 December 2010

2010-12-03T17:57:11Z

← Older revision		Revision as of 17:57, 3 December 2010
Line 36:		Line 36:
	See [[Using Public or Private Programs and Libraries]] for		See [[Using Public or Private Programs and Libraries]] for
	a detailed overview of the environment variables and directories.		a detailed overview of the environment variables and directories.

			At any given time there are several active versions of our software.
			Students need to be aware of what version is appropriate for thier work
			and set up their workspace to reflect this.

			* The latest source checked into CVS

			* The version in a students project directory at the time they last
			checked it out or changed it.

			* The version installed in a students sandbox the last time they built
			and installed it.

			* The public installed copy at: /research/graphics/tools/linux/install_$GARCH

			* The copy used for cloning at: /research/graphics/tools/public/clone

Brad Berg at 18:21, 23 November 2010

2010-11-23T18:21:05Z

← Older revision		Revision as of 18:21, 23 November 2010
Line 10:		Line 10:


	Here's a description of the directories you will find under '''/~~map~~/~~gfx0~~/''':		Here's a description of the directories you will find under '''/research/graphics/''':

	* '''data''': A directory for large datasets.		* '''data''': A directory for large datasets.
Line 32:		Line 32:

	* '''project''': Project software.		* '''project''': Project software.


			See [[Using Public or Private Programs and Libraries]] for
			a detailed overview of the environment variables and directories.

Brad Berg at 18:07, 4 May 2010

2010-05-04T18:07:31Z

← Older revision		Revision as of 18:07, 4 May 2010
Line 18:		Line 18:
	* '''tools/linux/import''': Pre-installed third party software.		* '''tools/linux/import''': Pre-installed third party software.

	* '''tools/linux/install_linux: Shared copies of pre-built Linux projects.		* '''tools/linux/install_linux''': Shared copies of pre-built Linux projects.

	* '''tools/linux/install_WIN32: Shared copies of pre-built Windows projects.		* '''tools/linux/install_WIN32''': Shared copies of pre-built Windows projects.

	* '''cvsroot''': The CVS repository. The files in here are only for administrators to access. Students should only access the repository through CVS commands.		* '''cvsroot''': The CVS repository. The files in here are only for administrators to access. Students should only access the repository through CVS commands.

Brad Berg at 17:57, 4 May 2010

2010-05-04T17:57:39Z

← Older revision		Revision as of 17:57, 4 May 2010
Line 8:		Line 8:

	Even if you intend to work on Windows you should set up your sandbox at Brown using Linux. The instructions will include Windows specific instructions when applicable. Explicit procedures for setting up a remote Windows system (like your laptop) are not yet in place. If you are familiar with setting up Windows development environments you should be able to adapt these procedures.		Even if you intend to work on Windows you should set up your sandbox at Brown using Linux. The instructions will include Windows specific instructions when applicable. Explicit procedures for setting up a remote Windows system (like your laptop) are not yet in place. If you are familiar with setting up Windows development environments you should be able to adapt these procedures.


	Here's a description of the directories you will find under '''/map/gfx0/''':		Here's a description of the directories you will find under '''/map/gfx0/''':

Brad Berg: New page: The graphics group has developed a system over many years that allows easy development of a large, shared base of software. We give the whole thing the nickname `$G` ("dollar g...

2010-05-04T17:57:22Z

New page: The graphics group has developed a system over many years that allows easy development of a large, shared base of software. We give the whole thing the nickname <tt>$G</tt> ("dollar g...

New page

The graphics group has developed a system over many years that allows easy development of a large, shared base of software. We give the whole thing the nickname <tt>[[$G]]</tt> ("dollar gee"), named after the environment variable that represents the root of the source tree.

There source code our group has created is modified and backed up through a source control system called CVS (Concurrent Versioning System). You must have CVS set up properly in order to develop with our shared codebase.

Source control works by allowing an individual user to make structured copies of the master versions of files (this process is called "checking out" the files). The user then modifies his or her personal copies of the files, and then "checks in" the changes once they're certain that the code compiles and runs properly. The location where a user modifies a personal copy of shared code is called a "sandbox", because it is in some sense walled off from the master copy: destructive changes to the code in the sandbox do not affect the master copy, provided the user doesn't check them in.

Environment variables are used to configure the development environment. Visit this page for general instructions for [[Setting Environment Variables]] and using them. The instructions in the remainder of this section require that you know how to set up environment variables. For Windows the instructions use the native Windows (cmd.exe) command shell. Unix command examples should work on most shells.

Even if you intend to work on Windows you should set up your sandbox at Brown using Linux. The instructions will include Windows specific instructions when applicable. Explicit procedures for setting up a remote Windows system (like your laptop) are not yet in place. If you are familiar with setting up Windows development environments you should be able to adapt these procedures.

Here's a description of the directories you will find under '''/map/gfx0/''':

* '''data''': A directory for large datasets.

* '''users''': Space for students to set up sandboxes.

* '''tools/linux/import''': Pre-installed third party software.

* '''tools/linux/install_linux: Shared copies of pre-built Linux projects.

* '''tools/linux/install_WIN32: Shared copies of pre-built Windows projects.

* '''cvsroot''': The CVS repository. The files in here are only for administrators to access. Students should only access the repository through CVS commands.

Within the CVS repository the primary directories are:

* '''import''': Downloaded kits for third party software.

* '''common''': Software used by multiple projects.

* '''project''': Project software.

Shared Public Directory Structure - Revision history

Tom Sgouros: typos

Brad Berg at 14:49, 4 April 2012

Brad Berg at 18:51, 2 February 2012

Brad Berg at 17:57, 3 December 2010

Brad Berg at 17:57, 3 December 2010

Brad Berg at 18:21, 23 November 2010

Brad Berg at 18:07, 4 May 2010

Brad Berg at 17:57, 4 May 2010

Brad Berg: New page: The graphics group has developed a system over many years that allows easy development of a large, shared base of software. We give the whole thing the nickname $G ("dollar g...

Brad Berg: New page: The graphics group has developed a system over many years that allows easy development of a large, shared base of software. We give the whole thing the nickname `$G` ("dollar g...