Subject: Re: [Boost-bugs] [Boost C++ Libraries] #6644: Windows: auto_link.hpp incorrectly errors with "Mixing a dll boost library with a static runtime is a really bad idea..."
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2015-07-05 04:04:18
#6644: Windows: auto_link.hpp incorrectly errors with "Mixing a dll boost library
with a static runtime is a really bad idea..."
-------------------------------+-------------------------------------------
Reporter: noloader@⦠| Owner: johnmaddock
Type: Bugs | Status: reopened
Milestone: To Be Determined | Component: config
Version: Boost 1.48.0 | Severity: Problem
Resolution: | Keywords: Windows auto_link /MT /MD DLL
-------------------------------+-------------------------------------------
Changes (by darthpjb@â¦):
* status: closed => reopened
* resolution: worksforme =>
Comment:
Apologies for the double-post, but this issue-tracker seems to be having a
few problems at the moment.
Replying to [comment:11 darthpjb@â¦]:
> I can both confirm that this issue is still present - and also that it
is still caused by boost-python.
> If BOOST_PYTHON_STATIC_LIB is not defined, python defines BOOST_DYN_LINK
- and prevents static linking of all boost libraries.
This appears when attempting to static-link boost v1.58 into a project
using MSVC-12.0, using the /MT /MTD runtime-options.
without knowing that BOOST_PYTHON_STATIC_LIB must be defined, this
prevents the use of boost in this scenario.
Unless there is some reason why boost-python itself cannot be statically
linked (which doesn't appear to be the case), this behavior is not only
highly-problematic, but potentially breaking.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/6644#comment:12> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:18 UTC