Install 3rd party code: Difference between revisions
Jump to navigation
Jump to search
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... |
No edit summary |
||
| Line 1: | Line 1: | ||
Most | 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. | 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. | |||
* Create the kit directory and put any download files there. | |||
The '''import/''' directory | * 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. | |||
Revision as of 15:05, 4 April 2012
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. 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>.zip import/<Package>/<Installed Kit>/...
- Create a subdirectory under import to hold all versions of a package.
- Create the kit directory and put any download files there.
- 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.