<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Apr 29, 2013 at 11:13 AM, Philippe Cerfon <span dir="ltr"><<a href="mailto:philcerf@gmail.com" target="_blank">philcerf@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi.<br>
<br>
I've always thought one of the main objectives of cmake was being<br>
portable, right?<br>
So I was looking for a way to let the user (i.e. the person building a<br>
project) choose how he wan't to link each external library (i.e. not<br>
the ones built as targets by my project), depending on what that lib<br>
supports and (when my own code supports it:) dynamically loaded via<br>
e.g. dlopen.<br>
<br>
But it seems that I cannot even tell CMake (in a portable way) that it<br>
should use static or dynamic linking for some external lib (not to<br>
talk about the core libs like libc or libstdc++).<br>
Of course I can work around this any manually search for e.g. .so and<br>
.a files... but that woudln't be portable anymore... not to talk about<br>
different linkage options per linker... so ideally CMake should (IMHO)<br>
take care of all this (for each supported platform/linker).<br>
<br>
<br>
Am I missing something? Or is that just som major deficiency in the<br>
portable-part?<br></blockquote><div><br></div><div>Static linking of external libraries is just a weird thing to do.<br><br></div><div></div><div>Ian<br></div></div></div></div>