<div class="gmail_quote">On Sun, Apr 19, 2009 at 3:42 PM, Mike 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;">
<div class="im">I think at this point the FindBoost.cmake file is just going to have<br>
to have the same options that BJam has for building boost in all of<br>
its variations:<br>
<br>
Shared or Static libraries<br>
Debug or Release<br>
Static or Dynamic C++ Runtime Link<br>
</div></blockquote><div><br>I like your idea obviously, I'm just trying to think of a way
to do it without deprecating Boost_USE_STATIC_LIBS. The most straightforward solution would be to require the user to define Boost_USE_STATIC_RUNTIME or something like that to get the "-s", but this would also change behaviour on WIN32. This doesn't seem acceptable to me.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
Just another thing to add to the mix of possibilities.<br>
<br>
</div>What would _really_ be helpful is if we could simply get the current<br>
Boost build system (BJam) to just create a "UseBoost.cmake" file then<br>
all of these issues would just go away. Wouldn't that just be a<br>
Utopian solution. ;-)</blockquote><div><br>This might be helpful but could also backfire. We have a giant directory of boost builds at work, for example. Depending on the project we're using them for sometimes we need shared libraries and sometimes static.<br>
</div></div><br>-- <br>Philip Lowman<br>