On Fri, 12 Sep 2003, Stas Bekman wrote:
Randy Kobes wrote:
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...
That is a good point ... The difficulties I was running into in installing mod_perl.lib, and subsequently make it useable for 3rd party modules, is that it's more useful when put into the installed Apache tree, rather than an Apache or mod_perl source tree, as a user may delete the sources after installation without realizing they may be used later for 3rd party modules. One could keep the option of building against an Apache source tree, and then prompt the user for an installation directory if the source directory is given, but then with the installation directory at hand, there's no use in principle for the source directory.
But now you are talking about a different thing. Above you said:
>>>In order to do this, I dropped >>>support for being able to build mod_perl on Win32 using an >>>Apache source tree,
whereas your real problem is about building extensions. So what I was saying is that we probably need to continue building *mod_perl* as before, however make mod_perl.lib and anything else needed available under the Apache source tree (or I think under the perl lib tree for mp1, since that's where we keep all our mp stuff). Does it make sense?
However, as you say, it may be better not to drop the source support - what I could do is, if an Apache source directory is given, try to make a guess where the installation directory is, and then prompt for confirmation, if a guess is found, or else just prompt for the installation directory.
If you copy it away, you don't need to do that.
__________________________________________________________________ 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]
