Hi, On Wed, April 23, 2014 15:30, Dmitry Koterov wrote: >>
>>> make test TESTS="-n -d extension_dir=/my/dir -d extension=my.so -d >>> extension=other.so tests" >> >> instead of such hacks better run run-tests.php manually. make install >> puts a copy in $PREFIX/lib/php/build/run-tests.php, youcan alsotake the >> one from php-src's root. >> >> php run-tests.php --help >> >> The Makefile wraps this in the test target with some magic trying to >> detect extensions which had just been built but doesn't load others to >> avoid conflicts from new ones with ones from extension_dir. > > > So am I right that there is no chance to make more-or-less standard "make > test" work in this case? I suppose that "make test" is a standard step > that is performed by a typical user of a PECL extension... People will be > confused if plain "make test" does not work. > That's not entirely true, as not every pecl user runs tests anyway. And, after all, when you do this, you'll be rather using "pecl run-tests" than direct make test and it will happen after the extension is installed to the standard path. Regards Anatol -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
