On 16 October 2012 19:59, Jacob Carlborg <span dir="ltr">&lt;<a href="mailto:doob@me.com" target="_blank">doob@me.com</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 2012-10-16 17:17, Manu wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Well, that&#39;s obviously crap. What is the approach most people take when<br>
they want to install their library?<br>
I&#39;ll just do what&#39;s considered standard...<br>
</blockquote>
<br></div>
I mostly only build from source using git submodules. I have one or two libraries placed in the DMD directory.</blockquote><div><br></div><div>Okay, well I&#39;ll stick with that for now I guess.</div><div><br></div><div>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can DMD just be fixed to include [local/]/include/d in it&#39;s default<br>
search paths? I presume GDC and LDC already look there?<br>
</blockquote>
<br></div>
Preferably I would like a package manager to handle this.</blockquote><div><br></div><div>Well, a solution I can use now would be nice.</div><div>Nominating a directory at least until such an established package manager emerges might be a convenient intermediary.</div>
</div>