On Sunday, 4 June 2017 at 23:45:34 UTC, Jonathan M Davis wrote:
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:
> [...]
Today I saw that a new DMD version had been released. So I
downloaded it
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
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
On Wednesday, 24 May 2017 at 03:21:56 UTC, Vladimir Panteleev
wrote:
On Tuesday, 23 May 2017 at 23:11:30 UTC, Jolly James wrote:
Come one, let's be ones: If DMD has no x64 linker, VS
integration is not a bit optional.
Unlike some other operating systems, 64-bit Windows versions
can run
On Tuesday, 23 May 2017 at 23:11:30 UTC, Jolly James wrote:
Come one, let's be ones: If DMD has no x64 linker, VS
integration is not a bit optional.
Unlike some other operating systems, 64-bit Windows versions can
run 32-bit software just fine. If you require targeting Win64 (or
the
On Monday, 22 May 2017 at 23:58:37 UTC, Vladimir Panteleev wrote:
Additionally, Visual Studio integration is an optional feature
of the Windows version, and of course VS2017 is just one
supported version of VS.
Come one, let's be ones: If DMD has no x64 linker, VS integration
is not a bit
On Monday, 22 May 2017 at 21:08:02 UTC, Jolly James wrote:
On Monday, 22 May 2017 at 07:28:23 UTC, Vladimir Panteleev
wrote:
On Sunday, 21 May 2017 at 22:47:44 UTC, Jolly James wrote:
On Monday, 1 May 2017 at 18:30:53 UTC, Rainer Schuetze wrote:
Please note that the next dmd installer will
On Monday, 22 May 2017 at 21:08:02 UTC, Jolly James wrote:
I mean, if for any circumstance, e.g. like the VS2017 thing
(which did not suddenly appear from one day to another anyway),
the whole software cannot be used without larger fiddling (in
this case: setting up NSIS + plugins), it seems
On Monday, 22 May 2017 at 07:28:23 UTC, Vladimir Panteleev wrote:
On Sunday, 21 May 2017 at 22:47:44 UTC, Jolly James wrote:
On Monday, 1 May 2017 at 18:30:53 UTC, Rainer Schuetze wrote:
Please note that the next dmd installer will also detect
VS2017 and setup directories correctly in sc.ini:
On Sunday, 21 May 2017 at 22:47:44 UTC, Jolly James wrote:
On Monday, 1 May 2017 at 18:30:53 UTC, Rainer Schuetze wrote:
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
I really like this
On Sunday, 21 May 2017 at 22:47:44 UTC, Jolly James wrote:
On Monday, 1 May 2017 at 18:30:53 UTC, Rainer Schuetze wrote:
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
I really like this
On Monday, 1 May 2017 at 18:30:53 UTC, Rainer Schuetze wrote:
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
I really like this philosophy:
"It does not work, a fix is available, but it
On Monday, 1 May 2017 at 18:30:53 UTC, Rainer Schuetze wrote:
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
On 01.05.2017 10:03, Igor wrote:
On Monday, 1 May 2017 at 01:54:30 UTC, evilrat wrote:
On Sunday, 30 April 2017 at 16:05:10 UTC, Igor wrote:
I should also mention that compiling using DUB works. It only doesn't
work from VS.
Check your VisualD settings and make sure it has DMD path set
On Monday, 1 May 2017 at 01:54:30 UTC, evilrat wrote:
On Sunday, 30 April 2017 at 16:05:10 UTC, Igor wrote:
I should also mention that compiling using DUB works. It only
doesn't work from VS.
Check your VisualD settings and make sure it has DMD path set
up.
See under
On Sunday, 30 April 2017 at 16:05:10 UTC, Igor wrote:
I should also mention that compiling using DUB works. It only
doesn't work from VS.
Check your VisualD settings and make sure it has DMD path set up.
See under Tools>Options>Projects and solutions>Visual D Settings
On Sunday, 30 April 2017 at 16:52:52 UTC, Igor wrote:
On Sunday, 30 April 2017 at 16:31:13 UTC, John Chapman wrote:
Here are mine, if it helps:
I tried but still the same problem. I also tried reinstalling
VisualD after changing sc.ini in DMD but that didn't help
either.
You are going
On Sunday, 30 April 2017 at 16:31:13 UTC, John Chapman wrote:
Here are mine, if it helps:
I tried but still the same problem. I also tried reinstalling
VisualD after changing sc.ini in DMD but that didn't help either.
On Sunday, 30 April 2017 at 16:05:10 UTC, Igor wrote:
On Sunday, 30 April 2017 at 15:53:07 UTC, Mike Parker wrote:
On Sunday, 30 April 2017 at 14:56:44 UTC, Igor wrote:
I tried updating sc.ini to new paths but I still get this
error. Can someone offer some advice?
Which paths did you set?
On Sunday, 30 April 2017 at 15:53:07 UTC, Mike Parker wrote:
On Sunday, 30 April 2017 at 14:56:44 UTC, Igor wrote:
I tried updating sc.ini to new paths but I still get this
error. Can someone offer some advice?
Which paths did you set?
These are the ones I changed:
On Sunday, 30 April 2017 at 14:56:44 UTC, Igor wrote:
I tried updating sc.ini to new paths but I still get this
error. Can someone offer some advice?
Which paths did you set?
On Saturday, 22 April 2017 at 02:46:30 UTC, Mike Parker wrote:
On Saturday, 22 April 2017 at 02:39:41 UTC, evilrat wrote:
Also VS 2017 is much more modular now, so its now lighter than
ever before.
but of course for C++ (and D) you still need Windows SDK.
The SDK stuff is installed with
On Saturday, 22 April 2017 at 02:39:41 UTC, evilrat wrote:
Also VS 2017 is much more modular now, so its now lighter than
ever before.
but of course for C++ (and D) you still need Windows SDK.
The SDK stuff is installed with VS.
IIRC D also can be used without VS or WinSDK at all, just
On Saturday, 22 April 2017 at 02:22:56 UTC, NotSpooky wrote:
I don't have Windows so I don't know if this has changed, but
last time I tried to install dmd there it asked to install VS
2013, I know some people that didn't want to install DMD
because VS is huge, now that the build tools are
On Saturday, 22 April 2017 at 02:22:56 UTC, NotSpooky wrote:
On Saturday, 22 April 2017 at 02:13:09 UTC, Mike Parker wrote:
There's no issue with compatibility. DMD is perfectly
compatible with all recent versions of VS, including 2017. The
issue is that 2017 has changed its directory tree
On Saturday, 22 April 2017 at 02:13:09 UTC, Mike Parker wrote:
There's no issue with compatibility. DMD is perfectly
compatible with all recent versions of VS, including 2017. The
issue is that 2017 has changed its directory tree and the DMD
*installer* can't pick it up automatically. Now
On Friday, 21 April 2017 at 14:37:40 UTC, NotSpooky wrote:
I'd be very nice if instead of offering to install VS, it
offered the build tools. Also mentioning which installations
are compatible so that the user can select the one he/she
prefers.
A lot of people are confused with this.
On Thursday, 20 April 2017 at 04:58:55 UTC, Mike Parker wrote:
You can install the MS Build Tools 2015. DMD will work with
that.
I'd be very nice if instead of offering to install VS, it offered
the build tools. Also mentioning which installations are
compatible so that the user can select
On Thursday, 20 April 2017 at 17:10:05 UTC, Meta wrote:
On Thursday, 20 April 2017 at 17:06:15 UTC, Mike Parker wrote:
On Thursday, 20 April 2017 at 14:44:54 UTC, Meta wrote:
On Thursday, 20 April 2017 at 14:29:28 UTC, Jolly James wrote:
What has the DMD compiler to do with a VS plugin that I
On Thursday, 20 April 2017 at 00:13:29 UTC, Meta wrote:
On Wednesday, 19 April 2017 at 20:47:51 UTC, Jolly James wrote:
I cannot even fix it myself because DMD is looking for
"bin\link.exe". But with VS2017 the path would actually be
something like "\bin\HostX64\x64".
Please ignore Mike's
On Thursday, 20 April 2017 at 17:06:15 UTC, Mike Parker wrote:
On Thursday, 20 April 2017 at 14:44:54 UTC, Meta wrote:
On Thursday, 20 April 2017 at 14:29:28 UTC, Jolly James wrote:
What has the DMD compiler to do with a VS plugin that I am
not using?
You said in your original post "DMD
On Thursday, 20 April 2017 at 14:44:54 UTC, Meta wrote:
On Thursday, 20 April 2017 at 14:29:28 UTC, Jolly James wrote:
What has the DMD compiler to do with a VS plugin that I am not
using?
You said in your original post "DMD installer only offers to
install VS2013". This isn't the DMD
On Thursday, 20 April 2017 at 14:29:28 UTC, Jolly James wrote:
What has the DMD compiler to do with a VS plugin that I am not
using?
You said in your original post "DMD installer only offers to
install VS2013". This isn't the DMD installer but the Visual D
installer that installs the plugin
On Thursday, 20 April 2017 at 05:02:37 UTC, Mike Parker wrote:
On Thursday, 20 April 2017 at 04:58:55 UTC, Mike Parker wrote:
[...]
I should add that Mike's suggestion to edit sc.ini should do
the trick, but I find it convenient to have both toolsets
installed.
I'll give it a try, thanks
On Thursday, 20 April 2017 at 00:13:29 UTC, Meta wrote:
On Wednesday, 19 April 2017 at 20:47:51 UTC, Jolly James wrote:
[...]
Please ignore Mike's answer. Visual D is maintained by Rainers
Schuetze and is hosted here[1] on github. From the readme:
For more information on installation, a
On Thursday, 20 April 2017 at 04:58:55 UTC, Mike Parker wrote:
You can install the MS Build Tools 2015. DMD will work with
that. You have two options to do so -- download the installer
at the link below or run the VS 2017 installer and select it in
the "Individual Components" tab. I'm on my
On Wednesday, 19 April 2017 at 20:47:51 UTC, Jolly James wrote:
I cannot even fix it myself because DMD is looking for
"bin\link.exe". But with VS2017 the path would actually be
something like "\bin\HostX64\x64".
You can install the MS Build Tools 2015. DMD will work with that.
You have two
On Wednesday, 19 April 2017 at 20:47:51 UTC, Jolly James wrote:
I cannot even fix it myself because DMD is looking for
"bin\link.exe". But with VS2017 the path would actually be
something like "\bin\HostX64\x64".
Please ignore Mike's answer. Visual D is maintained by Rainers
Schuetze and is
On Wednesday, 19 April 2017 at 20:47:51 UTC, Jolly James wrote:
I cannot even fix it myself because DMD is looking for
"bin\link.exe". But with VS2017 the path would actually be
something like "\bin\HostX64\x64".
Edit your sc.ini in the dmd\windows\bin dir or use junctions to
map
I cannot even fix it myself because DMD is looking for
"bin\link.exe". But with VS2017 the path would actually be
something like "\bin\HostX64\x64".
DMD does not support VS2017. Therefore I cannot link x64
applications. DMD installer only offers to install VS2013 (what I
am absolutely not going to do, as that would be a real shame with
the disk space it consumes).
Any plans for supporting VS2017?
41 matches
Mail list logo
