Re: PEAR on Windows
| From: | Shane Caraveo | Date: | Sun, 07 Jul 2002 20:55:12 +0000 |
| Subject: | Re: PEAR on Windows | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-1814@lists.php.net to get a copy of this message | ||
Stig S. Bakken wrote:
On Thu, 2002-07-04 at 10:19, Martin Jansen wrote:I had only one real issue, in pear.in there is @include_path@ and @pear_version@. I am assuming that these get replace during install on linux. Couldn't go-pear do the same for windows, or can we just get rid of them. -c inidir works from pear.bat, and how important is the version anyway ;). ShaneOn Wed Jul 03, 2002 at 11:3839PM +0200, Jonas Koch Bentzen wrote:Since this is a Windows issue, it should be done in the Windows installer IMHO. It would make my life and go-pear's job a lot easier too. :-P - StigMartin Jansen skrev:I don't know much about the internals of PHP's build system, but I think that adding the PEAR directory to include_path during installation is more a job for the guys on php-dev@lists.php.net. Can you post your proposal there and here what they think?On Wed Jul 03, 2002 at 08:3928PM +0200, Jonas Koch Bentzen wrote:Is there any way we could make it do that? The PHP binary must know where the base php directory is, and thus where php/pear is, right?With PHP 4.2.1, does PEAR work out of the box on Windows *without* the user having to add the PEAR directory to his/her include_path as described on http://pear.php.net/manual/en/faq.windows.php ? I'm sorry I can't test this myself - I'm a Linux user.The path is *not* added automatically. (At least that's what happened when I installed the binary package on my windows box here.)