[PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: Documentation problem From: Daniel Beulshausen (daniel <email protected>)
Date: 07/12/01

At 12:43 12.07.2001 +0100, Phil Driscoll wrote:
>On Thursday 12 July 2001 12:19, Hojtsy Gabor wrote:
>
> > It is needed IMHO on Win2k. Apache wont start, saying that
> > a needed dll can't be found. You can add c:\php (or whatever)
> > to the PATH, and then it will find them, but it is not better...
> >
>
>Agreed - but only in the case of the php apache module. The php.exe will pick
>up php4ts.dll because they live in the same directory.
>I assume that the Apache module only fails because we choose to ship the
>apache module dll inside the sapi folder instead of in the same directory as
>php4ts.dll.

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. (also if you choose to use multiple sapi's it's not a very good
idea to put the dll into three different places)
in this case the cgi is the exception and not any other sapi module,
because windows also uses the current path to search executables and dlls.

>IMHO it would be better to move the apache module up a directory in the
>distribution rather than advide people to stick things in winnt/system32 or
>similar. We get plenty of support problems which are caused by people
>forgetting to clear out the old junk in their system directories, and I'm
>sure that this would be reduced by having the whole kit and caboodle in the
>same directory. For that matter, I think it would be better for php.ini to
>live there too!

the current structure of the dist is very clean, changing it isn't a good idea.
putting everything into one folder would end up in a mess.
if people don't read the readme it's their own fault, but ignoring the
common practice to put system dll's into system(32) isn't a good idea to
solve this.

daniel

/*--
daniel beulshausen - daniel <email protected>
using php on windows? http://www.php4win.de