[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 #7 from Rainer Schuetze <r.sagitario at gmx.de> 2013-10-15 00:50:04 PDT ---
(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.

> 
> Optlink is never valid in 64 so I moved the LINKCMD for it to 32 (do you see
> any problems with that)?

That should be no problem.

> Any tips for getting this working with Express?  If I remember correctly a
> person need a specific version of the platform SDK to get the necessary command
> line tools but I can't remember the details beyond that.

I haven't used the Express versions recently, but IIRC VS2012 Express
installation was very similar to the full version, while VS2010 Express never
had x64 support. You had to install the Windows 7 SDK to get the x64 tool
chain.

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