Boost logo

Boost-Build :

From: Robert Ramey (Ramey_at_[hidden])
Date: 2005-01-26 01:49:43

Rene Rivera wrote:
> 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:

That is what I did at first and it seemed to work ok. However, there were a
couple of things I didn't like about it.

It didn't address the fact that certains builds are known aprior to be no
supported. So I was desirious of adding the same checking to the build
Jamfile to avoid wasting time for all builds. Once this was done, then it
seemed pointless to include the checks both places. So I removed it from the
tests. I counted on the fact that the tests would be skipped when the
corresponding library failed to build. As it turns out, I was dissatisfied
with that since the test was compiled even though it was known apriori that
it would fail to link. So I ended leaving checks in both the tests and the
library build. This seems kind of crude to me - but I don't have to fiddle
with boost-base.jam - which is fine by me.

So I guess its all resolved.

Robert Ramey


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at