Home > Archive > PHP Documentation > June 2004 > Re: [PHP-DOC] help needed with windows install part of the PHP
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: [PHP-DOC] help needed with windows install part of the PHP
|
|
| Jakub Vrana 2004-06-30, 3:57 pm |
| Steph wrote:
> We seem to have established now that you can't have the one-dir-does-all
> setup when running PHP as an Apache2 module.
I believe it is possible with this configuration:
1. php*ts.dll, php*apache*.dll, php.ini, *.dll in e.g. C:\PHP\
2. C:\PHP\ in PATH
3a. C:\PHP\ in PHPRC (for PHP 4)
3b. C:\PHP\ in Registry entry HKLM\Software\PHP\IniFilePath (for PHP 5)
C:\PHP\ in PATH is necessary only for *.dll (such as libmysql.dll). You
can have these also in other PATH directory (e.g. C:\Windows\System32).
Trailing slashes are necessary in some cases (e.g. 3a).
Nuno Lopes wrote:
> C:\windows\system32\libmysql.dll (without this the mysql extension doesn't load)
It works for me perfectly with libmysql.dll in any PATH directory.
Jakub Vrana
| |
| Nuno Lopes 2004-06-30, 3:57 pm |
| > I believe it is possible with this configuration:
>
> 1. php*ts.dll, php*apache*.dll, php.ini, *.dll in e.g. C:\PHP\
> 2. C:\PHP\ in PATH
> 3a. C:\PHP\ in PHPRC (for PHP 4)
> 3b. C:\PHP\ in Registry entry HKLM\Software\PHP\IniFilePath (for PHP 5)
>
> C:\PHP\ in PATH is necessary only for *.dll (such as libmysql.dll). You
> can have these also in other PATH directory (e.g. C:\Windows\System32).
I think this is the perfect solution!
> Trailing slashes are necessary in some cases (e.g. 3a).
>
> Nuno Lopes wrote:
doesn't load)[color=darkred]
>
> It works for me perfectly with libmysql.dll in any PATH directory.
It doesn't work for me. Which version are you using? I'm using XP SP1.
My apache log (if I delete the libmysql.dll from the system dir):
"PHP Warning: PHP Startup: Unable to load dynamic library
'C:/php/ext/php_mysql.dll' - The specified procedure could not be found.
in Unknown on line 0"
Nuno
| |
|
| > > I believe it is possible with this configuration:
>
> I think this is the perfect solution!
Microsoft advise against putting application libraries in
C:\Windows\System32. And yeah, that was news to me too :I
I should add that if you start bringing registry entries into it you're
going to alienate a lot of newbies. It's not needed, and I certainly don't
see any way it's more straightforward than copying the entire contents of
the PHP directory into the toplevel of Apache\bin if you want to have the
option of running PHP as a SAPI module. You'd only need to alter httpd.conf
to say whether you were using php*apache.dll or the cgi version of php.exe,
which could be in a different directory, and could be a different version
that uses a different php*ts.dll.
The problem with setting a PHP PATH entry is that it excludes the
possibility of other installations.
- Steph
| |
| Jakub Vrana 2004-06-30, 3:57 pm |
| Steph wrote:
> I should add that if you start bringing registry entries into it you're
> going to alienate a lot of newbies.
Sure. We can create a .reg file for them as there were for PWS some time
ago.
> It's not needed, and I certainly don't
> see any way it's more straightforward than copying the entire contents of
> the PHP directory into the toplevel of Apache\bin if you want to have the
> option of running PHP as a SAPI module.
There are of course more possible ways:
1. Copy everything to C:\Windows
2. Copy everything to Apache\bin
3. Copy something to C:\PHP and something to Apache\bin or C:\Windows
4. Copy everything to C:\PHP and set PATH and PHPRC or registry entry
We can document them all. 1 is the most ugly, 4 is probably the most
complicated but the clearest.
Jakub Vrana
|
|
|
|
|