I'm trying to get the regex lib (boost 1.28.0) built on win32 (MSVC v6, stlport 4.5.3). The standard build that is provided with regex appears to work fine and I get the full compliment of regex libraries (debug, static/dynamic, etc.). However, when I attempt to build the credit_card_example file, the link fails with unresolved external symbols. I then added the 13 regex source files to a msdev project along with the credit_card_example source file and linked everything statically (using BOOST_REGEX_STATIC_LINK or whatever it is). That worked fine. So this leads me to believe that something is going on with BOOST_REGEX_DECL macro. I put some #pragma message(...) statements into some headers and determined that the macro is being defined correctly. Is it possible that this macro is missing on some functions/classes or is it more likely a build option or macro issue? The first unresolved symbol I have is boost::re_detail::match_results_base<...>::m_free(...) As I was looking around for that symbol, I discovered in regex.hpp that match_results_base did not have BOOST_REGEX_DECL macro on the class definition. I added it and rebuilt and I ended up with more unresolved symbols. So obviously that isn't the direction to go. I have, however, not been able to find the actual definition of m_free yet (still looking). Thanks -Rob
I'm trying to get the regex lib (boost 1.28.0) built on win32 (MSVC v6, stlport 4.5.3). The standard build that is provided with regex appears to work fine and I get the full compliment of regex libraries (debug, static/dynamic, etc.). However, when I attempt to build the credit_card_example file, the link fails with unresolved external symbols. I then added the 13 regex source files to a msdev project along with the credit_card_example source file and linked everything statically (using BOOST_REGEX_STATIC_LINK or whatever it is). That worked fine. So this leads me to believe that something is going on with BOOST_REGEX_DECL macro. I put some #pragma message(...) statements into some headers and determined that the macro is being defined correctly. Is it possible that this macro is missing on some functions/classes or is it more likely a build option or macro issue?
It all links OK for me, I've tried the following combinations: debug-mt debug-mt-dll stldebug-mt stldebug-mt-dll release-mt release-mt-dll which I think covers all the bases. What error messages are you getting? John Maddock http://ourworld.compuserve.com/homepages/john_maddock/index.htm
participants (2)
-
John Maddock
-
Rob Reece