make install; where do .di files go?

[Nick Sabalausky]

On Tue, 16 Oct 2012 17:48:54 +0200
Jordi Sayol <g.sayol at yahoo.es> wrote:

> Al 16/10/12 17:17, En/na Manu ha escrit:
> > On 16 October 2012 18:09, Jacob Carlborg <doob at me.com
> > <mailto:doob at me.com>> wrote:
> > 
> >     On 2012-10-16 16:01, Iain Buclaw wrote:
> > 
> >         /usr/[local/]include/d is the standard path.  Each compiler
> > tends to have it's own subfolder here anyway...
> > 
> > 
> >     DMD doesn't look anywhere outside of its folder by default.
> > 
> > 
> > Well, that's obviously crap. What is the approach most people take
> > when they want to install their library? I'll just do what's
> > considered standard...
> 
> Linux dmd deb/rpm packages installs "/etc/dmd.conf" file which
> contains the modules/interfaces paths. The easiest way to add another
> path for your library in Linux is to create a "pkg-config" file.

Would that be Debian-specific though?

> There are some D libraries deb packages containing a "pkg-config"
> file (.pc) on the apt repository https://code.google.com/p/d-apt/
> 
> > 
> > Can DMD just be fixed to include [local/]/include/d in it's default
> > search paths? I presume GDC and LDC already look there?
> 
> Linux dmd will not include /usr/include/d path by default to avoid
> conflicts with ldc1 (tango) "object.di" incompatibility, and I
> recommend you to not use this path for that reason.
> 

Then we can use '/usr/include/d2'. Problem solved ;)