Re: [Boost-users] Compiler wants to link to threading library all of a sudden

Subject: Re: [Boost-users] Compiler wants to link to threading library all of a sudden
From: Joshua Boyce (raptorfactor_at_[hidden])
Date: 2012-02-09 11:22:01

On Thu, Feb 9, 2012 at 12:54 AM, Crispin Cooper <cooperch_at_[hidden]> wrote:

> On 07/02/2012 15:56, Lars Viklund wrote:
>
>> I would reckon that shared_ptr most probably has some thread safety
>> primitives, and the other types might have internal mutexes as well.
>>
> I just tested shared_ptr on its own - it doesn't try to link.
>
> Is this something that is changing with the previous or current release?
>  Won't additional locks cause overheads, and is there a global #define I
> can set to disable them?
>
>
> Crispin
>
> --
> Dr Crispin Cooper
> Sustainable Places Research Institute
> Cardiff University
>
> ______________________________**_________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/**mailman/listinfo.cgi/boost-**users
>

>

I believe the cause of the behaviour you're observing is not necessarily
additional locks, but instead that the implementation of boost::mutex has
changed (to add a C++11 interface or something similar), and in the process
has moved from header-only to requiring linking.

This is all from my memory of skimming the developer list though, so you
may want to check out the archives for more information.