[Scons-dev] Testing non-core tools

[Russel Winder]

Dirk,

Thanks for getting back to me on this quickly, much appreciated.

On Fri, 2013-07-26 at 19:23 +0200, Dirk Bächle wrote:

> Hi Russel,

> 

> so far I always used the fixture methods from the testing framework with 

> a relative path, like this:

> 

> test.file_fixture('../../../__init__.py','site_scons/site_tools/qt4/__init__.py')

> 

> (example from the qt4 Tool tests). Doesn't this work for you?

> 

> There is also TestCmd::workpath(...), which returns an absolute path 

> with the working directory of the current test as prefix.


Everything I have tried in order to get the tool on the fixture list so
that it is picked up by the SConstruct under test gives:

    EnvironmentError: No tool named 'sometool': not a Zip file:

This means the SConstruct is not finding the tool, it is not on the
path. I am getting to stage being angry :-)

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder at ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel at winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : <http://two.pairlist.net/pipermail/scons-dev/attachments/20130726/b3ba5dba/attachment.pgp>