On Sat, Feb 2, 2013 at 9:24 AM, Michiel Beijen <michiel.beijen@xxxxxxxxx> wrote: > Op 2 feb. 2013 02:16 schreef "Good Guy" <xfsgpr@xxxxxxxxxxx> het volgende: > I don't >> mind doing it but whenever I try do build it in VS2010, I always get errors >> and so I gave up. even VS 2012 is out now and it is a very good package to >> create fast binaries. > > As far as I know, the 32 bit binaries that were made available previously > were compiled with MS Visual Studio 6, which is about fifteen years old by > now. I still have copy of that, though. The instructions are a part of the > Apache documentation: http://httpd.apache.org/docs/2.4/platform/ > > So it would be still possible to build it yourself although the defined way > includes using a proprietary and ancient compiler, which is no longer sold. > And of course, sites like Apache Lounge and Apache Haus also distribute > their own binary builds, including 64 bits. There is also an issue that all the 'parts' of the webserver that you assemble together (Apache, mod_php, etc) must be compiled with compatible compilers. mod_php built with VS 2012 will not work with httpd built with VC 6. I believe* this issue came to a head because users began complaining about this issue. The guy who selflessly had been creating the 'official unofficial' builds with VC 6 was suddenly getting grief and issues from people complaining that he wasn't doing it quite how they wanted. Given that what he was doing (and was prepared to do) was not what they wanted, it made sense to stop providing any build, and instead point people towards 'stack' distributions of httpd and php etc from places like ApacheLounge, since this will actually give them what they want. This should also explain why documenting the old build instructions is not overly useful - they would document a build system that doesn't build what the users wanted. Cheers Tom * 'I believe', because I don't use windows personally, and so issues like this are really only noise to me, I've not cared to look in great detail. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|