Re: Re: Documentation problem

At 14:40 12.07.2001 +0100, Phil Driscoll wrote:

On Thursday 12 July 2001 13:58, Daniel Beulshausen wrote: no that's wrong. common windows style is to put dlls into the system folder, first to make them available to every program, second to avoid stale dlls. Well I don't know of any situation where any of the php dlls are going to be shared by any other programs, and most of the related problems I see on the list are due to 'forgotten' dlls in the system folder (i.e. out of sight of the user at upgrade time). I don't feel strongly enough about it to argue too much for a change in how we do it, but my instinct is only to put things in the system folder which are actually going to be shared.

if the extensions depends upon another dll it's most likely shared with other programs, otherwise we use static import libaries in favour of dlls. i.e. for the oci8 extension you'll need to have the oci8 client libaries installed which are used by other oracle client programs as well. this applies for most database extension which rely upon client dlls to be present, most of them share their interface by putting the dlls into the system folder. but it applies for many other "php extension" - "external program" relations, and i can list really few here :) daniel /*-- daniel beulshausen - daniel@php4win.de using php on windows? http://www.php4win.de