[Scons-dev] detect and where_is
Gary Oberbrunner
garyo at oberbrunner.com
Mon Jan 7 21:40:32 EST 2013
On Mon, Dec 31, 2012 at 6:24 AM, Russel Winder <russel at winder.org.uk> wrote:
> The detect function in TestSCons.TestScons fiddles with variables and
> then calls where_is. The where_is function uses the user's PATH by
> default. This means where_is returns True in situation where SCons has
> no access to the executable. This means that using the where_is function
> to determine whether a test should run is completely useless since it
> effectively lies :-(
>
> So what is the SCons idiom for determining whether an executable is
> accessible to SCons when executing?
>
You've got it right -- the tests (can) use different logic than SCons.
There's perhaps some value in keeping them separate so the tests have
maximum flexibility, but basically you're right. There's no great way to
do it now since many tools' exists() method just returns True.
--
Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20130107/8d9d9130/attachment.html>
More information about the Scons-dev
mailing list