Re: [Boost-users] [build] Unexpected static libraries in 1.63

Subject: Re: [Boost-users] [build] Unexpected static libraries in 1.63
From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2017-03-14 03:01:39

In the develop branch I've deleted the non-intrusive exception_ptr support
form Boost Exception and the build step it required. This feature was
experimental, always disabled by default, only worked on some MSVC versions
and probably wasn't used by anyone.

That said, if anyone reading this has #define
BOOST_ENABLE_NON_INTRUSIVE_EXCEPTION_PTR in his build system please speak
up. :)

Emil

On Sun, Mar 12, 2017 at 10:33 PM, Gavin Lambert via Boost-users <
boost-users_at_[hidden]> wrote:

> On 2/03/2017 12:28, I wrote:
>
>> I've recently rebuilt Boost 1.63 locally for both Windows and Linux,
>> requesting dynamic libraries only (link=dynamic).  However several
>> libraries are still being built in both static and dynamic forms:
>>
>>  - chrono
>>  - system
>>  - timer
>>  - unit_test_framework
>>
>> Additionally some libraries are being built only in static forms:
>>
>>  - exception
>>  - test_exec_monitor
>>
>> I assume the latter is intentional, as presumably some libraries can
>> only work as static libraries.  Is the former intentional or a bug?  It
>> seems like a bug.  Or do these contain symbols that the dynamic
>> libraries do not?
>>
>
> Any chance the former group of libraries can be fixed before 1.64?
>
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users