[Issue 11266] Ship new sc.ini with expanded support for more versions of Visual Studio/Windows SDK

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=11266



--- Comment #12 from Rainer Schuetze <r.sagitario at gmx.de> 2013-10-15 23:30:51 PDT ---
(In reply to comment #9)
> It'd look just like above. If neither LINKCMD64 nor LINKCMD64 is found dmd just
> uses "link". I believe this means it'll still work if someone just runs the
> usual vcvarsall.bat to get the MSVC toolset in the PATH (if they installed MSVC
> after dmd, for instance).  vcvarsall.bat prepends to the PATH so optlink
> shouldn't get in the way in this case.  vcvarsall.bat is already required for
> the current sc.ini so this should be functionally no different then what we
> have now.

If you have run vcvarsall.bat, VCINSTALLDIR is set and dmd uses VCINSTALLDIR to
create a non-working path to link.exe for VS2012+ instead of using just "link":

Can't run 'c:\Program Files (x86)\Microsoft Visual Studio
11.0\VC\bin\amd64\link
', check PATH

If you haven't run vcvarsall.bat, VCINSTALLDIR is not set, but also PATH
doesn't contain the VC bin directory, so it will probably pick up optlink when
running "link".

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------