Using Public or Private Programs and Libraries - Revision history

Jadrian Miles at 21:31, 23 January 2012

2012-01-23T21:31:43Z

← Older revision		Revision as of 21:31, 23 January 2012
Line 1:		Line 1:
	~~== Using Public or Private Programs and Libraries ==~~

	You can have either private copies of libraries and programs or you can use the shared copies. When you use private programs and libraries you determine when they are updated and which ones you want to use. The downside is that you have to set them up and mange them yourself. Alternatively you can use public software, however because it is public it can be changed by any member of the group at any time. Usually people use caution when changes happen, but regardless any changes are likely to disrupt some users.		You can have either private copies of libraries and programs or you can use the shared copies. When you use private programs and libraries you determine when they are updated and which ones you want to use. The downside is that you have to set them up and mange them yourself. Alternatively you can use public software, however because it is public it can be changed by any member of the group at any time. Usually people use caution when changes happen, but regardless any changes are likely to disrupt some users.

Brad Berg: /* Using only Private Directories at the Top of Your Work Area */

2010-11-23T18:16:18Z

Using only Private Directories at the Top of Your Work Area

← Older revision		Revision as of 18:16, 23 November 2010
Line 54:		Line 54:
	Do not copy the entire import directory as it uses a lot of space. Only copy the packages you need. You can also install imports by downloading the latest package.		Do not copy the entire import directory as it uses a lot of space. Only copy the packages you need. You can also install imports by downloading the latest package.

	It's recommended that you build the Brown software rather than copy it from the public directory. This ensures ~~that~~ the versions ~~you are working with correspond~~ to the source code in your work area.		It's recommended that you build the Brown software rather than copy it from the public directory. This ensures you have the latest versions corresponding to the source code in your work area.

	If you want to install your project in the private area set:		If you want to install your project in the private area set:

Brad Berg: /* Using Public or Private Programs and Libraries */

2010-11-23T18:11:26Z

Using Public or Private Programs and Libraries

← Older revision		Revision as of 18:11, 23 November 2010
Line 7:		Line 7:
	The '''import/''' directory has subdirectories for each package. The organization of each subdirectory is determined by the vendor and the person that set up the install.		The '''import/''' directory has subdirectories for each package. The organization of each subdirectory is determined by the vendor and the person that set up the install.

	Public libraries and programs written by Brown students ~~can be~~ installed in the '''/research/graphics/tools/linux/install_linux/''',		Public libraries and programs written by Brown students is installed in one of these directories depending on the platform:
	or '''/research/graphics/tools/linux/install_WIN32/''',
	or '''/research/graphics/tools/linux/install_OSX/''' ~~directories.~~ Each has '''bin/''', '''lib''', '''include/''', and '''share/''' subdirectories. When building with libraries the build system looks for an install directory in this order:		:'''/research/graphics/tools/linux/install_linux/'''
			:'''/research/graphics/tools/linux/install_WIN32/'''
			:'''/research/graphics/tools/linux/install_OSX/'''

			Each has '''bin/''', '''lib''', '''include/''', and '''share/''' subdirectories. When building with libraries the build system looks for an install directory in this order:

	$GROOT/users/$USER/install_$GARCH/		$GROOT/users/$USER/install_$GARCH/
Line 17:		Line 21:
	$G/install_$GARCH/		$G/install_$GARCH/

	The '''$G''' variable is used to access installed projects as ~~described~~ and it is also used to access the make files in:		The '''$GTO''' variable is used to access installed projects and defaults to '''$G'''.

			The '''$G''' variable is used as a default location and it is also used to access the make files in:

	$G/common/build/make/		$G/common/build/make/



	== Using only Public Directories ==		== Using only Public Directories ==

Brad Berg at 18:05, 23 November 2010

2010-11-23T18:05:52Z

