On 17 October 2012 11:48, Jordi Sayol <span dir="ltr">&lt;<a href="mailto:g.sayol@yahoo.es" target="_blank">g.sayol@yahoo.es</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">
Al 16/10/12 22:37, En/na Nick Sabalausky ha escrit:<br>
<div class="im">&gt;&gt; Linux dmd deb/rpm packages installs &quot;/etc/dmd.conf&quot; file which<br>
&gt;&gt; contains the modules/interfaces paths. The easiest way to add another<br>
&gt;&gt; path for your library in Linux is to create a &quot;pkg-config&quot; file.<br>
&gt;<br>
&gt; Would that be Debian-specific though?<br>
<br>
</div>This is Linux and C specific.<br>
In debian/Ubuntu/LinuxMint, with &quot;libgtk-3-dev&quot; and &quot;pkg-config&quot; packages installed, just type:<br>
$ pkg-config --cflags --libs gtk+-3.0<br>
You&#39;ll get all the sources, libraries and some flags that gcc needs to properly compile gtk projects.<br>
<div class="im"><br>
&gt;&gt; Linux dmd will not include /usr/include/d path by default to avoid<br>
&gt;&gt; conflicts with ldc1 (tango) &quot;object.di&quot; incompatibility, and I<br>
&gt;&gt; recommend you to not use this path for that reason.<br>
&gt;&gt;<br>
&gt;<br>
&gt; Then we can use &#39;/usr/include/d2&#39;. Problem solved ;)<br>
&gt;<br>
<br>
</div>Is a possibility, but it must be agreed.<br></blockquote><div><br></div><div>Well let&#39;s attempt to begin that process in that case :)</div><div><br></div><div>why include/d2? include/d/ seems much better... what are the chances a library have both a d1 and d2 version which may conflict in include/d?</div>
<div><br></div></div>