Re-use pre-existing code or programs - Revision history

Brad Berg at 13:55, 23 June 2009

2009-06-23T13:55:32Z

← Older revision		Revision as of 13:55, 23 June 2009
Line 27:		Line 27:
	<pre>		<pre>
	cd $GROOT/users/$USER/common/gg/		cd $GROOT/users/$USER/common/gg/
	make allclean		make allclean # Clear out all gg libraries.
	make all		make all # Build the gg libraries.
			make install # Install the libraries to your sandbox.
	</pre>		</pre>

Line 37:		Line 38:
	cvs co project/brain		cvs co project/brain
	cd project/brain/brainapp/		cd project/brain/brainapp/
	make allclean		make allclean # Clear any old program files.
	make all		make all # Build the program.
			make install # Install the program in your sandbox.
	</pre>		</pre>

Brad Berg at 16:13, 29 May 2009

2009-05-29T16:13:49Z

← Older revision		Revision as of 16:13, 29 May 2009
Line 9:		Line 9:
	</pre>		</pre>

	Utilities and libraries used by multiple projects are stored under the <code>common/</code> directory. It is small enough that you can check out the whole thing or just the sub-directories you will be using. The following example checks out common include files (for the Nag libraries) and the <code>gg</code> and <code>mri</code> libraries and utilities.		Utilities and libraries used by multiple projects are stored under the <code>common/</code> directory. It is small enough that you can check out the whole thing or just the sub-directories you will be using. The following example checks out common include files (for the Nag libraries) and the <code>gg</code> and <code>mri</code> libraries and utilities. Note that you can check out software into any directory in your sandbox; not just at the top level.

	<pre>		<pre>

Brad Berg at 16:02, 29 May 2009

2009-05-29T16:02:20Z

← Older revision		Revision as of 16:02, 29 May 2009
Line 1:		Line 1:
	After you have set up the $G environment variables you can check out and build existing programs and libraries in your sandbox. Programs and libraries installed in the public $G area (e.g. <code>$G/install_linux/bin/</code>) are conveniently pre-built, but are subject to change. Building and using your own local copy ensures that you will be working with a private stable version.		After you have set up the $G environment variables you can check out and build existing programs and libraries in your sandbox. Programs and libraries installed in the public $G area (e.g. <code>$G/install_linux/bin/</code>) are conveniently pre-built, but are subject to change. Building and using your own local copy ensures that you will be working with a private stable version.

	Do not use the command examples on this page without understanding them. They are only examples and not rote commands. You will have to create variations appropriate to your own circumstances.		Do not use the command examples on this page without understanding them. They are only examples and not rote commands. These instructions are general and not specific to any project. You will have to create variations appropriate to your own circumstances. Instructions for setting up a project are on the project pages.

	Before you can install private copies you need to create a directory for installed files. The installation directory is named <code>install_$GARCH</code>; where <code>$GARCH</code> is the platform name (e.g. <code>install_linux</code> or <code>install_WIN32</code>). By default the installation directory is at the top of your sandbox; which can be your home directory or in the $G user area. Advanced users can designate any location by setting the <code>$GTO</code> variable.		Before you can install private copies you need to create a directory for installed files. The installation directory is named <code>install_$GARCH</code>; where <code>$GARCH</code> is the platform name (e.g. <code>install_linux</code> or <code>install_WIN32</code>). By default the installation directory is at the top of your sandbox; which can be your home directory or in the $G user area. Advanced users can designate any location by setting the <code>$GTO</code> variable.

Brad Berg at 15:04, 29 May 2009

2009-05-29T15:04:13Z

← Older revision		Revision as of 15:04, 29 May 2009
Line 34:		Line 34:

	<pre>		<pre>
	cd $GROOT/users/$USER		cd $GROOT/users/$USER/
	cvs co project/brain		cvs co project/brain
	cd project/brain/brainapp/		cd project/brain/brainapp/

Brad Berg at 15:03, 29 May 2009

2009-05-29T15:03:53Z

← Older revision		Revision as of 15:03, 29 May 2009
Line 12:		Line 12:

	<pre>		<pre>
	cd $GROOT/users/$USER		cd $GROOT/users/$USER/
	cvs co common/include common/gg common/mri		cvs co common/include common/gg common/mri
	</pre>		</pre>

Brad Berg at 15:03, 29 May 2009

2009-05-29T15:03:32Z

