[Boost-bugs] [Boost C++ Libraries] #8458: -DBOOST_THREAD_DONT_USE_CHRONO in thread.obj.rsp but not explicitly set

Subject: [Boost-bugs] [Boost C++ Libraries] #8458: -DBOOST_THREAD_DONT_USE_CHRONO in thread.obj.rsp but not explicitly set
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-04-18 13:46:40

#8458: -DBOOST_THREAD_DONT_USE_CHRONO in thread.obj.rsp but not explicitly set
 Reporter: lukeocamden@… | Owner: anthonyw
     Type: Bugs | Status: new
Milestone: To Be Determined | Component: thread
  Version: Boost 1.53.0 | Severity: Problem
 Keywords: |
 Wondering if anyone can reproduce this on Windows. In my setup I don't
 specify BOOST_THREAD_DONT_USE_CHRONO anywhere but it appears in the
 generated rsp files which are used to build boost. Unless I'm doing
 something wrong this would contradict the documentation at
 http://www.boost.org/doc/libs/1_53_0/doc/html/thread/build.html which

 "Boost.Thread uses by default Boost.Chrono for the time related functions
 defined. The user should define BOOST_THREAD_DONT_USE_CHRONO for compilers
 that don't work well with Boost.Chrono."

 An unfortunate consequence is that boost::thread::try_join_until(const
 chrono::time_point<chrono::system_clock, chrono::nanoseconds>&) is marked
 with dllimport but is not actually exported by the boost thread dll.
 LNK2001 ensues!

 I attach a patch which seems to fix the problem for me.

Ticket URL: <https://svn.boost.org/trac/boost/ticket/8458>
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:12 UTC