Problem with unit-test rule

Stan Blakey wrote:

> When I try to use the unit-test rule I get a message:
> "rule unit-test unknown in module
Jamfile<...."
>  
> exe works fine. I tried in my own jamfile and I tried
modifying the
> hello example with the same results.

You haven't said what version of Boost.Build you're using,
so
I'm going to assume it's CVS HEAD, and you also did not
provide
a complete testcase, so I'm gonna assume something too.

Can you try adding

        import testing ;

at the top of your Jamfile? It appears that such
statement is executed when testing Boost, but is
not executed for a completely standalone project.
If such line fixes the problem for you, I'll apply
a better fix.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Thanks, That did the trick.

Btw, My boost version info is
Boost.Build V2 (Milestone 11)
Boost.Jam 03.1.14

Downloaded this week from sourceforge.

Stan
 

-----Original Message-----
From: boost-build-bounceslists.boost.org
[mailto:boost-build-bounceslists.boost.org] On Behalf
Of Vladimir Prus
Sent: Saturday, June 02, 2007 10:14 AM
To: boost-buildlists.boost.org
Subject: Re: [Boost-build] Problem with unit-test rule

Stan Blakey wrote:

> When I try to use the unit-test rule I get a message:
> "rule unit-test unknown in module
Jamfile<...."
>  
> exe works fine. I tried in my own jamfile and I tried
modifying the 
> hello example with the same results.

You haven't said what version of Boost.Build you're using,
so I'm going
to assume it's CVS HEAD, and you also did not provide a
complete
testcase, so I'm gonna assume something too.

Can you try adding

        import testing ;

at the top of your Jamfile? It appears that such statement
is executed
when testing Boost, but is not executed for a completely
standalone
project.
If such line fixes the problem for you, I'll apply a better
fix.

- Volodya


_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost-build
--------------------------------------------------------

CONFIDENTIALITY NOTICE: This e-mail message, including any
attachments, is for the sole use of the intended
recipient(s) and contains information that is confidential
and proprietary to Applied Micro Circuits Corporation or its
subsidiaries. It is to be used solely for the purpose of
furthering the parties' business relationship. All
unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of
the original message.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus wrote:

[snip]

> Can you try adding
>
>        import testing ;
>
> at the top of your Jamfile? It appears that such
> statement is executed when testing Boost, but is
> not executed for a completely standalone project.
> If such line fixes the problem for you, I'll apply
> a better fix.

Sorry for intruding, but what kind of "fix" would
that be? IMHO I don't 
think that "testing" should be imported
implicitly.

/ Johan


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Monday 04 June 2007 12:45, Johan Nilsson wrote:
> Vladimir Prus wrote:
> 
> [snip]
> 
> > Can you try adding
> >
> >        import testing ;
> >
> > at the top of your Jamfile? It appears that such
> > statement is executed when testing Boost, but is
> > not executed for a completely standalone project.
> > If such line fixes the problem for you, I'll
apply
> > a better fix.
> 
> Sorry for intruding, but what kind of "fix"
would that be? IMHO I don't 
> think that "testing" should be imported
implicitly.

I actually planned to implicitly import 'testing'. Now,
pretty much everything
is automatically imported, with 'testing' being an
exception. Do you think
it's better to require manual import of 'testing'?

- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus wrote:
> On Monday 04 June 2007 12:45, Johan Nilsson wrote:

[snip]

>> Sorry for intruding, but what kind of
"fix" would that be? IMHO I
>> don't think that "testing" should be
imported implicitly.
>
> I actually planned to implicitly import 'testing'. Now,
pretty much
> everything
> is automatically imported, with 'testing' being an
exception.

I didn't know that, did it change recently. Are e.g. path,
os, set,
class, regex now being imported?

> Do you
> think
> it's better to require manual import of 'testing'?

I _personally_ prefer to manually import testing whenever I
need it. I
actually prefer to import most non-basic stuff explicitly -
especially
when the rules end up in the "global namespace",
such as unit-test.

Perhaps it is a bit unintuitive that e.g. importing the
testing module
makes "unqualified" rules available, i.e.
"unit-test" instead of
"testing.unit-test"?

/ Johan







_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build