Re: rule unit-test unknown...

From: Karla & Malcolm Cifuentes (malcolm_cifuentes_at_[hidden])
Date: 2005-04-17 11:26:43

I think you need to use this line in your Jamfile
import testing ;

If you read tools/testing.jam you get
"
# For historical reason, a 'unit-test' rule is available which
# has the same syntax as 'exe' and behaves just like 'run'.
"

Not really sure what history is behind this comment, implies run is
prefered though.

Would be nice if some one else could explain why you would ever use run
as opposed to unit-test.

Good luck
mal

"Brian Ravnsgaard Riis" <brian_at_[hidden]> wrote in message
news:<d3s7fe+c2gq_at_[hidden]>...
> 
> 
> $ bjam 
> test\Jamfile:22: in modules.load
> rule unit-test unknown in module Jamfile</c:/src/workspace/d20/test>.
> c:/src/workspace/boost/tools/build/v2/build\project.jam:302: in 
> load-jamfile
> c:/src/workspace/boost/tools/build/v2/build\project.jam:68: in load
> c:/src/workspace/boost/tools/build/v2/build\project.jam:79: in 
> project.load
> c:/src/workspace/boost/tools/build/v2\build-system.jam:100: in load
> c:\src\workspace\boost\tools\build\v2/kernel\modules.jam:259: in 
> import
> c:\src\workspace\boost\tools\build\v2/kernel/bootstrap.jam:120: in
> boost-build
> c:\src\workspace\d20\boost-build.jam:1: in module scope
> 
> Do I have to do anything special to get the unit-test target to work? 
> This is BBv2, obviously. Recent (as in "now") CVS checkout. Tried to 
> define the same target as an "exe" target instead. Compiled and linked

> correctly first time.
> 
> /Brian Riis
> 
> 
> 
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 
> 
> 
>