$G in practice - Revision history

Brad Berg: /* Development Environment */

2010-04-29T19:44:58Z

Development Environment

← Older revision		Revision as of 19:44, 29 April 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_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: /* Development Environment */

2010-04-23T13:58:07Z

Development Environment

← Older revision		Revision as of 13:58, 23 April 2010
Line 19:		Line 19:
	* '''tools/linux/import''': Pre-installed third party software.		* '''tools/linux/import''': Pre-installed third party software.

	* '''cvsroot''': The CVS repository. The files in here are only for administrators to access. Students should only access the repository through CVS ~~command~~.		* '''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: /* Development Environment */

2010-04-23T13:49:37Z

Development Environment

← Older revision		Revision as of 13:49, 23 April 2010
Line 16:		Line 16:

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

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

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

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

Brad Berg: /* Setting Environment Variables */

2010-04-23T12:22:24Z

Setting Environment Variables

← Older revision		Revision as of 12:22, 23 April 2010
Line 114:		Line 114:
	</pre>		</pre>


			If you want to explicitly designate a compiler visit this page with a more [https://sourceforge.net/apps/mediawiki/vrg3d/index.php?title=G_COMPILER detailed description of G_COMPILER].

	'''PATH''': Only on Windows does this needs to be set in order to access the Unix utilities for Windows. A few Unix utilities are needed to build projects. You can check these out of CVS from Linux with:		'''PATH''': Only on Windows does this needs to be set in order to access the Unix utilities for Windows. A few Unix utilities are needed to build projects. You can check these out of CVS from Linux with:

Brad Berg: /* Access to CVS */

2010-04-23T12:11:19Z

Access to CVS

← Older revision		Revision as of 12:11, 23 April 2010
Line 41:		Line 41:
	On Windows set '''CVSROOT''' to: <code>Y:\map\gfx0\cvsroot\</code>		On Windows set '''CVSROOT''' to: <code>Y:\map\gfx0\cvsroot\</code>

	'''CAUTION:''' The free versions of CVS we've tried do not work reliably on Windows. Unless you carefully check your work you should perform CVS operations on Unix. It is generally safe to check software ~~out~~ from CVS on Windows.		'''CAUTION:''' The free versions of CVS we've tried do not work reliably on Windows. Unless you carefully check your work you should perform CVS operations on Unix. It is generally safe to do a read-only check out of software from CVS on Windows.

	The CVS repository has the golden copies of our software. It is a high valued item so you need to use caution whenever you modify it. It is important to understand how CVS works and what effects CVS command have. If you are new to CVS there are many tutorials online to help you get started. Note that deleting or renaming directories in the CVS repository needs to be done by an administrator.		The CVS repository has the golden copies of our software. It is a high valued item so you need to use caution whenever you modify it. It is important to understand how CVS works and what effects CVS command have. If you are new to CVS there are many tutorials online to help you get started. Note that deleting or renaming directories in the CVS repository needs to be done by an administrator.

Brad Berg: /* Access to CVS */

2010-04-22T14:51:24Z

Access to CVS

← Older revision		Revision as of 14:51, 22 April 2010
Line 44:		Line 44:

	The CVS repository has the golden copies of our software. It is a high valued item so you need to use caution whenever you modify it. It is important to understand how CVS works and what effects CVS command have. If you are new to CVS there are many tutorials online to help you get started. Note that deleting or renaming directories in the CVS repository needs to be done by an administrator.		The CVS repository has the golden copies of our software. It is a high valued item so you need to use caution whenever you modify it. It is important to understand how CVS works and what effects CVS command have. If you are new to CVS there are many tutorials online to help you get started. Note that deleting or renaming directories in the CVS repository needs to be done by an administrator.

			One page cheat sheet for CVS: http://www.bravegnu.org/cvscheat/cvscheat.pdf

	=== Creating a Development Sandbox ===		=== Creating a Development Sandbox ===

Brad Berg: /* Access to CVS */

2010-04-21T16:41:08Z

Access to CVS

← Older revision		Revision as of 16:41, 21 April 2010
Line 42:		Line 42:

	'''CAUTION:''' The free versions of CVS we've tried do not work reliably on Windows. Unless you carefully check your work you should perform CVS operations on Unix. It is generally safe to check software out from CVS on Windows.		'''CAUTION:''' The free versions of CVS we've tried do not work reliably on Windows. Unless you carefully check your work you should perform CVS operations on Unix. It is generally safe to check software out from CVS on Windows.

			The CVS repository has the golden copies of our software. It is a high valued item so you need to use caution whenever you modify it. It is important to understand how CVS works and what effects CVS command have. If you are new to CVS there are many tutorials online to help you get started. Note that deleting or renaming directories in the CVS repository needs to be done by an administrator.

	=== Creating a Development Sandbox ===		=== Creating a Development Sandbox ===

Brad Berg: /* Development Environment */

2010-04-21T16:33:05Z

Development Environment

← Older revision		Revision as of 16:33, 21 April 2010
Line 10:		Line 10:

	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/''':

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

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

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

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


			Within the CVS repository the primary directories are:

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

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

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

Brad Berg: /* Verify You Can Build Software */

2010-04-20T19:58:42Z

Verify You Can Build Software

← Older revision		Revision as of 19:58, 20 April 2010
Line 123:		Line 123:
	> cd/d <Sandbox>\common\utility		> cd/d <Sandbox>\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 '''<Sandbox>\install_WIN32''' to ensure it was properly populated.		Finally inspect '''<Sandbox>\install_WIN32''' to ensure it was properly populated.

Brad Berg: /* Verify You Can Build Software */

2010-04-20T19:58:11Z

Verify You Can Build Software

← Older revision		Revision as of 19:58, 20 April 2010
Line 121:		Line 121:
	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 <Sandbox>\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 '''<Sandbox>\install_WIN32''' to ensure it was properly populated.