Re: [jamboost] Re: Suggested alteration of boost-base.jam

From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-01-25 23:23:33

Robert Ramey wrote:
> 
>>And I don't see errors when building. What errors are you talking
>>about? How do I reproduce them?
> 
> Here is my problem
> 
> a) when running from a test (I think)

I see the error only when testing. And my answer to the "should I 
commit" is, _no_. BBv1 is correct in giving an error in this situation. 
Although the error is no informative, it's not something that's worth 
improving.

The basic problem is that you have tests (run-test) which depend on the 
wserialization library, but you are telling BBv1 not to build that 
library in some circumstances. This presents a problem to the tests that 
depend on that library as they can't build because of missing dependency.

To get what I think is the effect you want.. Is to add the <build>no 
requirement on the tests themselves. This would cause the entire test to 
be skipped which prevents the error from showing. For example here's 
what I did to not get the error:

===================================================================
RCS file: /cvsroot/boost/boost/libs/serialization/test/Jamfile,v
retrieving revision 1.14
diff -u -r1.14 Jamfile
--- Jamfile	1 Nov 2004 04:56:59 -0000	1.14
+++ Jamfile	26 Jan 2005 04:11:26 -0000
@@ -39,6 +39,10 @@
rule run-invoke ( test-name : sources * : defn * )
{
Echo $(test-name) ;
+ local test-with-wide-char-io-support = ;
+ if boost_wserialization in $(sources:G=:D=) {
+ test-with-wide-char-io-support = wide-char-io-support ;
+ }
# debug
local tests = [
run
@@ -49,6 +53,7 @@
: # input files
: # requirements
std::locale-support
+ $(test-with-wide-char-io-support)
# <threading>single
# <runtime-link>static
<stlport-iostream>on
@@ -82,6 +87,7 @@
: # input files
: # requirements
std::locale-support
+ $(test-with-wide-char-io-support)
# <threading>single
# <runtime-link>static
<stlport-iostream>on
===================================================================

This is assuming that the "wide-char-io-support" rule is already defined 
in the build/Jamfile. This produces messages like:

test_polymorphic_text_archive
test_polymorphic_text_warchive
**** skipping build of 
<@boost!libs!serialization!test>test_polymorphic_text_warchive.test; 
toolset= cw variant= debug ****

And more importantly those white cells you see in some of the python tests.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq