Ive had VS2015 community for a while and its been working just fine for stuff other than UE, so i decided to upgrade to 4.10 and get rid of VS2013 since 4.10 fully supports 2015 now,
but there seems to be some issue with the default include dirs. As a side note, it happens even when creating new/empty UE C++ projects.
PCH.TestProject.h.cpp
<UE 4.10 Path>\Engine\Source\Runtime\Launch\Resources\Windows\PCLaunch.rc(10) : fatal error RC1015: cannot open include file 'windows.h'.
<UE 4.10 Path>\Engine\Source\Runtime\Core\Resources\Windows\ModuleVersionResource.rc.inl(3) : fatal error RC1015: cannot open include file 'windows.h'.
<VS2015 Path>\VC\INCLUDE\crtdefs.h(10): fatal error C1083: Cannot open include file: 'corecrt.h': No such file or directory
I went and checked the dir to make sure that i had the win 10 kit and it seems i have more than one version or something
so i replaced the project settings paths with the correct paths “Windows Kits\10\include\10.0.10150.0…” and im still getting the same stuff.
I really doubt that the fact that i have the community version causes this error,
this is the first time im having default include issues with UE so im quite clueless, is there anyone else having the same issue?
EDIT#1: After some searching this seems to fix the issue: Build errors. windows.h etc. [SOLVED] - C++ Gameplay Programming - Unreal Engine Forums
EDIT#2: Seems to be working fine now and changes to the code are applied.
Though, compiling from inside the editor gives me an error “<VS2015 Path>\4.0\VC\INCLUDE\cstdio(13)” cant find <stdio.h> while it compiles from VS just fine. Weird.
EDIT#3: After 3 hours of messing with the project files, i believe that for some reason UnrealBuildTool can’t find my Win SDK directory and it wont use the Include directories set under “VC++ Directories” either.
Its not just happening with the stdio file, UnrealBuildTool is having the same errors as VS before i set the include directories under project settings. Is there any place to set the include directories for the BuildTool?
Starting to think that im gonna have to do a clean boot, with just vs2015 installed and one windows kit. Or ill just go back to good 'ol 4.9…
Ill be updating this post with the solutions to my issues in case someone else is having the same.