Menu

BuildInstructions Log in to Edit

Bjarne Büchmann

Build instructions

This page should provide the information necessary to build the tools and provide a general unified bin directory for the tools.

Before you build, make sure that you have read [PreRequisites].

Download source

Use git to download source. The necessary command line can be pasted from http://sourceforge.net/p/getm-utils/git/, i.e.

git clone git://git.code.sf.net/p/getm-utils/git getm-utils-git

Environment variables

Some of the tools require some environment variables to be set in order to compile.

The various tools will - at least to some extend - try to use identical or similar environment variables to compile. In particular, for netCDF libraries, set environment variables NETCDFINC and NETCDFLIBDIR. Using version 4 of the NetCDF library be sure that 'nc-config' is in your path.

variable meaning
NETCDFINC NetCDF3 variable. Path to directory where netcdf.inc is located, if your compiler needs that.
NETCDFLIBDIR NetCDF3 variable. Path to netCDF library, if compiler needs that.

Example, for netCDF v.3 I use (with bash) e.g.:

export NETCDF=NETCDF3
export NETCDFBASE=/opt/netcdf-3.6.2/
export NETCDFINC=${NETCDFBASE}/include
export NETCDFLIBDIR=${NETCDFBASE}/lib

Build

Go to the downloaded directory e.g. getm-utils-git.
By default, the compiled utilities are copied to a local bin directory, e.g. getm-utils-git/bin. You can change this by setting BINDIR.

export BINDIR=$(pwd)/bin
make

To use the compiled utilities, you must make sure that the utility bin dir is in your PATH. Either, set BINDIR to a dir, which is already in the PATH, copy over the binaries, or add the local bin dir to your PATH.

If you want to compile just a single utility, then use the -C flag and the directory for that utility. Be aware that there may be more instructions for each utility on separate pages.


Related

Wiki: GETM Utils
Wiki: Gvc2Zax
Wiki: OtpsTides
Wiki: PreRequisites

Discussion

Anonymous
Anonymous

Add attachments
Cancel