Install 3rd-party programs or libraries

A lot of great software has been written by people not in our group, and it's to our advantage to be able to make use of it. This HOWTO explains how to install a 3rd-party project (that is, a program or library) into $G so that everyone in the group can use it. This is easiest if you can get a simple source tree for the project, but we can even deal with complicated source trees and binary-only projects.

Remember to never copy files directly into $G! Everything in $G should get there by being checked into CVS.

Install a simple source tree

In this case, installing a 3rd-party project is identical to checking in and installing one you wrote yourself.

1. Copy the source tree into any directory of your choice (not in $G but somewhere in your homedir). Remember to make sure the tree is clean; no object files or other binaries.
2. Import the project into CVS as normal.
3. Modify the Makefile that came with the project so that make all builds the project locally and make install puts executables into $G/bin, headers into $G/include, libraries into $G/lib, and documentation into $G/man.
4. Check in and commit your changes to the Makefile, and you're done!

Install a complicated source tree

In some rare situations, you can't put all the project's source into our CVS tree. In this case, the goal is to package everything you've got up into a .zip file and make the build and install scripts temporarily unpack the source tree.

1. If you already have a .zip file for the source tree, continue on. If not, use the zip command to create an archive.
2. Move the .zip file into its own directory and create a Makefile there.
   • The all target should unzip the archive and build it.
   • The install target should copy the resulting executables, headers, libraries, and documentation into $G/bin, $G/include, $G/lib, and $G/man respectively.
3. Move the .zip file somewhere else temporarily and import the project into CVS as normal with just the Makefile in the directory.
4. Move the .zip file into the appropriate $G/src/<projname> directory, check it in with cvs add -kb <archivename>, and then commit.

Here's an example Makefile for the NIFTI medical image format library:

all:
	unzip -ou nifti.zip
	# nifti.zip has a 
	cd src; make all

install: all
	cd src; make doc
	cp src/bin/* $(G)/bin
	cp -rf src/lib $(G)/lib/nifti
	cp -rf src/include $(G)/include/nifti
	cp -rf src/docs/html $G/shared/man/nifti

Advanced: use wget

Sometimes it makes sense to have the build and install scripts just download the project directly, rather than checking an archive into our CVS. Be careful about doing this, as versions and URLs change over time.

Rather than download the project's .zip file yourself and then check that in, you can add a wget command to the Makefile to download it, and then unzip, build, and install it as above.

Here's an optional download target that could be appended to the Makefile above and added to the all step:

download:
	rm -rf src nifti.zip
	wget -rq --reject "*.html*" --nH --cut-dirs=2 http://nifti.nimh.nih.gov/pub/dist/src/
	zip -r nifti.zip src
	rm -rf src

Install binary files directly

If you don't even have a .zip file of the source tree for a project, then you have no other choice but to put the actual binary library file into CVS. Remember to add it with "cvs add -kb filename" to signify to CVS that it's a binary file. Even in this case, create a Makefile that will respond to "make all" and "make install". For "make all" you can just print out, "Nothing to do for this project." "make install" should use gfxinstall3 to install the files in the proper places in $G.