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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