← Older revision		Revision as of 15:03, 29 May 2009
Line 36:		Line 36:
	cd $GROOT/users/$USER		cd $GROOT/users/$USER
	cvs co project/brain		cvs co project/brain
	cd project/brain/brainapp		cd project/brain/brainapp/
	make allclean		make allclean
	make all		make all
	</pre>		</pre>

Brad Berg at 15:02, 29 May 2009

2009-05-29T15:02:43Z

← Older revision		Revision as of 15:02, 29 May 2009
Line 23:		Line 23:
	</pre>		</pre>

	Other directories will need to be built before they are installed. The build process for a particular project is determined by the project developers and may vary. This is because there are many combinations of compilers, platforms, and versions that can potentially be built. ~~Generally though~~ <code>make all</code> will build useful combinations and <code>make allclean</code> will clear out generated intermediate files.		Other directories will need to be built before they are installed. The build process for a particular project is determined by the project developers and may vary. This is because there are many combinations of compilers, platforms, and versions that can potentially be built. By convention <code>make all</code> will build generally useful combinations and <code>make allclean</code> will clear out generated intermediate files.

	<pre>		<pre>

Andrew Forsberg: took out "> " quotes so you can copy and paste commands more easily

2009-05-29T15:00:37Z

took out "> " quotes so you can copy and paste commands more easily

← Older revision		Revision as of 15:00, 29 May 2009
Line 6:		Line 6:

	<pre>		<pre>
	> mkdir $GROOT/users/$USER/install_linux/		mkdir $GROOT/users/$USER/install_linux/
	</pre>		</pre>

Line 12:		Line 12:

	<pre>		<pre>
	> cd $GROOT/users/$USER		cd $GROOT/users/$USER
	> cvs co common/include common/gg common/mri		cvs co common/include common/gg common/mri
	</pre>		</pre>

Line 19:		Line 19:

	<pre>		<pre>
	> cd $GROOT/users/$USER/common/include/nag/		cd $GROOT/users/$USER/common/include/nag/
	> make install		make install
	</pre>		</pre>

Line 26:		Line 26:

	<pre>		<pre>
	> cd $GROOT/users/$USER/common/gg/		cd $GROOT/users/$USER/common/gg/
	> make allclean		make allclean
	> make all		make all
	</pre>		</pre>

Line 34:		Line 34:

	<pre>		<pre>
	> cd $GROOT/users/$USER		cd $GROOT/users/$USER
	> cvs co project/brain		cvs co project/brain
	> cd project/brain/brainapp		cd project/brain/brainapp
	> make allclean		make allclean
	> make all		make all
	</pre>		</pre>

Brad Berg at 14:56, 29 May 2009

2009-05-29T14:56:56Z

← Older revision		Revision as of 14:56, 29 May 2009
Line 6:		Line 6:

	<pre>		<pre>
	> mkdir $GROOT/$USER/install_linux/		> mkdir $GROOT/users/$USER/install_linux/
	</pre>		</pre>

Line 12:		Line 12:

	<pre>		<pre>
	> cd $GROOT/$USER		> cd $GROOT/users/$USER
	> cvs co common/include common/gg common/mri		> cvs co common/include common/gg common/mri
	</pre>		</pre>
Line 19:		Line 19:

	<pre>		<pre>
	> cd $GROOT/$USER/common/include/nag/		> cd $GROOT/users/$USER/common/include/nag/
	> make install		> make install
	</pre>		</pre>
Line 26:		Line 26:

	<pre>		<pre>
	> cd $GROOT/$USER/common/gg/		> cd $GROOT/users/$USER/common/gg/
	> make allclean		> make allclean
	> make all		> make all
Line 34:		Line 34:

	<pre>		<pre>
	> cd $GROOT/$USER		> cd $GROOT/users/$USER
	> cvs co project/brain		> cvs co project/brain
	> cd project/brain/brainapp		> cd project/brain/brainapp

Brad Berg at 14:54, 29 May 2009

2009-05-29T14:54:48Z

← Older revision		Revision as of 14:54, 29 May 2009
Line 23:		Line 23:
	</pre>		</pre>

	Other directories will need to be built before they are installed. The build process for a particular project is determined by the project developers and may vary. This is because there are many combinations of compilers, platforms, and versions that can potentially be built. Generally though <code>make all</code> will build useful combinations ~~and~~ and <code>make allclean</code> will clear out generated intermediate files.		Other directories will need to be built before they are installed. The build process for a particular project is determined by the project developers and may vary. This is because there are many combinations of compilers, platforms, and versions that can potentially be built. Generally though <code>make all</code> will build useful combinations and <code>make allclean</code> will clear out generated intermediate files.

	<pre>		<pre>