Hi George, your efforts are much appreciated. At the European
conference some guys explicitly reported to me they know of several
people who would like to adopt and contribute to Rivet if we had a
working Windows build.
On 2012-08-05 16:54, Georgios Petasis wrote:
Dear Massimo,
Since there is some interest, I am trying to build a windows binary
for windows (using the 32 bit distribution from apache, cmake and
microsoft compiler).
I have made some progress, but I have a few problems:
a) Where is "SERVER_CONFIG_FILE" defined? Grep in the (built) linux
sources showed that it is used in mod_rivet.c only, but I couldn't
find where it is defined.
it's in apache2's includes
magnesium:~/Projects/rivet/trunk> grep SERVER_CONFIG_FILE
/usr/local/apache2/include/*
/usr/local/apache2/include/ap_config_auto.h:#define SERVER_CONFIG_FILE
"conf/httpd.conf"
/usr/local/apache2/include/httpd.h:#ifndef SERVER_CONFIG_FILE
/usr/local/apache2/include/httpd.h:#define SERVER_CONFIG_FILE
"conf/httpd.conf"
b) I made some (minor) changes, I hope to provide a patch when all is
done.
great
c) I have made these definitions:
ADD_DEFINITIONS ( -DRIVET_PACKAGE_NAME="Rivet" )
ADD_DEFINITIONS ( -DSTART_TAG="<?" )
ADD_DEFINITIONS ( -DEND_TAG="?>" )
ADD_DEFINITIONS ( -DRIVET_RIVETLIB_DESTDIR="" )
#ADD_DEFINITIONS ( -DSERVER_CONFIG_FILE="" )
#ADD_DEFINITIONS ( -DRIVET_APACHE2=1 )
ADD_DEFINITIONS ( -DRIVET_DISPLAY_VERSION=1 )
ADD_DEFINITIONS (
-DRIVET_PACKAGE_VERSION="${PKG_MAJOR_VERSION}.${PKG_MINOR_VERSION}.${PKG_BUILD_VERSION}")
ADD_DEFINITIONS ( -DRIVET_MAX_POST=0 )
ADD_DEFINITIONS ( -DRIVET_UPLOAD_FILES_TO_VAR=1 )
ADD_DEFINITIONS ( -DRIVET_SEPARATE_VIRTUAL_INTERPS=0 )
ADD_DEFINITIONS ( -DRIVET_HEAD_REQUESTS=0 )
ADD_DEFINITIONS ( -DRIVET_UPLOAD_DIR="C:\\ProgramData\\TEMP" )
ADD_DEFINITIONS ( -DRIVET_NAMESPACE_EXPORT=1 )
ADD_DEFINITIONS ( -DRIVET_NAMESPACE_IMPORT=1 )
ADD_DEFINITIONS ( -DRIVET_NAMEOFEXECUTABLE="" )
ADD_DEFINITIONS ( -DUSE_TCL_STUBS )
ADD_DEFINITIONS ( -DTCL_THREADS )
Do you think any important definition missing?
(Although now I am think it, tcl stubs must not be used...)
if these definitions replace those (auto)generated by the autotools
chain I think they look like complete and reflect the defaults to a
large extent. RIVET_NAMEOFEXECUTABLE is probably unused (it's
automatically generated by the autotools from NAMEOFEXECUTABLE which in
turn is defined from the TCL_PROG symbol pointing to the tclsh shell
file). In ${rivet_root}/Makefile.am there is a shell script which runs
tclsh during the install stage to do some clean up and create the
pkgIndex.tcl files mapping the various packages. My knowledge of CMake
falls short and I don't know how you can take advantage of code in
Makefile.am files when building with CMake, but in case you need to
translate/map between the two approaches, otherwise most of the stuff
that come with Rivet won't work and chances are that also the module
initialization will fail.
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
