Installing the RPM:Download rpms from Google Code.
Optional prerequisites are unixODBC-2.x, openssl-0.9, gd-2.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!
Getting the source from SVN:
svn checkout http://smx.googlecode.com/svn/trunk/ smx-read-onlyor for project members:
svn checkout https://smx.googlecode.com/svn/trunk/ smx --username [your username] That should get all the code. If you want to submit a patch, run svn diff, and send the output to email@example.com.
Future versions of smx will probably REQUIRE sqlite, since it works so much more reliably than berkely and tdb, and seems to compile easliy on most platforms.
If desired for backward compatibility, download TDB from https://sourceforge.net/projects/tdb. 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.
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:
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.