On 1/19/2012 5:29 AM, Pierre Joye wrote: > 2012/1/19 Ángel González <keis...@gmail.com>: > >> Such binaries wouldn't be compatible with IIS, but mingw seems preferible >> to the legacy VC6 for use with the oficial Apache binaries.
A couple of things to remember; msvcrt.dll is quite actively maintained, even when it's maintained against the interests of php or the c language standards bodies. This would not be true of msvcr70.dll, for example. Actively supported is msvcr100.dll, of VisualStudio 2010, and that is what the httpd project expects to ship some httpd 2.4.0 binaries with. But the msvcrt.dll itself is neither less or more maintained so far than the per-studio-release flavor. It's a shame that the NT/kernel team and the VisualStudio team simply can't get along. Any mingw/gcc build is going to bind right back to msvcrt.dll, nullifying whatever train of thought you were pursuing. There are php-specific defects that MS has chosen to err on the side of incompatibility to spec. > There is no such thing like "official apache binaries", they provide > some as conveniences. Just as with php; these are open source, we give you the source. What you the user proceed to do with it is with our blessings :) This is one of the advantages of keeping build systems and dependencies as accessible as possible, something I consider a flaw in php's win (and aix, solaris and hpux support), and a laudable goal of the coapp effort (all the way through pushing upstream their own shallow fork fixes). -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
