Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42642
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.net designates 213.165.64.20 as permitted sender)
Message-ID: <496F81E0.1090507@gmx.net>
Date: Thu, 15 Jan 2009 19:35:12 +0100
User-Agent: Thunderbird 2.0.0.18 (X11/20081105)
MIME-Version: 1.0
To: Stanislav Malyshev <stas@zend.com>
CC: 'PHP Internals' <internals@lists.php.net>
References: <496E65B2.1070106@zend.com>
In-Reply-To: <496E65B2.1070106@zend.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] build IDs proposal
From: chris_se@gmx.net (Christian Seiler)

Hi,

> I think that it would be better if we adopted more clean and scalable
> solution for that. I propose having one string build ID, which would
> look something like: "API20071006,NTS,Debug,VC8" and would be rquired to
> match exactly in the engine and the module. This should be relatively
> easy to generate when compiling.

I'm generally in favor of that change, however, I'm not quite sure on
the impact of including the Visual Studio version specifier.

I don't have that much experience with PHP on Windows but I have
successfully built PHP extensions with VC8 (i.e. VS 2005 Express) for
PHP 5.2.x. I didn't have any problems whatsoever in using these
extensions together with the official PHP builds (VC6) and Zend Core
(IIRC also VC6) - as long as both VC runtimes were installed on the
corresponding system.

Since VC6 is not available for free download I wouldn't be able to build
Windows extensions for VC6 builds of PHP anymore if the version string
check would inhibit the loading of the extension.

Would any of the PHP Windows guys like to comment on this?

Viele Grüße,
Christian