Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37724
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain isdg.net designates 208.247.131.9 as permitted sender)
Message-ID: <4831C9CA.8080806@isdg.net>
Date: Mon, 19 May 2008 14:41:14 -0400
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: nternals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: LIBXML conflict
From: hsantos@isdg.net (Hector Santos)


Pierre Joye wrote:

>> Now, of course, you might not be able to learn all this until
 >> some one (outside the inner loop) confronts these issues.

> The thing is that there is a golden rule on Windows and for PHP
> windows: Always use the same library versions and the same compiler.
> 
> For the compiler, it is VC6 for every released version. 2k5 support
> will be provided for 5.3+.
 >
 > Now, I really think that such discussions belong to php-internals
 > and not in a private sphere.

Good point, which begs the the issue:

     For VC6.0 compiling, only the SDK for this one should be used.
     I believe the last compatible one supported was Windows 2003 SDK.
     But 2000 SDK is the nice fitting one.

However, the PHP Building From Source web site has indicated to download
the 2005 SDK.  That might be ok, but it does introduce mismatches if one
is using vc6 (for whatever reason).

The other question is what part of the SDK doe PHP need, for what?  OLE?
Does the pure raw PHP2TS.DLL (no extensions), need it?

I just finished duplicating an release build of PHP5TS.DLL (PHP 5.2.6) I
find the following is required:

- 1998/06/17 00:00:00 | 65372    | oldnames.lib
- 1998/06/22 00:00:00 | 146332   | odbc32.lib
- 1998/06/22 00:00:00 | 75418    | odbccp32.lib
- 2000/08/23 19:29:06 | 235942   | msvcrt.lib
- 2001/05/06 16:50:00 | 84486    | oleaut32.lib
- 2001/06/03 02:13:14 | 150902   | advapi32.lib
- 2001/06/03 02:13:28 | 78144    | ole32.lib
- 2001/06/04 15:43:26 | 182168   | kernel32.lib
- 2001/07/04 00:59:42 | 139502   | user32.lib
- 2001/07/26 00:29:38 | 77128    | shell32.lib
- 2001/07/26 00:29:42 | 1265694  | uuid.lib
- 2001/07/26 00:29:44 | 39282    | ws2_32.lib
- 2003/10/25 14:58:58 | 960150   | iconv_a.lib
- 2008/01/11 07:15:58 | 2944956  | libxml2_a_dll.lib  (2.6.31 rrichards)
- 2008/05/13 21:18:47 | 159308   | resolv.lib
- 2008/05/17 09:00:28 | 10760    | zlib.lib

and this is for a PURE vc6.0 with its compatible 2001 PSDK.  No mixing
of 2005 SDK or platform related stuff.

I would love to assist in getting this cleaned up for PHP. If PHP 5.3 is
going for vs2005, thats fine. I welcome that,  but IMO a final lock on
PHP 5.2 under VC 6.0 should be stabilized, especially since, IMV,
something went wiery after 5.2.5 which is pretty darn stable.

I already have end-users telling me that they need to put old 5.2.5
extensions into their 5.2.6 installations because of issues.

-- 
Hector Santos
Santronics Software, Inc.