Subject: Re: [Boost-build] linking Boost.Test in a project outside boost
From: Mathieu Champlon (m.champlon_at_[hidden])
Date: 2013-05-10 04:10:50
On 09/05/2013 23:58, Thomas Suckow wrote:
> I don't really understand the "Super Fancy Magic Linking(tm)" that
> happens when msvc is used either. But for some reason it decided it
> wanted the multi-threaded version but by default Boost.Build compiles
> single threaded versions. On linux, it would have worked. Easiest
> solution I know of is to use the multithreaded version and call it a
> day, I doubt it really matters anyway (what is a clock cycle or 2).
With msvc there's the auto-linking feature which decides from the code
which .lib must be looked for (see Auto-Linking in
I just realized that adding <define>BOOST_ALL_NO_LIB to deactivate it
actually also fixes the issue.
I was pretty sure I had tried it... Anyway I think I'll use that instead.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk