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 spatialite-tools are exactly the ones inherited by libspatialite.
spatialite-tools are built on the top of libspatialite, so it's very alike you've already resolved any required dependency while building libspatialite'; you simply have to use now the same settings.
The following is the full list of options you can pass to ./configure:
--enable-geos=[yes|no]
--enable-proj=[yes|no]

On Linux and MacOsX you can support [or not] readline setting:
--enable-readline=[yes|no]

Any required library will be searched by default on /usr/local/lib
you can alter the standard behaviour using:
--with-proj-lib=some_dir
--with-geos-lib=some_other_dir
--with-spatialite-lib=yet_another_dir

Building on Linux

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

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

Building on MacOsX

Building spatialite-tools on MacOsX is quite the same as for Linux; simply an --target=macosx is required because the libs layout on MacOsX is a little bit peculiar.
We'll suppose you have unpacked the sources as
./spatialite-tools-2.3.1

# cd spatialite-tools-2.3.1
# ./configure --target=macosx
# 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.

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; simply an --target=mingw32 is required to sane any specific Windows idiosyncrasy.
We'll suppose you have unpacked the sources as
C:\spatialite-tools-2.3.1

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

using Microsoft Visual Studio .NET

We suppose you have already installed Visual Studio enabling the command line tools [you are expected to use the command prompt shell].
We'll suppose you have unpacked the sources as
C:\spatialite-tools-2.3.1

> cd c:\spatialite-tools-2.3.1
> nmake /f makefile.vc
> nmake /f makefile.vc install

Please note: standard definitions in makefile.vc assumes: If you want to alter this basic behaviour you have then to adapt makefile.vc.
The libspatialite-geos.def file contains any external symbol to be exported from the DLL when you build including GEOS.

back