DMD v2.066.0-rc1

Tue Aug 5 22:20:24 PDT 2014

On 8/3/2014 8:51 PM, Manu via Digitalmars-d-announce wrote:
> This windiows installer went wrong on me.
> First, it tried to uninstall, it offered to uninstall from 'C:\D'. My DMD
> install is 'C:\dev\D'... The path was presented in a greyed out textbox that I
> couldn't type in to correct it, and no button to select the true install location.
> The uninstall step failed.
>
> Then when reinstalling I was given the option where to install, I chose
> 'C:\dev\D' and it installed over the top of my existing install, and wiped my
> sc.ini file. So I need to configure the DirectX SDK paths again.

Please file these on bugzilla as 2 bug reports.

https://issues.dlang.org/enter_bug.cgi

> Side note:
> I still think the installer really should detect the DXSDK; it's a Microsoft
> library, and virtually any multimedia software developed with VS2010 or prior
> will depend on it (It's merged into the WinSDK since DX2012).
>
> The DXSDK install paths are:
> Include: C:\Program Files (x86)\Microsoft DirectX SDK (June 2010)\Include
> Lib: C:\Program Files (x86)\Microsoft DirectX SDK (June 2010)\Lib\x64
>
> The "(June 2010)" part is a safe assumption, it's the last released one, and it
> will remain so since it's now bundled with the WinSDK for more recent visual
> studio releases. It's the only one available on the Microsoft website.
> As I see it, if we profess to support VS2010 and prior, then we should detect
> the DXSDK paths in the installer, otherwise software that builds fine in VS2012+
> won't work with VS2010 without user intervention, and that will almost certainly
> lead to posts on this forum.

One of the reasons I delayed so long in supporting VS is because Microsoft 
changes things around with every release, making trying to support whatever 
version the customer has is a constant configuration/testing nightmare, 
consuming a great deal of time and effort with little payback.

With dmc, this is not a problem.

As an aside, one thing I find difficult to understand is why experienced C++ 
developers find it so hard to set an environment variable (or one in the sc.ini) 
pointing to where the right .h files are and the right .lib files are.

Heck, I just cribbed them from where Microsoft set them in its own command 
prompt shortcut "Visual Studio x64 Win64 Command Prompt (2010)". For example, 
clicking on the shortcut and typing "set" gives:

--------------------------------------

Setting environment for using Microsoft Visual Studio 2010 x64 tools.

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC>set
ALLUSERSPROFILE=C:\ProgramData
CommandPromptType=Native
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
ComSpec=C:\Windows\system32\cmd.exe
FP_NO_HOST_CHECK=NO
Framework35Version=v3.5
FrameworkDir=C:\Windows\Microsoft.NET\Framework64
FrameworkDIR64=C:\Windows\Microsoft.NET\Framework64
FrameworkVersion=v4.0.30319
FrameworkVersion64=v4.0.30319
FSHARPINSTALLDIR=C:\Program Files (x86)\Microsoft F#\v4.0\
HOMEDRIVE=C:
HOMEPATH=\Users\walter
INCLUDE=C:\Program Files (x86)\Microsoft Visual Studio 
10.0\VC\INCLUDE;C:\Program Files (x86)\Micros
oft Visual Studio 10.0\VC\ATLMFC\INCLUDE;C:\Program Files (x86)\Microsoft 
SDKs\Windows\v7.0A\include
;
LIB=C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\LIB\amd64;C:\Program 
Files (x86)\Microsof
t Visual Studio 10.0\VC\ATLMFC\LIB\amd64;C:\Program Files (x86)\Microsoft 
SDKs\Windows\v7.0A\lib\x64
;
LIBPATH=C:\Windows\Microsoft.NET\Framework64\v4.0.30319;C:\Windows\Microsoft.NET\Framework64\v3.5;C:
\Program Files (x86)\Microsoft Visual Studio 10.0\VC\LIB\amd64;C:\Program Files 
(x86)\Microsoft Visu
al Studio 10.0\VC\ATLMFC\LIB\amd64;
MEDIAMALL=C:\Program Files (x86)\MediaMall\
MOZ_PLUGIN_PATH=C:\Program Files (x86)\Foxit Software\Foxit Reader\plugins\
NUMBER_OF_PROCESSORS=6
OS=Windows_NT
Path=C:\Program Files (x86)\Microsoft Visual Studio 
10.0\VC\BIN\amd64;C:\Windows\Microsoft.NET\Frame
work64\v4.0.30319;C:\Windows\Microsoft.NET\Framework64\v3.5;C:\Program Files 
(x86)\Microsoft Visual
Studio 10.0\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio 
10.0\Common7\IDE;C:\Program
  Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools;C:\Program Files 
(x86)\HTML Help Workshop;C:
\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 
Tools\x64;C:\Program Files (x86)\Mic
rosoft SDKs\Windows\v7.0A\bin\x64;C:\Program Files (x86)\Microsoft 
SDKs\Windows\v7.0A\bin;C:\Program
  Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common 
Files\Microsoft Shar
ed\Windows 
Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsP
owerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL 
Server\100\Tools\Binn\;C:\Program Files\Microso
ft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL 
Server\100\DTS\Binn\;C:\Program Files (
x86)\Windows Live\Shared
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
Platform=X64
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=AMD64 Family 21 Model 1 Stepping 2, AuthenticAMD
PROCESSOR_LEVEL=21
PROCESSOR_REVISION=0102
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC=C:\Users\Public
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\Windows
VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\
VS100COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\
VSINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 10.0\
windir=C:\Windows
WindowsSdkDir=C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\
windows_tracing_flags=3
windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC>
----------------------------------

There's VCINSTALLDIR and WindowsSdkDir and INCLUDE and LIBPATH