back

Index of contents

Installation

The default destination path prefix for installed files is /usr/local.
Results from the installation script will be placed into subdirectories include and lib.
If this default path prefix is proper, then execute:

    ./configure

If another path prefix is required, then execute:

    ./configure --prefix=/my/path

In either case, the directory of the prefix path must exist and be writable by the installer.

After executing configure, execute:

    make
    make install

Or even better, you can strip any executable binary, in order to eliminate any debugging symbol, and thus widely reducing their size:

    make install-strip

Required dependencies

The external dependencies needed in order to build librasterlite are the followings:

libtiff

a library required in order to access TIFF images http://www.remotesensing.org/libtiff

libgeotiff

a library supporting GeoTIFF http://trac.osgeo.org/geotiff

libjpeg

a library required in order to access JPEG images http://www.ijg.org

zlib

a library supporting DEFLATE (zip) compression http://www.zlib.net

libpng

a library supporting PNG images http://www.libpng.org/pub/png/libpng.html

libspatialite / libproj

please refer to the libspatialite documentation.

libepsilon

librasterlite internally includes a copy of libepsilon, a library supporting Wavelt compressed images: so you ARE NOT required to install and/or build libepsilon as a separete step.
libepsilon is a copyright of Alexander Simakov, <xander@entropyware.info> http://sourceforge.net/projects/epsilon-project/

Building on Linux

Building librasterlite on Linux does not require any special setting; we'll suppose you have unpacked the sources as
./librasterlite-1.0

# cd librasterlite-1.0
# ./configure
# make
# sudo make install
# or (in order to save some disk space)
# sudo make install-strip

IMPORTANT NOTICE:
the above builds a dynamically-linked version of the tools (i.e. rasterlite_load, rasterlite_pyramids and so on, depends on several shared libraries at run time).
If you want to get a statically-linked version of the tools (i.e., not requiring any external dependency), you simply have now to type:
# mkdir static_bin
# make -f Makefile-static-Linux
and you'll get any statically-linked tool built into the ./static_bin dir

Building on MacOsX

Building spatialite-tools on MacOsX is quite the same as for Linux; we'll suppose you have unpacked the sources as
./librasterlite-1.0

# cd librasterlite-1.0
# ./configure
# make
# sudo make install
# or (in order to save some disk space)
# sudo make install-strip
IMPORTANT NOTICE: this will build an executable for your specific platform. i.e. when building on a PPC Mac, resulting binary will be targeted to run on PPC anyway.
And when building on Intel Mac, resulting binary will run on Intel target.

IMPORTANT NOTICE:
the above builds a dynamically-linked version of the tools (i.e. rasterlite_load, rasterlite_pyramids and so on, depends on several shared libraries at run time).
If you want to get a statically-linked version of the tools (i.e., not requiring any external dependency), you simply have now to type:
# mkdir static_bin
# make -f Makefile-static-MacOsX
and you'll get any statically-linked tool built into the ./static_bin dir

Building on Windows

On Windows systems you can choose using two different compilers:

using MinGW / MSYS

We suppose you have already installed the MinGW compiler and the MSYS shell.
Building spatialite-tools under Windows is then more or less like building on any other UNIX-like system; we'll suppose you have unpacked the sources as
C:\librasterlite-1.0

$ cd c:/librasterlite-1.0
$ export "CFLAGS=-I/usr/local/include"
$ export "LDFLAGS=-L/usr/local/lib"
$ ./configure
$ make
$ make install
$ or (in order to save some disk space)
$ make install-strip

IMPORTANT NOTICE:
the above builds a dynamically-linked version of the tools (i.e. rasterlite_load, rasterlite_pyramids and so on, depends on several shared libraries at run time).
If you want to get a statically-linked version of the tools (i.e., not requiring any external dependency), you simply have now to type:
$ mkdir static_bin
$ make -f Makefile-static-MinGW
and you'll get any statically-linked tool built into the ./static_bin dir

using Microsoft Visual Studio .NET

Not currently supported

back