← Older revision		Revision as of 18:05, 23 November 2010
Line 1:		Line 1:
	== Using Public or Private Programs and Libraries ==		== Using Public or Private Programs and Libraries ==

	You can have either private copies of libraries or you can use the shared copies. If you ~~want to~~ use private programs and libraries ~~then~~ you determine when they are updated and which ones you want to use. ~~You also~~ have to set them up yourself. ~~You~~ can ~~also instead~~ use public ~~copies~~, however because ~~they are~~ public ~~they~~ can be changed by any member of the group. Usually people use caution when changes happen, but regardless any changes are likely to ~~affect~~ some users.		You can have either private copies of libraries and programs or you can use the shared copies. When you use private programs and libraries you determine when they are updated and which ones you want to use. The downside is that you have to set them up and mange them yourself. Alternatively you can use public software, however because it is public it can be changed by any member of the group at any time. Usually people use caution when changes happen, but regardless any changes are likely to disrupt some users.

	Libraries and programs from third parties are typically downloaded from the web. The public copies are installed in '''/~~map~~/~~gfx0~~/tools/linux/import/'''. The environment variable '''G_IMPORT''' controls where the the build system gets third party libraries when linking. If you want private copies, set up an import directory in your sandbox. You can install the latest versions them from scratch or copy select packages from the public imports.		Libraries and programs from third parties are typically downloaded from the web. The public copies are installed in '''/research/graphics/tools/linux/import/'''. The environment variable '''G_IMPORT''' controls where the the build system gets third party libraries when linking. Defaults are '''$G/import''' and then '''$GROOT/tools/linux/import'''. If you want private copies, set up an import directory in your sandbox. You can install the latest versions them from scratch or copy select packages from the public imports.

	The '''import/''' directory has subdirectories for each package. The organization of each subdirectory is determined by the vendor and the person that set up the install.		The '''import/''' directory has subdirectories for each package. The organization of each subdirectory is determined by the vendor and the person that set up the install.

	~~Libraries~~ and programs written by Brown students can be installed in '''/~~map~~/~~gfx0~~/tools/linux/install_linux/''' or '''/~~map~~/~~gfx0~~/tools/linux/install_WIN32/''' directories. Each has '''bin/''', '''lib''', and '''~~include~~/''' subdirectories. When building with libraries the build system looks for an install directory in this order:		Public libraries and programs written by Brown students can be installed in the '''/research/graphics/tools/linux/install_linux/''',
			or '''/research/graphics/tools/linux/install_WIN32/''',
			or '''/research/graphics/tools/linux/install_OSX/''' directories. Each has '''bin/''', '''lib''', '''include/''', and '''share/''' subdirectories. When building with libraries the build system looks for an install directory in this order:

	$GROOT/users/$USER/install_$GARCH/		$GROOT/users/$USER/install_$GARCH/
	$HOME/install_$GARCH/		$HOME/install_$GARCH/
	$GROOT/tools/linux/install_$GARCH/		$GROOT/tools/linux/install_$GARCH/
			$GTO/install_$GARCH/
	$G/install_$GARCH/		$G/install_$GARCH/


	The '''$G''' variable is used to access installed projects as described and it is also used to access the make files in:		The '''$G''' variable is used to access installed projects as described and it is also used to access the make files in:
Line 25:		Line 27:
	With this setup your work are has only your project code and that can be in any directory you want.		With this setup your work are has only your project code and that can be in any directory you want.

	G /~~map~~/~~gfx0~~/tools/linux		G /research/graphics/tools/linux


	If you want to install your project in the public area set:		If you want to install your project in the public area set:

	GTO /~~map~~/~~gfx0~~/tools/linux		GTO /research/graphics/tools/linux


Line 38:		Line 40:
	This configuration allows you to decide when software is updated. Your work will not impacted by changes made to the public area.		This configuration allows you to decide when software is updated. Your work will not impacted by changes made to the public area.

	G /~~map~~/~~gfx0~~/users/$USER		G /research/graphics/users/$USER
	> cd $G		> cd $G
	> cvs co common # Populate the common directory.		> cvs co common # Populate the common directory.
Line 44:		Line 46:
	> mkdir $G/install_linux		> mkdir $G/install_linux
	> mkdir $G/install_WIN32		> mkdir $G/install_WIN32
	Copy select imports from /~~map~~/~~gfx0~~/tools/linux/import/ to: /~~map~~/~~gfx0~~/users/$USER/import/		Copy select imports from /research/graphics/tools/linux/import/ to: /research/graphics/users/$USER/import/

	Do not copy the entire import directory as it uses a lot of space. Only copy the packages you need. You can also install imports by downloading the latest package.		Do not copy the entire import directory as it uses a lot of space. Only copy the packages you need. You can also install imports by downloading the latest package.
Line 52:		Line 54:
	If you want to install your project in the private area set:		If you want to install your project in the private area set:

	GTO /~~map~~/~~gfx0~~/users/$USER		GTO /research/graphics/users/$USER


	If you want to install your project in the public area set:		If you want to install your project in the public area set:

	GTO /~~map~~/~~gfx0~~/tools/linux		GTO /research/graphics/tools/linux

	== Using Public Third Party Packages and Private Brown Software. ==		== Using Public Third Party Packages and Private Brown Software. ==
Line 63:		Line 65:
	It is less likely that changes to third party software will impact your work. If that is the case then with this configuration you will not have to copy over their software.		It is less likely that changes to third party software will impact your work. If that is the case then with this configuration you will not have to copy over their software.

	G /~~map~~/~~gfx0~~/users/$USER		G /research/graphics/users/$USER
	G_IMPORT /~~map~~/~~gfx0~~/tools/linux		G_IMPORT /research/graphics/tools/linux
	> cd $G		> cd $G
	> cvs co common # Populate the common directory.		> cvs co common # Populate the common directory.
Line 75:		Line 77:
	If you want to install your project in the private area set:		If you want to install your project in the private area set:

	GTO /~~map~~/~~gfx0~~/users/$USER		GTO /research/graphics/users/$USER


	If you want to install your project in the public area set:		If you want to install your project in the public area set:

	GTO /~~map~~/~~gfx0~~/tools/linux		GTO /research/graphics/tools/linux

Brad Berg: /* Using only Private Directories at the Top of Your Work Area */

2010-05-05T14:56:01Z

Using only Private Directories at the Top of Your Work Area

← Older revision		Revision as of 14:56, 5 May 2010
Line 38:		Line 38:
	This configuration allows you to decide when software is updated. Your work will not impacted by changes made to the public area.		This configuration allows you to decide when software is updated. Your work will not impacted by changes made to the public area.

	~~Set~~ G ~~to:~~ /map/gfx0/users/$USER		G /map/gfx0/users/$USER
	> cd $G		> cd $G
	> cvs co common # Populate the common directory.		> cvs co common # Populate the common directory.
Line 58:		Line 58:

	GTO /map/gfx0/tools/linux		GTO /map/gfx0/tools/linux



	== Using Public Third Party Packages and Private Brown Software. ==		== Using Public Third Party Packages and Private Brown Software. ==

Brad Berg at 14:54, 5 May 2010

2010-05-05T14:54:44Z

← Older revision		Revision as of 14:54, 5 May 2010
Line 18:		Line 18:

	$G/common/build/make/		$G/common/build/make/



Line 30:		Line 31:

	GTO /map/gfx0/tools/linux		GTO /map/gfx0/tools/linux



	== Using only Private Directories at the Top of Your Work Area ==		== Using only Private Directories at the Top of Your Work Area ==
Line 55:		Line 58:

	GTO /map/gfx0/tools/linux		GTO /map/gfx0/tools/linux

Brad Berg: /* Using only Public Directories */

2010-05-05T14:53:47Z

Using only Public Directories

← Older revision		Revision as of 14:53, 5 May 2010
Line 22:		Line 22:
	== Using only Public Directories ==		== Using only Public Directories ==

	With this setup ~~you~~ only ~~need~~ your project code and that can be in any directory you want.		With this setup your work are has only your project code and that can be in any directory you want.

	G /map/gfx0/tools/linux		G /map/gfx0/tools/linux
Line 30:		Line 30:

	GTO /map/gfx0/tools/linux		GTO /map/gfx0/tools/linux


	== Using only Private Directories at the Top of Your Work Area ==		== Using only Private Directories at the Top of Your Work Area ==

Brad Berg at 14:52, 5 May 2010

2010-05-05T14:52:46Z

← Older revision		Revision as of 14:52, 5 May 2010
Line 1:		Line 1:
			== Using Public or Private Programs and Libraries ==

	You can have either private copies of libraries or you can use the shared copies. If you want to use private programs and libraries then you determine when they are updated and which ones you want to use. You also have to set them up yourself. You can also instead use public copies, however because they are public they can be changed by any member of the group. Usually people use caution when changes happen, but regardless any changes are likely to affect some users.		You can have either private copies of libraries or you can use the shared copies. If you want to use private programs and libraries then you determine when they are updated and which ones you want to use. You also have to set them up yourself. You can also instead use public copies, however because they are public they can be changed by any member of the group. Usually people use caution when changes happen, but regardless any changes are likely to affect some users.

Line 16:		Line 18:

	$G/common/build/make/		$G/common/build/make/


			== Using only Public Directories ==

			With this setup you only need your project code and that can be in any directory you want.

			G /map/gfx0/tools/linux


			If you want to install your project in the public area set:

			GTO /map/gfx0/tools/linux


			== Using only Private Directories at the Top of Your Work Area ==

			This configuration allows you to decide when software is updated. Your work will not impacted by changes made to the public area.

			Set G to: /map/gfx0/users/$USER
			> cd $G
			> cvs co common # Populate the common directory.
			> cvs co project/... # Populate the projects you want to work on.
			> mkdir $G/install_linux
			> mkdir $G/install_WIN32
			Copy select imports from /map/gfx0/tools/linux/import/ to: /map/gfx0/users/$USER/import/

			Do not copy the entire import directory as it uses a lot of space. Only copy the packages you need. You can also install imports by downloading the latest package.

			It's recommended that you build the Brown software rather than copy it from the public directory. This ensures that the versions you are working with correspond to the source code in your work area.

			If you want to install your project in the private area set:

			GTO /map/gfx0/users/$USER


			If you want to install your project in the public area set:

			GTO /map/gfx0/tools/linux


			== Using Public Third Party Packages and Private Brown Software. ==

			It is less likely that changes to third party software will impact your work. If that is the case then with this configuration you will not have to copy over their software.

			G /map/gfx0/users/$USER
			G_IMPORT /map/gfx0/tools/linux
			> cd $G
			> cvs co common # Populate the common directory.
			> cvs co project/... # Populate the projects you want to work on.
			> mkdir $G/install_linux
			> mkdir $G/install_WIN32

			It's recommended that you build the Brown software rather than copy it from the public directory. This ensures that the versions you are working with correspond to the source code in your work area.

			If you want to install your project in the private area set:

			GTO /map/gfx0/users/$USER


			If you want to install your project in the public area set:

			GTO /map/gfx0/tools/linux

Brad Berg at 12:46, 5 May 2010

2010-05-05T12:46:43Z

← Older revision		Revision as of 12:46, 5 May 2010
Line 5:		Line 5:
	The '''import/''' directory has subdirectories for each package. The organization of each subdirectory is determined by the vendor and the person that set up the install.		The '''import/''' directory has subdirectories for each package. The organization of each subdirectory is determined by the vendor and the person that set up the install.

	Libraries and programs written by Brown students can be installed in '''/map/gfx0/tools/linux/install_linux/''' or '''/map/gfx0/tools/linux/install_WIN32/''' directories. Each has '''bin/''', '''lib''', and '''include/''' subdirectories. When building with libraries the build system ~~first~~ looks for an install directory in this order:		Libraries and programs written by Brown students can be installed in '''/map/gfx0/tools/linux/install_linux/''' or '''/map/gfx0/tools/linux/install_WIN32/''' directories. Each has '''bin/''', '''lib''', and '''include/''' subdirectories. When building with libraries the build system looks for an install directory in this order:

	$GROOT/users/$USER/install_$GARCH/		$GROOT/users/$USER/install_$GARCH/

Brad Berg at 12:45, 5 May 2010

2010-05-05T12:45:49Z

← Older revision		Revision as of 12:45, 5 May 2010
Line 8:		Line 8:

	$GROOT/users/$USER/install_$GARCH/		$GROOT/users/$USER/install_$GARCH/
	$HOME/install_$GARCH		$HOME/install_$GARCH/
	$GROOT/tools/linux/install_$GARCH		$GROOT/tools/linux/install_$GARCH/
	$G/install_$GARCH		$G/install_$GARCH/


			The '''$G''' variable is used to access installed projects as described and it is also used to access the make files in:

			$G/common/build/make/