On Wed, Dec 7, 2011 at 8:22 AM, Sebastian Bergmann <sebast...@php.net>wrote:

>  Can somebody look into 
> https://bugs.php.net/bug.php?**id=54514<https://bugs.php.net/bug.php?id=54514>please?
>  This causes issues for CLI tools implemented in PHP that are invoked
>  through Apache Ant, for instance, and need to know the PHP interpreter
>  that is running them.
>
>  See 
> https://github.com/**sebastianbergmann/phpunit/**issues/432<https://github.com/sebastianbergmann/phpunit/issues/432>for
>  an
>  example of how this affects PHPUnit.
>
> --
> Sebastian Bergmann                    Co-Founder and Principal Consultant
> http://sebastian-bergmann.de/                           http://thePHP.cc/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
+1, I also seen workarounds of this missing functionality in the symfony2:

https://github.com/symfony/Process/blob/master/PhpExecutableFinder.php
https://github.com/symfony/symfony/blob/master/tests/Symfony/Tests/Component/Process/PhpExecutableFinderTest.php

PHP_BINDIR is available, and from a quick test, $_SERVER['_'] has the path
for the php binary also (only tested it on linux, cli).

-- 
Ferenc Kovács
@Tyr43l - http://tyrael.hu

Reply via email to