make install; where do .di files go?

Manu turkeyman at gmail.com
Wed Oct 17 05:03:41 PDT 2012


On 17 October 2012 11:48, Jordi Sayol <g.sayol at yahoo.es> wrote:

> Al 16/10/12 22:37, En/na Nick Sabalausky ha escrit:
> >> 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?
>
> This is Linux and C specific.
> In debian/Ubuntu/LinuxMint, with "libgtk-3-dev" and "pkg-config" packages
> installed, just type:
> $ pkg-config --cflags --libs gtk+-3.0
> You'll get all the sources, libraries and some flags that gcc needs to
> properly compile gtk projects.
>
> >> 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 ;)
> >
>
> Is a possibility, but it must be agreed.
>

Well let's attempt to begin that process in that case :)

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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20121017/463fafce/attachment-0001.html>


More information about the Digitalmars-d mailing list