On 08.01.2018 08:56, Andre Pany wrote:
On Wednesday, 3 January 2018 at 17:43:36 UTC, Martin Nowak wrote:
Glad to announce D 2.078.0.
This release comes with runtime detection of Visual Studio
installation paths, an integral promotion transition for unary
operations on byte and short sized integers, more -betterC features,
and a couple of language and library tweaks.
Thanks to everyone involved in this 👏
https://dlang.org/contributors.html.
http://downloads.dlang.org/releases/2.x/2.078.0/
http://dlang.org/changelog/2.078.0.html
- -Martin
It seems vs-auto-detection does not work with the Visual Studio 2017
Community version:
I executed "vcvars64.bat". After that environment variable PATH contains
following
entries:
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\HostX64\x64;
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\Common7\IDE\VC\VCPackages;
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TestWindow;
C:\Program Files (x86)\Microsoft Visual
...
dmd app.d -m64
Error: can't run 'C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\VC\\bin\link.exe', check PATH
I checked the location and link.exe is available in the very first
element of PATH environment variable:
C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\Hostx64\x64
Could you check?
Kind regards
André
Unfortunately the corresponding installer PRs didn't make it into the
release, so you still have to remove most options of section
Environment64 from sc.ini yourself. This should be enough
[Environment64]
LIB=%@P%\..\lib64
DFLAGS=%DFLAGS% -L/OPT:NOICF
When using the 7z dmd file, the most harmful setting is LINKCMD, that
doesn't work for VS2017.
