<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 11, 2012 at 2:19 PM, Klaim - Joël Lamotte <span dir="ltr"><<a href="mailto:mjklaim@gmail.com" target="_blank">mjklaim@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>My current understanding is that boost don't have a specific default lib dir for different address models, which is the source of the problem as</div>
<div>FindBoost script can't rely on a protocol to find these lib files.</div>
<div><br></div><div>Am I correct?</div></blockquote></div><br><div class="gmail_extra"><br>I am getting back to this because it is becoming more a problem each day for me:</div><div class="gmail_extra">I have several projects that would benefit from a 64bit version, but still need to be provided as a 32bit version too.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra" style>Apparently setting BOOST_LIBRARYDIR does indeed allow to manually specify the library directory.</div><div class="gmail_extra" style>I reported the issue ( <a href="http://www.cmake.org/Bug/view.php?id=14087">http://www.cmake.org/Bug/view.php?id=14087</a> )that this is not documented in the help command</div>
<div class="gmail_extra" style>or maybe it's because BOOST_LIBRARY_DIRS should be used instead but it don't work because BOOST_LIBRARY_DIRS </div><div class="gmail_extra" style>is automatically overriden.</div><div class="gmail_extra" style>
<br></div><div class="gmail_extra" style>In my specific case, as I need to build either the 32 bit or the 64bit version of the applications, </div><div class="gmail_extra" style>I need to specify BOOST_LIBRARYDIR in both cases to be sure the user (other developers starting helping on the project)</div>
<div class="gmail_extra" style>is linking with the correct version instead of relying on BOOST_DIR.</div><div class="gmail_extra" style>This is not perfect but at least the developer can't ignore the issue.</div><div class="gmail_extra" style>
<br></div><div class="gmail_extra" style>I am looking for suggestions to improve the situation, either on CMake or boost, </div><div class="gmail_extra" style>as I'm not sure what to do exactly. I'm willing to subit patches to both to ease</div>
<div class="gmail_extra" style>development of 32+64bits application using CMake and boost, so</div><div class="gmail_extra" style>some directions on how to this issue would be useful.</div><div class="gmail_extra" style><br>
</div><div class="gmail_extra" style>For now I think the simplest solution would be to make b2 use a default 64bit lib directory </div><div class="gmail_extra" style>when the directory is unspecify. Then FindBoost cmake module can rely on this knowledge to try to find the right binaries,</div>
<div class="gmail_extra" style>based on BOOST_Dir, instead of always using the same binaries by default.</div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>Does it seem like a good solution to you?</div>
<div class="gmail_extra" style><br></div><div class="gmail_extra" style>Joel Lamotte</div><div class="gmail_extra" style><br></div><div class="gmail_extra"><br></div></div></div>