On Mon, Dec 8, 2008 at 10:49 AM, Hendrik Sattler <span dir="ltr"><<a href="mailto:post@hendrik-sattler.de">post@hendrik-sattler.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How do you link against them if you do not know the name? Do you use<br>
that special auto-linking feature of MSVC?</blockquote><div> </div><div>You specify them as library dependencies on the command line. For the
import libraries, I simply use target_link_libraries() in CMake. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Well, it's obvious that boost library naming sucks a lot. I know that<br>
you cannot do anything about that.</blockquote><div><br>This has nothing to do with boost. This is a very common way of labeling import libraries and their corresponding shared libraries. A typical approach is this:<br><br>
library_d.lib <-- Debug library<br>library.lib <-- Release library<br><br>I don't see any issue with this. This is required in order to tell them apart so that one may link against the appropriate library. Of course I would not distribute the debug versions, which I think is where you're confused. When I distribute my application the user is only responsible for ensuring they have the release versions of those libraries.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Again, how do you link against those libraries?</blockquote><div><br>See my answer to your first question.</div>
</div>