[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 #9 from Brad Anderson <eco at gnuk.net> 2013-10-15 09:25:54 PDT ---
(In reply to comment #7)
> (In reply to comment #6)
> > The VS{2010,2012,2013}{LINKCMD,PATH} business is because the way the installer
> > does things is by simple find and replace so that'd make those easy to enable.
> > If you see no harm in having the LIB for every version active that'd certainly
> > make things easier.
> 
> If LINKCMD is patched by the installer, I'm fine with it. But how does the
> sc.ini in the zip file look like? I don't have a solution to making it work
> with both VS2010 and VS2012 yet.
> 

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.

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