On 18 October 2012 12:21, David Nadlinger <span dir="ltr">&lt;<a href="mailto:see@klickverbot.at" target="_blank">see@klickverbot.at</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thursday, 18 October 2012 at 07:29:45 UTC, Manu wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
and 2) I don&#39;t really care where it is, I would just like an answer that is<br>
agree&#39;d by the various compilers, and which is included in each of their<br>
search paths by default. How can one make a build script for their apps<br>
when it&#39;s not consistent where libraries are to be found?<br>
</blockquote>
<br></div>
Just an aside: During the whole discussion, please don&#39;t forget that you also need to compile your library separately for each compiler, as long as they are not ABI compatible (which is still a long way out). Thus, while I don&#39;t think a standard import path wouldn&#39;t be nice to have, the issue doesn&#39;t stand out as a single big problem as it might seem at first.</blockquote>
<div><br></div><div>Really? The D compilers aren&#39;t ABI compatible on Linux?</div><div>Good to know. Cheers!</div><div><br></div><div>Well, for my own purposes, I only intend to interact with bindings for C libs, which, fortunately, are universally binary compatible :)</div>
</div>