Boost logo

Boost-Build :

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-02-27 14:26:24

----- Original Message -----
From: "William Kempf" <williamkempf_at_[hidden]>
> > > I'd really like to include Boost.Threads in the regression testing.
> >Have
> > > you put any thought into how this could work? I've tried the
> >but
> > > receive an error.
> > >
> > > run libs/thread/test/test_thread.cpp
> > > <dll>libs/thread/build/boost_threadmon
> > > : #args
> > > : #input-files
> > > : #requirements
> > > <include>$(BOOST_ROOT)
> > ^^^^^^^^^^^^^^^^^^^^^^
> >Shouldn't need this part, it's added automatically
> This is nice to know. Is it true only for the status/Jamfile or is this
> a feature in all Jamfiles in Boost?

No, just in status, and only for the testing targets described there (IOW,
"exe" still doesn't get <include>$(BOOST_ROOT)

> > > <runtime-link>static/dynamic
> > ^^^^^^^^^^^^^^
> >Can't use this form in requirements specification. What's your intention,
> >to
> >say that it can be built both ways? In that case, you can just leave it
> >out.
> Then which variant does it choose to use?

I think you're confusing terms. Variants are collections of build
properties. debug, release, and profile are all variants.

Anyway, if you leave it out, it uses whatever is specified by the build. If
the build doesn't specify, it uses the default value for the feature (as
long as the feature is relevant to the toolset). The default for the feature
is its first value as declared in features.jam. In this case, "dynamic".

> > > <threading>multi
> > > ;
> > >
> > > The error is:
> > >
> > > No compatible subvariant found for:
> > > <status!C:!home!boost!libs!thread!build>libb
> > > oost_thread.lib
> >
> >I'm pretty sure that's because it's trying to find a subvariant whose
> ><runtime-link> setting is static/dynamic. That shouldn't work ;-)
> But it does in the actual Jamfiles for the projects. Why should it not
> here?

It "worked" by accident. What did it actually do? Nobody wrote code
intending to make that do anything sensible.

> > > I assume it can't figure out whether to use debug or release?
> >
> >No, debug is the default BUILD setting.
> It might be important to regression test stuff with both BUILD settings.
> For example, the VC++ compiler does some special "magic things" in debug
> builds, such as initialize all pointers to special values. Occasionally
> this can result in bugs that occur in release builds that don't occur in
> debug builds. Of course, this is a regression test and not a unit test,
> maybe you should just ignore what I said... ;).

Almost none of the tests make sense in release mode, since assertions get
compiled away.

> >I tried this, and found a bug in the status/Jamfile which I fixed. I also
> >added your tests. It doesn't link, but I'm sure you can figure that one
> >out.
> Actually, no, that's proving a bit vexing and I *think* it's still a build
> system problem. When I run using jam -d+2 to see what's going on I see
> error as:
> link /nologo /DEBUG
> libboost_thread.lib(tss.obj) : error LNK2001: unresolved external symbol
> __imp__on_thread_exit
> : fatal error LNK1120: 1 unresolved externals
> on_thread_exit() is a method from the boost_threadmon.dll so it appears
> the build system isn't linking against the DLL's import library. Sure
> enough, looking at the contents of test_thread.CMD shows the following:
> Despite the <dll> specification the boost_threadmon.dll's import library
> isn't being linked. Curiously, there is output indicating that the DLL
> built because of the <dll> specification, however.

Hmm, I think I'm going to have to ask Rene to look at this one. He's
responsible for the <dll> dependency handling.

> >I killed the bogus <runtime-link>static/dynamic in your requirements
> >section
> >(perhaps you'd like that in the default-BUILD, but we don't have a
> >default-BUILD section for test targets in status/Jamfile. Maybe we should
> >fix this).
> I think it's important to regression test every variant of the library.
> Debug/release variants are a little debatable, but other variants can mean
> very drastic differences in test results. Which runtime we use is
> that may, indeed, change the behavior of tests.

You can always make two separate test targets:

test-suite threads
: [
run libs/thread/test/test_thread.cpp
: : :
: threads-static

run libs/thread/test/test_thread.cpp
: : :
: threads-dynamic


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