Hi,
I've attached a diff for Win32 against the current cvs
mod_perl that does three things ....
- enables ModuleConfig on Win32: this required adding
the ModuleConfig.c to mod_perl.dsp, as well as adding
perl_call_handler and perl_get_startup_pool to mod_perl.def.
I tested this out with a relatively simple module, for
which it worked fine.
- copies the Apache and mod_perl header files into the
Perl tree, so that Apache::src can be used on Win32.
This works only when building mod_perl by giving APACHE_SRC
to 'perl Makefile.PL'. By defining $APACHE_SRC through this
in the top-level Makefile.PL, most of what needs to be done
is already there, except for the mod_perl header files.
The modules/src test is then also enabled for Win32.
- defines the hooks so that the internal/stacked test can be
run. This was done by defining $EVERYTHING in the top-level
Makefile.PL (if APACHE_SRC is given), but disabling PERL_SSI
and PERL_SECTIONS. I'm not sure this is the right thing to
do for Win32, but ... Enabling the test then also involves some
changes to t/conf/httpd.conf-win32 to require docs/stacked.pl
and to set the <Location> used in the test.
All tests passed with perl-5.6.1 (compiled with ActivePerl
compile-time flags) using Apache_1.3.20.
I was looking at these because, first of all, wanting to see
if ModuleConfig works on Win32, and also because in
building mod_perl-2.0 for Win32 it seems better not to
have so many if ($Is_Win32) exceptions - the above
is closer in spirit to the Unix build. For these I guess
it would be nice to get some experience and work out
the bugs in a stable environment ...
best regards,
randy
mc.diff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
