DMD VS2017 Support

Jonathan M Davis via Digitalmars-d digitalmars-d at puremagic.com
Sun Jun 4 16:45:34 PDT 2017


On Sunday, June 04, 2017 16:03:46 Jolly James via Digitalmars-d wrote:
> On Monday, 1 May 2017 at 18:30:53 UTC, Rainer Schuetze wrote:
> > On 01.05.2017 10:03, Igor wrote:
> >> On Monday, 1 May 2017 at 01:54:30 UTC, evilrat wrote:
> >>> [...]
> >>
> >> That was it. It didn't occur to me that this was the problem
> >> because I
> >> payed closed attention during VisualD installation and saw it
> >> properly
> >> recognized where DMD was installed but for some reason the
> >> path wasn't
> >> set in Options. Once I did set it, compile and build worked.
> >> Thanks
> >> evilrat!
> >>
> >> So in conclusion it seems the problem is in VisualD
> >> installation which
> >> doesn't set the path properly even though it recognizes where
> >> DMD is
> >> installed. Hope the author takes a look at this problem so
> >> beginners
> >> wanting to try D don't give up on a problem like this.
> >
> > VS 2017 uses a "private" registry that the Visual D installer
> > doesn't have access to. I'll change the registry location in
> > the next release.
> >
> > Please note that the next dmd installer will also detect VS2017
> > and setup directories correctly in sc.ini:
> > https://github.com/dlang/installer/pull/227
>
> Today I saw that a new DMD version had been released. So I
> downloaded it (dmd-2.074.1.exe).
>
> Unfortunately, the installer does *not* detect VS2017, instead it
> asks me to install VS2013 for x64 support.

That PR was merged into the master branch, not the stable branch, so the
updates to the installer will be in 2.075.0. Presumably, they either thought
that it was too large a change for a release that only has bugfixes, or they
just merged it into master, because that's the default, and they didn't
think about it.

- Jonathan M Davis



More information about the Digitalmars-d mailing list