On Sun, 14 Oct 2001, Randy Kobes wrote: > - 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 ....
thanks, that's in. if we can prune anything, that'd be great. > - src/modules/perl/modperl_filter.c: to fix a typedef for Win32 i added a MP_FUNC_T macro for this, since i'm pretty sure there are more of these. > 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 ... a pleasant surprise :-) > 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? i was hoping we could have something like the Apache::Build::write_src_makefile for win32. to generate one or both of a .dsp or Makefile for nmake. this is why all the source files and such are stored in variables so hopefully we don't have to hardcode anything/have a static .dsp file like 1.x has. thanks again randy! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
