http://d.puremagic.com/issues/show_bug.cgi?id=11266
--- Comment #6 from Brad Anderson <e...@gnuk.net> 2013-10-15 00:02:48 PDT --- (In reply to comment #5) > I've suggested a slightly more elaborate version of sc.ini here: > http://forum.dlang.org/thread/20130903205311.00003c40@unknown?page=5#post-l10vtc:2476o:241:40digitalmars.com > > Just adding all possible library paths for the different SDKs should do the > trick to support different installations. Do you see any harm in(In reply to comment #5) > I've suggested a slightly more elaborate version of sc.ini here: > http://forum.dlang.org/thread/20130903205311.00003c40@unknown?page=5#post-l10vtc:2476o:241:40digitalmars.com > > Just adding all possible library paths for the different SDKs should do the > trick to support different installations. So you are saying something like (modified slightly)?: --- ; environment for both 32/64 bit [Environment] LIB="%@P%\..\lib" DFLAGS="-I%@P%\..\..\src\phobos" "-I%@P%\..\..\src\druntime\import" [Environment32] LINKCMD=%@P%\link.exe [Environment64] ; VS2010 ;VS2010LINKCMD=%VCINSTALLDIR%\bin\amd64\link.exe ; VS2012 ;VS2012LINKCMD=%VCINSTALLDIR%\bin\x86_amd64\link.exe ; needed with /DEBUG to find mspdb*.dll ;VS2012PATH=%PATH%;%VCINSTALLDIR%\bin\x86_amd64;%VCINSTALLDIR%\..\Common7\IDE ; VS2013 ;VS2013LINKCMD=%VCINSTALLDIR%\bin\x86_amd64\link.exe ; needed with /DEBUG to find mspdb*.dll ;VS2013PATH=%PATH%;%VCINSTALLDIR%\bin\x86_amd64;%VCINSTALLDIR%\..\Common7\IDE ; needed to avoid COMDAT folding (bugzilla 10664) DFLAGS=%DFLAGS% -L/OPT:NOICF LIB="%@P%\..\lib64" ;;;; search path for C Runtime libraries ; the following lib path works with VS2008, VS2010 and VS2012 LIB=%LIB%;"%VCINSTALLDIR%\lib\amd64" ;;;; search path for Platform libraries ; the following lib path works with Windows SDK 6.x and 7.x LIB=%LIB%;%WindowsSdkDir%\Lib\x64 ; the following lib path works with Windows SDK 8.0 LIB=%LIB%;%WindowsSdkDir%\Lib\win8\um\x64 --- 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. Optlink is never valid in 64 so I moved the LINKCMD for it to 32 (do you see any problems with that)? 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. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------