on Tue Aug 05 2008, Markus Werle
Hi!
I am using VS2005SP1, compiling debug version with MFC in a static lib. No problem for boost libs to auto-select the correct (static) libraries all the time.
Enters Boost.Python which deliberately chooses to ignore my compiler settings and to set BOOST_PYTHON_DYNAMIC_LIB and then later at boost\python\detail\config.hpp, line 128:
#ifdef BOOST_PYTHON_DYNAMIC_LIB # define BOOST_DYN_LINK // <---- BOOM! #endif
which obviously is properly catched in auto_link.hpp, line 292
Everything works as expected if I define BOOST_PYTHON_STATIC_LIB, but I do not understand why I have to take that extra effort. All other boost libs play together with my the compiler settings ...
Am I missing something?
Probably not. Can you open a ticket at http://svn.boost.org ? A patch would be very, very much appreciated too! Thanks, -- Dave Abrahams BoostPro Computing http://www.boostpro.com