unable to build with Visual Studio Community 2015 on Win7 64

[nig]

As I tried to build a new Version of Megaglest from Github these days I have to see that my building programs seem to be outdated (with a look at the compiling Doc, still hard to find at https://docs.megaglest.org/MG/Windows_Compiling)

So I scratched all my old Visual and C++ installs manually to avoid confusions amd updated my git to 2.7.1.windows.1 (32Bit, because the old one was 32 Bit too).

After that I installed Visual Studio Community 2015. There was an Errormessage during that:

well, ....

after that I followed the compiling wiki and the build script couldnt find "msbuild". Googling around  I found: seems to be a bug in Frameworks or configuration, no known solutions, just workarounds. So I set a path in windowsenvironmet to the newest msbuild.exe I found. (lots of msbuild.exe are on the machine).

now all building scripts stop like this:

(click to show/hide)

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppBuild.targets(366,5): warning MSB8003: Could not find WindowsSDKDir variable from the registry.  TargetFrameworkVersion or Platform
Toolset may be set to an invalid version number. [E:\silk\git\megaglest-source\mk\windoze\vc2015\g2xml.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppBuild.targets(366,5): warning MSB8003: Could not find WindowsSDKDir variable from the registry.  TargetFrameworkVersion or Platform
Toolset may be set to an invalid version number. [E:\silk\git\megaglest-source\mk\windoze\vc2015\xml2g.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(356,5): error MSB6006: "CL.exe" wurde mit dem Code 5 beendet. [E:\silk\git\megaglest-source\mk\windoze\vc2015\g2xml.
vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(356,5): error MSB6006: "CL.exe" wurde mit dem Code 5 beendet. [E:\silk\git\megaglest-source\mk\windoze\vc2015\xml2g.
vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppBuild.targets(366,5): warning MSB8003: Could not find WindowsSDKDir variable from the registry.  TargetFrameworkVersion or Platform
Toolset may be set to an invalid version number. [E:\silk\git\megaglest-source\mk\windoze\vc2015\shared_lib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(356,5): error MSB6006: "CL.exe" wurde mit dem Code 5 beendet. [E:\silk\git\megaglest-source\mk\windoze\vc2015\shared
_lib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppBuild.targets(366,5): warning MSB8003: Could not find WindowsSDKDir variable from the registry.  TargetFrameworkVersion or Platform
Toolset may be set to an invalid version number. [E:\silk\git\megaglest-source\mk\windoze\vc2015\libstreflop.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\BuildCustomizations\masm.targets(50,5): error MSB4174: Die Aufgabenfactory "XamlTaskFactory" wurde nicht in der Microsoft.Build.Tasks.v4.0, Vers
ion=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a-Assembly gefunden. [E:\silk\git\megaglest-source\mk\windoze\vc2015\libstreflop.vcxproj]

please help

nig

[nig]

finally found it:

By default on windows the c++ compilers are not installed by installing visualstudio community 2015.

After installing visualstudio community 2015 you can install the c++ SDK by trying to open an own softwareobject. Do this:

You need to launch Visual studio, then do: file > new > project, in the window than opened, select "Model > Visual C++" and in the middle of the window you should see a button "install microsoft C++" or something like that, click on it and it will launch the install process for the C++ & Microsoft SDK.

Be ready to watch your machine again installing for half an hour, eating another GB. Of course i get the incompatibilitywarning again:


But who cares? Ican build my own megaglrst64.dev again, enjoing being blocked from lobby!

There might be some installation-properties you can set at first installing of "visualstudio community 2015" to avoid this fumbling around. Maybe someone checks that out and put it to the compiling WIKI.
Dont expect Windowsusers to do researches like this. There is a reason, why they are not at Linux.

greets
nig

[filux]

Thx for finding this  this information will help for other testers 

... and mICROSOFT did a "great job" again  .

This is quite good source of informations about this situation (read also comments on the bottom):
https://blogs.msdn.microsoft.com/vcblog/2015/07/24/setup-changes-in-visual-studio-2015-affecting-c-developers/

... and there is some helpful video too: