Install 3rd party code - Revision history

Brad Berg at 15:09, 4 April 2012

2012-04-04T15:09:09Z

← Older revision		Revision as of 15:09, 4 April 2012
Line 13:		Line 13:
	* Create a subdirectory for each installed version of the package. Perform any build required to install the package. The details of how directories are named and structured are determined primarily by the vendor.		* Create a subdirectory for each installed version of the package. Perform any build required to install the package. The details of how directories are named and structured are determined primarily by the vendor.

	* Optionally you can integrate the package into the make system by adding a file: commmon/build/make/<package>.make You will need to also modify common/build/make/use.make to recognize the package on the [[G_USE]] variable.		* Optionally you can integrate the package into the make system by adding a file: commmon/build/make/<package>.make You will need to also modify common/build/make/use.make to recognize the package on the [[G_USE]] variable. You should be able to ascertain how to do this by looking at some of the existing files like: nag.make

	* Once everything is working check in the package. The '''import/*/kit''' directory has uninstalled downloaded packages. Only check in the downloaded kits. Do not check in pre-installed software. Note that tar and zip files need to be checked in as binary files using the -b CVS option.		* Once everything is working check in the package. The '''import/*/kit''' directory has uninstalled downloaded packages. Only check in the downloaded kits. Do not check in pre-installed software. Note that tar and zip files need to be checked in as binary files using the -b CVS option.

Brad Berg at 15:06, 4 April 2012

2012-04-04T15:06:37Z

← Older revision		Revision as of 15:06, 4 April 2012
Line 13:		Line 13:
	* Create a subdirectory for each installed version of the package. Perform any build required to install the package. The details of how directories are named and structured are determined primarily by the vendor.		* Create a subdirectory for each installed version of the package. Perform any build required to install the package. The details of how directories are named and structured are determined primarily by the vendor.

	* Optionally you can integrate the package into the make system by adding a file: commmon/build/make/<package>.make You will need to also modify common/build/make/use.make to recognize the package on the G_USE variable.		* Optionally you can integrate the package into the make system by adding a file: commmon/build/make/<package>.make You will need to also modify common/build/make/use.make to recognize the package on the [[G_USE]] variable.

	* Once everything is working check in the package. The '''import/*/kit''' directory has uninstalled downloaded packages. Only check in the downloaded kits. Do not check in pre-installed software. Note that tar and zip files need to be checked in as binary files using the -b CVS option.		* Once everything is working check in the package. The '''import/*/kit''' directory has uninstalled downloaded packages. Only check in the downloaded kits. Do not check in pre-installed software. Note that tar and zip files need to be checked in as binary files using the -b CVS option.

Brad Berg at 15:05, 4 April 2012

2012-04-04T15:05:30Z

← Older revision		Revision as of 15:05, 4 April 2012
Line 1:		Line 1:
	Most ~~project~~ use code downloaded from third parties. For convenience some have been pre-installed in: '''/map/gfx0/tools/linux/import/'''		Most projects use code downloaded from third parties. For convenience some have been pre-installed in: '''/map/gfx0/tools/linux/import/'''

	If the package or a version you need is not there you'll need to add it. ~~You can ask Brad to do this for~~ you~~. You~~ can ~~also~~ set it up in your private import directory in your sandbox and make it public later. The import directories are structured as:		If the package or a version you need is not there you'll need to add it. If you want you can set it up in your private import directory in your sandbox and make it public later. The import directories are structured as:

	import/<Package>/kit/<Downloaded Kit>.tar		import/<Package>/kit/<Downloaded Kit>.tar
Line 7:		Line 7:
	import/<Package>/<Installed Kit>/...		import/<Package>/<Installed Kit>/...

			* Create a subdirectory under import to hold all versions of a package.

	~~The details of how directories are named~~ and ~~structured are determined primarily by the vendor~~.		* Create the kit directory and put any download files there.

	The '''import/''' directory ~~in CVS~~ has uninstalled packages. Do not check in pre-installed software. ~~Only check~~ in the ~~downloaded kits~~.		* Create a subdirectory for each installed version of the package. Perform any build required to install the package. The details of how directories are named and structured are determined primarily by the vendor.

			* Optionally you can integrate the package into the make system by adding a file: commmon/build/make/<package>.make You will need to also modify common/build/make/use.make to recognize the package on the G_USE variable.

			* Once everything is working check in the package. The '''import/*/kit''' directory has uninstalled downloaded packages. Only check in the downloaded kits. Do not check in pre-installed software. Note that tar and zip files need to be checked in as binary files using the -b CVS option.

Brad Berg: New page: Most project use code downloaded from third parties. For convenience some have been pre-installed in: '''/map/gfx0/tools/linux/import/''' If the package or a version you need is not ther...

2010-04-21T16:16:51Z

New page: Most project use code downloaded from third parties. For convenience some have been pre-installed in: '''/map/gfx0/tools/linux/import/''' If the package or a version you need is not ther...

New page

Most project use code downloaded from third parties. For convenience some have been pre-installed in: '''/map/gfx0/tools/linux/import/'''

If the package or a version you need is not there you'll need to add it. You can ask Brad to do this for you. You can also set it up in your private import directory in your sandbox and make it public later. The import directories are structured as:

import/<Package>/kit/<Downloaded Kit>.tar
import/<Package>/kit/<Downloaded Kit>.zip
import/<Package>/<Installed Kit>/...

The details of how directories are named and structured are determined primarily by the vendor.

The '''import/''' directory in CVS has uninstalled packages. Do not check in pre-installed software. Only check in the downloaded kits.