On 08.04.2009 05:46 Randy Kobes wrote: > You're right that problems can arise when using components that were > compiled with different versions of VC++. There is a Win32 binary > version of Apache/2.2.11 available from > http://httpd.apache.org/download.cgi, which should be compatible with > ActivePerl.
Yes, I know but it doesn't have an up-to-date mod_ssl and after been bitten several times from openssl-dll mismatch I didn't want to run the risk again. So I ended up reinstalling everything (VC6, SDK, MASM, tools...) in a fresh Virtual Maschine and I was finally able to compile everything, so I guess something was broken in my original environment. > If you're having problems compiling the Apache server, the > mailing lists for either httpd (http://httpd.apache.org/lists.html) or > apr (http://apr.apache.org/mailing-lists.html) would be a good place > to report problems. Good point but as I said it is working now. And I hoped for some broader info about what others are using to build their development environment under Windows. Either for building it yourself (VC6, newer VC, Mingw, perhaps even the Intel compiler?, which tools and additional libraries, helpers? [nd]make?) or from ready made packages (XAMPP, apache.org binaries, activestate, strawberry, others?) that do actually work well together as a solid and well maintained mod_perl environment. For the time being I answered it myself with still going the VC6 route but since this is such an old compiler I am also looking for (proven) alternatives to be prepared when this is becoming a dead end like it seemed to be when I was unable to build apache 2.2.11 with it. -Michael
