On Tue, 3 Aug 2004, Gabor Hojtsy wrote: > >>>http://testes.aborla.net/phpdoc/install.windows.html > >>>http://testes.aborla.net/phpdoc/faq.installation.html#faq.installation.addtopath > >>> > >>>diff: http://testes.aborla.net/win.install.diff > >> > >>Just a few notes :) > >> > > > >>8. It is still not clear to me, how php[45]ts.dll is found by > >> a CGI and an SAPI module setup, and what part of the install > >> instructions guarantee that it will be found at the default > >> place, where someone unzips PHP. > > > > Guaranty for SAPI module setup to find php[45]ts.dll is the fact that it sits > > in the same folder as the SAPI dlls. This is true for PHP 5 as the zip is > > packaged this way and for PHP 4 by copy/move sapi dlls from sapi folder to > > the main folder php-4.x.y is unzipped. > > The "move all SAPI dlls to the root PHP folder" instruction is missing > from the docs. It is advised that for the servers to find php4ts.dll, > c:\php needs to be on the PATH. But if people don't move the sapi dlls > to the PHP root folder, the instructions will not work. AFAIK. Nuno, > what do you think?
Also, some PHP extensions require additional DLL's available to work so we need a place to refer confused Windows users on where to put these and how to make them available to PHP. Right now most (all?) extensions that need additional DLL's tell the user to copy them into their system folder but since this is no longer the preferred method how about: This extension requires additional DLL's in order to work, be sure that example.dll and example2.dll are available to your systems PATH. See this FAQ entry for how to do this. I'm referring to extensions where PHP includes all the needed DLL's above. Locations for those extra DLL's are (AFAICT): PHP 4 -> phproot/dlls/* PHP 5 -> phproot/* Granted if they setup PHP via "the PATH method" this won't be a problem but it's still another issue to consider, an issue I'm running into while implementing the PECL docs. Regards, Philip
