Re: [INTERNALS-WIN] RE: [PHP-DEV] Differences in VC6 and VC9 Windows builds and MSSQL Driver.

On Fri, Jan 2, 2009 at 11:08 PM, Uwe Schindler <[email protected]> wrote:
>> > On a side note... would you advocate linking against a 10 year old
>> glibc?
>>
>> It is???  01/19/2008 1:30a prod rev 6.1.8638.18000 file rev 7.0.6001.18000
>> properly titled "Windows NT CRT DLL".
>>
>> Spend some time in depends.exe walking through the Vista/2008 server
>> shipping files.  If MS trusts it, so do I.
>
> To note: all binaries coming with recent windows versions (that are not
> .NET), e.g. explorer.exe, paint.exe and so on, are linked against the good
> old msvcrt.dll. And because of this, msvcrt.dll is the only CRT, that is
> distributed with every windows version (since 98 or so).
>
> And as you can see, the version of the latest msvcrt.dll is rather new and
> is so officially supported by MS.
>
> Further infos:
> http://kobyk.wordpress.com/2007/07/20/dynamically-linking-with-msvcrtdll-usi
> ng-visual-c-2005/

The CRT is there for BC reason.

With the risk to sound harsh, to keep using this CRT for PHP is not an
option. I do not have any issue to provide the VC9.0 with our builds
(installer or binaries zip). There is also projects providing VC9
builds for apache and perl (along other) and they are very successful
(growing community and quality of the builds).

I think we should better focus on working with VC9+ and to prepare the
next generation builds so we will not have to deal with the CRT issues
anymore (be with the manifests or any other solution that we may
find). But to still rely on the CRT "because it is here and has been
here for more than a decade" is like shooting ourselves in the foot :)

Important note: MSFT is working with us (besides me) and on apache ()
to test VC9+ support or more generally the full wamp stack on windows.
That will definitively make our life easier during this move.

Cheers,
-- 
Pierre

http://blog.thepimp.net | http://www.libgd.org