Well I suggest to stick to status-quo for 5.2 and then let's discuss if/how
to fix after that.
Statically linking libxml2 is yucki, and due to the reason that it's not
common practice on Windows systems you also have the DllMain issue. 

> -----Original Message-----
> From: Edin Kadribasic [mailto:[EMAIL PROTECTED] 
> Sent: Saturday, September 02, 2006 8:55 AM
> To: Andi Gutmans
> Cc: 'Rob Richards'; internals@lists.php.net
> Subject: Re: [PHP-DEV] libxml2/threading/win 2003
> 
> Andi Gutmans wrote:
> > I don't understand what problems you mean. On the contrary, 
> statically 
> > linking in everything makes the system extremely unflexible and 
> > doesn't allow you to upgrade dlls without having to upgrade 
> the whole 
> > PHP build. If libxml2.dll is placed in the same directory as 
> > php5ts.dll I don't see where the problems would come from.
> > On Windows, performance also isn't impacted by dll vs. non-dll as 
> > you'll always have position dependent code and worst case 
> the linker 
> > will relocate the dll.
> > 
> > I feel strongly that statically linking 3rd party libraries and PHP 
> > extensions such as PDO into php5ts.dll will lead to more 
> problems due 
> > to lack of flexibility in people's install. It's a really 
> bad design 
> > decision and I just don't understand how this happened.
> 
> The most optimal way to make the Windows build has been 
> discussed on this list several times during the past 3-4 
> years, including the question which extensions are built in 
> and what libraries to link statically. The design that we 
> came up with has been serving us well during that time.
> 
> Having 5-10 dlls that you need to ship just to run "Hello 
> world" and having to put them in PATH for everything but CGI 
> is suboptimal. Not to mention the fact that there are 
> colissions with other free software that uses the same libraries.
> 
> Since PHP 5.0 we are not bundling MySQL for example. If you 
> were reading bug reports you would know how just that one 
> de-bundled lib created a lot of trouble and confusion among our users.
> 
> Edin
> 

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to