If you’ve compiled software from source you’re probably used to the following sequence:
sudo make install
Which will configure the software to look for libraries and install itself to the default location (normally /usr/local), make and install. As root privileges are required to install to /usr/local, sudo is required.
This is fine unless:
- You’re not in the sudo’ers list (e.g., on a shared computer you’re not an administrator for).
- You want to have different versions of things (e.g., stable and development versions).
then things start to get complicated. Installing all the software to a single folder you have permission to write to, e.g., ~/software, by passing the –prefix=~/software flag to configure, then adding ~/software/bin to your $PATH and ~/software/lib to $LD_LIBRARY_PATH would solve the first problem but will still cause problems if you want different versions of things.
Ideally you’d install everything into it’s own directory something like:
which means you’re going to be spending a lot of time hacking around with environmental variables!
This is where EnvMaster comes in, it allows you to install different versions of software and libraries, in a nicely organised directory structure, and sorts out all the paths for you. When it’s properly set up you can load and swap software / libraries round using:
# Load in RSGISLib
envmaster load rsgislib
# Swap to use the developement version of RSGISLib
envmaster swap rsgislib/2.0.0 rsgislib/20131019
To install EnvMaster clone the source from the EnvMaster Bitbucket page and install:
hg clone https://bitbucket.org/chchrsc/envmaster envmaster
python setup.py install --prefix=$ENVMASTER_ROOT
Note: as with the rest of the examples, I’m installing to ~/software (where ~ is your home directory). You can use anywhere you have permission to write, just do a mental find and replace, wherever you see ~/software with the path your using. We normally install things to /share/osgeo/fw/
EnvMaster uses a corresponding text file for each library, these need to be stored in a separate directory (ideally on there own). We’ll make one called modules.
mkdir -p ~/software/modules
Once this is set up, create a text file (lets call it ~/software/setupenvmaster) containing the following:
# Set up path to modules files
# Initialize EnvMaster
And source it using:
If you add this line to .bashrc / .bash_profile envmaster will be available in every new terminal.
Note, if you used a different version of python to install envmaster (e.g., python3.3) you need to change pythonX.X to reflect this.
Now if you type
You should see ‘~/software/modules’ and ‘No module files found’.
EnvMaster is now all set up and it’s time to start installing things.
Let’s install GDAL, first download from here and untar.
Note, you probably want to install GDAL with other options (e.g., HDF5), see the RSGISLib documentation for the options recommended if building for RSGISLib.
You then need to set up the files for EnvMaster. Within ~/software/modules make a directory called gdal and create two text files, one called 1.10.1 (the version of gdal) and the other called version.py. In 1.10.1 put the following:
The first line tells EnvMaster this is an EnvMaster file, module.SetAll() sets environmental variables (PATH etc.,) based on the contents of ~/software/gdal/1.10.1.
In version.py put the following:
version = '1.10.1'
This tells EnvMaster the default version of GDAL is 1.10.1
If you run envmaster avail again it should list gdal. You can load GDAL using:
envmaster load gdal
To unload GDAL (and unset paths) use:
envmaster unload gdal
You can try running gdal_translate to check.
To see the environmental variables GDAL set use:
envmaster disp gdal
As well adding the path to general variables (e.g., PATH), EnvMaster has created variables specific to GDAL (e.g., GDAL_LIB_PATH), these are useful when linking from other software.
To see the envmaster modules you have loaded you can use:
There are loads more options available in EnvMaster than shown here. Whilst it does take a bit of time to set up, it allows you to build a highly organised and very flexible system. The user guide for EnvMaster, in LyX format, is available with the source code from here.
A comprehensive list of instructions for building software with EnvMaster under Linux is available from Landcare (here). Note: These were developed for their system and have very generously been made available. Use at your own risk.
Pete Bunting’s instructions for building under OS X are also available here, these have been tested under OS X 10.9.