back to main page
Installing spatialite-2.2 on Mac OS X
spatialite-2.2 is a SQLite's extension, and includes in
itself two further SQLite's extensions: the RTree, the MbrCache, the VirtualShape
and the VirtualText ones.
There are various alternative ways you can follow at your choice to deploy and use them:
- the spatialite executable way:
- this one represents all-the-stuff-you-need already-bounded-together
- spatialite does not requires any installation;
you simply have to gunzip what you've just downloaded [i.e. spatialite-2.2-MacOsX-10.5-target-bin.tar.gz]
and put it in some directory
- to get started you can launch the ./spatialite program. That's all.
spatialite is a statically linked executable;
it has no external dependencies at all, so it's immediately ready to run
- the sqlite3 way:
- MacOsX supports the sqlite3 package.
Very likely you have it already installed on your system
- Caveat: the sqlite3 of standard distribution doesn't supports
the dynamic extension loading mechanism anyway
- get the spatialite-2.2-MacOsX-10.5-target-libs.zip
- neither SQLite nor spatialite requires an installation;
you simply have to gunzip what you've just downloaded, placing binaries and dynamic libraries somewhere
[see note about dynamic libraries]
- to get started you can launch the sqlite3 program, and then .load 'libspatialite.dylib'
That's all
- the GUI tool way:
- you can find lots of GUI tools supporting SQLite.
May well be one of them supports dynamic extensions loading; all the ones I tested refused to do this.
- If you have best luck than me, then you simply have to get the spatialite-2.2-MacOsX-10.5-target-libs.zip
- gunzip it somewhere
- copy all the various shared libraries somewhere [see note about dynamic libraries]
- then you start you preferred SQLite GUI tool and after execute an SQL statement as:
- SELECT load_extension('libspatialite.dylib');
- If this works, you are ready to start
Then I suggest you to download the test.db database and follow the tutorial step by step;
it's the fastest way to become accustomed with SpatiaLite and VirtualShape
Managing dynamic libraries
On MacOsX systems, dynamic libraries are identified by a .dylib suffix
Usually they have a plain name i.e. somelib.dylib, but usually they
supports a version name as well, i.e. somelib.1.0.dylib
Usually this is accomplished simply by creating a symbolic link, as in:
$ ln -s somelib.1.0.dylib somelib.dylib
Usually dynamic libraries must be placed in the /usr/lib directory
You can as well keep yours dynamic libraries in any other directory at your choice,
but in this case you have to set en environment variable, as in:
$ LD_LIBRARY_PATH=/Users/user_name/my_preferred_dylib_dir
$ export LD_LIBRARY_PATH
back to main page