In a thread on the mod_perl list about building Apache::Dispatch on Win32 using mod_perl 1, Steve raised the point about the entry in Apache::MyConfig pointing to mod_perl.lib referred to the source location. For building 3rd party modules, it would be more convenient if mod_perl.lib was, first of all, installed into the Apache/ tree, and secondly, if Apache::MyConfig pointed rather to this location. The patch below to the current cvs Makefile.PL carries this out. In order to do this, I dropped support for being able to build mod_perl on Win32 using an Apache source tree, and instead now demand that APACHE_SRC point to an installed Apache/ directory (which it could before) - otherwise, the logic of trying to figure out where to put what becomes pretty involved. I've also dropped support for Apache versions that use ApacheModulePerl.dll as the name of the mod_perl library, rather than mod_perl.so - these are quite old Apache versions, and shouldn't be used especially on Win32 due to security holes. If this patch is OK, I'll make sure to specify these in the Changes and INSTALL.win32 files.
Shooting in the dark: isn't that sort of late to do such drastic changes like dropping builds against the source at this point for mp1? All books out there document it as working. Would it be too hard to keep it as before and fix things that don't work? On the other hand it's quite possible that nobody on win32 builds mp1 from source at all. Just an idea...
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
