Niget sources as well as binaries for 32-bit Windows systems can be downloaded from its home page at http://nanometrologie.cz/niget. The software is written mainly in C language using GTK+ (version 2) toolkit (http://www.gtk.org) and libraries from Gwyddion data analysis software (http://gwyddion.net). Some tools (Oliver-Pharr ODR, Hertz ODR, Two slopes, and Stiffness) use orthogonal distance regression (ODR) which includes Fortran code from ODRPACK95 project, available at http://www.netlib.org/toms/869.zip.
There are no distribution packages available, and users are supposed to compile Niget from source.
C compiler (preferably GNU gcc or Intel icc)
(optional) Fortran compiler (preferably GNU gfortran or Intel ifort)
GNU Make or compatible
GTK2 (and its dependences), including development libraries
(preferable) Gwyddion development libraries (see http://gwyddion.net/download.php for distribution-specific instructions; FFTW3 and GtkGLExt development libraries may be also required as dependences)
If paths to Gwyddion libraries and includes are not found by CMake or provided by user, a recent version of Gwyddion is automatically downloaded and built. Please that this does not include any additional tools or libraries which might be required by Gwyddion; these must be installed manually according to the installation instructions of Gwyddion.
In the Niget source directory, proceed as follows:
mkdir build (out-of-tree builds are preferred with CMake)
cmake .. (CMake looks for compilers and libraries, and configures the build)
This compiles Niget using default configuration. If CMake finds a suitable Fortran compiler, ODRPACK95 will be compiled and ODR-based tools enabled. Optional configuration parameters can be set by adding -D OPTION=VALUE to the cmake command (cmake -D OPTION1=VALUE1 … -D OPTIONn=VALUEn ..). Presently available options are:
DEBUG – ON (default) / OFF: make debug build
VERBOSE – ON / OFF (default): increase verbosity of some tools for debugging purposes
Specific compilers can be provided using CC and FC environment variables, e.g. CC=icc FC=ifort cmake .. to use Intel compilers. After running CMake, the options above are stored into CMake’s cache in the build directory, and need not be specified with further CMake runs (or have to be specified explicitly if a change is desired). Note: until the code is sufficiently tested, DEBUG is ON by default, and release build must be triggered manually.
After the software compiles successfully, the niget binary, created in the build directory, can be run.
Niget Windows 32-bit binaries are distributed in a single zip-file, which contains all the required libraries. This is the preferred way for Windows users to start using Niget.
Compiling using CMake and MinGW suite in MSYS2 environment has been tested and is currently used to provide the Windows builds of Niget. Unfortunately, no straightforward procedure is available at the moment.