$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: Khassapov, Alex (Alex.Khassapov_at_[hidden])
Date: 2008-03-27 22:14:52
Hi Volodya,
 
I tried the generator idea - still have the same problem:
 
/opt/boost-build/build/generators.jam:951: in ensure-type from module
generators
error: target { t_compliance_filter.py. } has no type
 
The same behavior - it doesn't recognise .py files - I was getting by
simply using unit-test rule.
 
Which brings the next question - boost-build does have python.jam module
with some testing functionality specific to Python.
 
Whent I try:
 
using python : 2.5 : /usr/local/bin/python ;
testing.make-test run-pyd-output : t_compliance_filter.py ;
 
I get the following error:
 
/opt/boost-build/tools/python.jam:1153: in python.capture-output
*** argument error
* rule common.variable-setting-command ( variable : value )
* called with: ( PYTHONPATH :  )
* missing argument value
 
I suspect that (1) the rule expects at least two sources and/or (2) it
works only on Windows/Cygwin, but we use Solaris.
 
Any further ideas?
 
Regards,
Alex
 
-----Original Message-----
From: boost-build-bounces_at_[hidden]
[mailto:boost-build-bounces_at_[hidden]] On Behalf Of Vladimir Prus
Sent: Thursday, 27 March 2008 4:53 PM
To: boost-build_at_[hidden]
Subject: Re: [Boost-build] unit test without source
 
Khassapov, Alex wrote:
 
> Hi,
> 
>  
> 
> I wonder if there's a rule I could use to run unit tets which don't
> require source, i.e. simply execute python scripts?
 
No. unit-test assumes that the sources is either EXE, or something
convertible to EXE. Making unit-test run whatever is passed to it
will mess up the current behaviour.
 
However, to get what you want you can:
 
1. Just use the 'make' rule.
2. Use the following:
        
        import type ;
        import generators ;
 
        type.register UNIT_TEST_RAW : UNIT_TEST ;
        generators.register-standard testing.unit-test : : UNIT_TEST_RAW
;
        
        unit-test-raw something : script.py ;
 
(This presently assumes that "." directory is in PATH)
 
Does this help?
 
- Volodya
 
 
_______________________________________________
Unsubscribe & other changes:
http://listarchives.boost.org/mailman/listinfo.cgi/boost-build