That one's working for me.It still looks a little funny though:
; default to 32-bit linker (can generate 64-bit code) that has a common path
; for VS2010, VS2012, and VS2013. This will be overridden below if the
; installer detects VS.
LINKCMD=%VCINSTALLDIR%\bin\link.exe
; -----------------------------------------------------------------------------
; This enclosed section is specially crafted to be activated by the Windows
; installer when it detects the actual paths to VC and SDK installations so
; modify this in the default sc.ini within the git repo with care
;
; End users: You can fill in the path to VC and Windows SDK and uncomment out
; the appropriate LINKCMD to manually enable support
; Windows installer replaces the following lines with the actual paths
VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\
WindowsSdkDir=C:\Program Files (x86)\Windows Kits\8.0\
Notice that it refers to LINKCMD=%VCINSTALLDIR%\... at the top, but VCINSTALLDIR is not set until down lower.
Then later in the file:
; Platform libraries (Windows SDK 8)
LIB=%LIB%;"%WindowsSdkDir%\Lib\win8\um\x64"
; Platform libraries (Windows SDK 7)
LIB=%LIB%;"%WindowsSdkDir%\Lib\x64"
The first one (Win8 SDK) is correct, but the second path (Win7 SDK) doesn't exist. The Win7 SDK is at "Microsoft SDKs\Windows\v7.0A" on my machine (installed by VS2010).
None of this seems to cause DMD to fail, but it may be confusing to have technically erroneous settings.