<div class="gmail_quote">On Fri, Feb 13, 2009 at 8:46 AM, Michael Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Patch attached and also added to the bug report. Actually since it was part of the "ABI" tag it was fairly simple to fix. Now wee need some volunteers to test the patch/fix.</blockquote><div><br>I considered the same patch. Because _boost_ABI_TAG is not used during RELEASE you would miss this case below:<br>
<br>boost_thread-vc80-mt-p-1_38.lib<br><div id=":tj" class="ArwC7c ckChnd">
boost_thread-vc80-mt-p.lib</div><br>One approach would be to make _boost_ABI_TAG be what it should be, the ABI tags, and get rid of _boost_STATIC_TAG. I haven't done much work here but I was thinking building up two versions of the ABI_TAG, one for RELEASE and one for DEBUG incrementally in the order the options are defined by Boost...<br>
<br><br> set( _boost_ABI_TAG "-")<br> set( _boost_ABI_TAG_DEBUG "-")<br> # Build the ABI tag in the following order<br> # "s" => linking statically to the C++ standard library and compiler<br>
# runtime support libraries (MSVC)<br> if(WIN32 AND Boost_USE_STATIC_LIBS )<br> set( _boost_ABI_TAG "${_boost_ABI_TAG}s")<br> set( _boost_ABI_TAG_DEBUG "${_boost_ABI_TAG_DEBUG}s")<br>
endif()<br> # "g" => using debug versions of the standard and runtime support<br> # libraries<br> if(WIN32 AND MSVC)<br> set( _boost_ABI_TAG_DEBUG "${_boost_ABI_TAG_DEBUG}g")<br>
endif()<br> # "y" => using special debug build of Python<br> # libraries<br>etc.<br><br>Then the actual find_library check could be simplified and the code would also be far more readable. Please feel free to complete the patch if you like this approach and have time.<br>
</div></div><br>-- <br>Philip Lowman<br>