> In system path (e.g. system32): the underlying extension libs (e.g. > libmysqli.dll) - the alternative is to hold them locally whereever you want > them, but if you do this you'd need a separate copy in apache2\bin and > anywhere a php.exe needs them. > > In apache2\bin: copy of php5ts.dll, copy of php.ini
I don't have any file in the apache dir... I've made a test, and if you copy the php.ini file to the apache dir, it will parse it, instead of the php.ini file in the windows folder. > In path_to_wherever_you_like: php5apache2.dll and php's dynamically loaded > libraries (e.g. php_mysqli.dll), any other versions of PHP (cli/cgi) you > fancy keeping there, a different copy of php.ini if you like (NB you could > even load PHP-GTK from there because you'd be using an entirely separate PHP > binary & ini to do so). > > Path given for both Apache's LoadModule configuration and PHP's > extension_dir ini setting in apache2\bin need to match > 'path_to_wherever_you_like'. > > My big question is, why wasn't this an issue under PHP 4? Is it a bug or a > feature, and if so which version's correct? I think that developpers should take a look into this, so that we could set apache+php without copying any files to a non-php folder. Nuno
