SMX Installation

Installing the RPM:

Prerequisites are unixODBC-2.x, openssl-0.9, gd-2.x, tdb-1.x, sqlite-3.x, and httpd-2.x.

We highly recommend getting the source from CVS and building RPMs for your own platform and specs. SMX RPM building is easy. Just run "make dist" for the tarball, and "rpmbuild -ta" for the rpm!

WARNING: AFAWK, on newer Linux distros, the configure script that comes with libtdb might think that mmap isn't available. Make sure the output from configure thinks mmap is OK. If not, run autoconf first.

Getting the source from CVS:

cvs -d:pserver:anonymous@cvs.smx.berlios.de:/cvsroot/smx login
cvs -z3 -d:pserver:anonymous@cvs.smx.berlios.de:/cvsroot/smx co

Prerequisites for Linux:

You can install all of these as RPM's from www.rpmfind.net, or using apt-get, or yum:

Required for Crypto support:

openssl, openssl-devel

Required for ODBC support:

unixODBC, unixODBC-devel (fedora) OR unixodbc-dev (debian)

Required for IMAGE support:

gd (graphics library by Thomas Boutell)

Required for SQLITE support:

sqlite and sqlite-devel (sqlite)

Required for Apache 2.0 module support:

httpd-devel (fedora) OR apache2-dev (debian)

BerkelyDB needs to be switched to mod_db4 when SMX runs as an apache module, which we haven't done, because maintaining two source bases is complicated. You're much better off with tdb - which is smaller, faster and performs better under the mixed/unstable conditions typical of web serving. The RPM build assumes TDB support. If you're running SMX as a CGI, native BerkeleyDB works fine.

Download from https://sourceforge.net/projects/tdb OR download an RPM which we built. Once all the prerequisites are installed, you should be able to run:

./configure
./make
./make install

Go to the Configuring Apache section.

Prerequisites for Windows:

Download and compile the latest versions of apache and openssl from apache.org and openssl.org.

Windows compilation requires that you add all the .cpp and .h files for each directory to a separate project.

Make libsmx and modsmx DLL projects, and SMX an EXE project.

You will need to adjust paths, and manually create a config.h so that apache, apr, gd, sqlite, openssl and libsmx are all in your project's path.

Configuring Apache:

The httpd.conf should have lines like this in it:

 LoadModule smx_module /usr/lib/libmodsmx.so
 AddHandler smx-parsed .htm
 AddHandler smx-parsed .html
 AddHandler smx-parsed .hmx

and in the individual VirtualHost sections, you may want to have something like:

 SMXInit %module(/var/www/html/global.htx) 

That should do it -- please email with any steps that were different in your configuration, or if you find any steps that were left out.