----- Original Message ----- From: "Doug MacEachern" <[EMAIL PROTECTED]> To: "Randy Kobes" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, October 13, 2001 9:23 PM Subject: Re: Apache-Test and Win32
> On Sat, 13 Oct 2001, Randy Kobes wrote: > > > Hi, > > Attached is a diff for modperl-2.0/Apache-Test/ as a first > > stab at getting it to work on Win32. The changes include: > > > > - TestMM.pm: in creating the run_tests target, Win32 doesn't > > understand prefixing the command with the environment > > variables, so this was changed for Win32. > > i made the change a little different, so that PASSENV is just empty if > WIN32. does that work ok? Yes, that works fine ... > > > As well, Apache.exe must be in the PATH beforehand. > > should we add the default install path if it isn't already in PATH? Yes, that would be handy ... I guess that involves extracting that from the apache sources used for building modperl ... To that end, I took a look at building mod_perl ... With two small changes (in the attached diffs - Outlook Express wraps things wrong) to: - src/modules/perl/modperl_apache_includes.h : to pull in some Win32-specific include files, and get rid of some warnings about redefinitions of uid_t and gid_t; this is similar to what was done for modperl-1. I'm not sure if all of these include files are needed, and could look later at pruning some .... - src/modules/perl/modperl_filter.c: to fix a typedef for Win32 all the files compile, with just one silly warning about something being used uninitialized. Again, I'm really impressed with how tight the modperl code is, in that it just required these small changes to compile on a foreign platform ... Of course, the library itself wasn't built, as the procedure for that was Unix specific, and so I don't know yet if it works ... But before embarking on that, I was wondering how this should be handled? One possibility, like mod_perl-1, is to make up a VC++ .dsp file, which could then be used to build things using either Visual Studio, or, using msdev, also from the command line. Or should everything proceed from the command line? best regards, randy
modperl_filter.c.diff
Description: Binary data
modperl_apache_includes.h.diff
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
