Odd problems building in Visual Studio 2015?

[Derek]

I'm using Visual Studio Community 2015.

I pulled the source code from Github earlier yesterday. I was able to get it to build, but only after I changed a few things that were giving me errors that didn't seem like they should.

First of all, I had to fix a typo(?) in Core.vcxproj.filters on line 968 it had "</ClInclud" instead of "</ClInclude>". Odd, but easy enough.

Next pch wouldn't compile, with an error message saying to update to Visual Studio 15 Update 2 or later. I'm not sure what version it was at the time, but I went and downloaded update 3, however the error persisted. In pch.h the line #if _MSC_FULL_VER < 190023918 was bizarrely returning true even though VS claims that the value of _MSC_FULL_VER is 190024210. But I commented out this error message and the compile proceeded.

Next, Core failed to build because of an internal compiler error (what?!) on line 45 of Identity.cpp. I tried a few things to fix this, ultimately what worked was removing the constexpr declaration on line 33. At this point the build succeeded.


So I don't know if I've been doing something wrong, or what. Like I said, I was able to work around them, but it doesn't seem like these problems should have existed. Just really odd.

EDIT: Also, the debug build crashes when I try to run a game. The release build works though.

[Jack Frost]

Is this Visual Studio 15 (aka Visual Studio 2017) or Visual Studio 2015 (aka Visual Studio 14)?

The Filter issue seems legit tho, thanks for letting us know.

[Derek]

(03-26-2017, 10:40 PM)Jack Frost Wrote: Is this Visual Studio 15 (aka Visual Studio 2017) or Visual Studio 2015 (aka Visual Studio 14)?

The Filter issue seems legit tho, thanks for letting us know.

Visual Studio Community 2015 version 14.0.25431.01 Update 3

My bad, didn't realize the version numbers were different from the year numbers. I fixed the thread title as well.

Also, I found that the debug build crashes when I try to load a game. The release build works fine.

[Jack Frost]

Most of our Windows based developers still use VS 2015 Update 3 or moved to VS 2017; both should work just fine. We've had some fixes recently, so you might want to update your working copy.

You might want to try a full rebuild (after clean) too, although it seems a little strange that those asserts trigger...as if you had an older toolset/compiler being invoked instead of the most recent one.

[Derek]

Digging into the _MSC_FULL_VER problem some more, I was able to find that while compiling it's value is 190023026, despite what Intellisense was showing (190024210). I tried compiling it in Visual Studio Community 2017, and without retargeting I got the same error. However after retargeting the platform toolset to v141 the _MSC_FULL_VER was 191025017, and PCH compiled. Retargeting the toolset to v141 also fixed the internal compiler error, so the rest of the solution was able to compile.


So I still don't know if something is just configured wrong with my setup or what. I checked online to see if there is something that could be changing _MSC_FULL_VER other than the platform toolset, but found nothing. Everything works perfectly fine in VS2015 if I just change those two things (pch.h and Identity.cpp), but it doesn't seem right.

[Jack Frost]

IntelliSense uses a different compiler than...well, the compiler, so it might be different. No idea why its doing that tho. Might have something to do with how VS 2015 is installed, or perhaps with some Registry stuff related to the C++ compilers/toolset of that particular version.
I only remember it being a pain to set up on a CI server without actually installing VS (for disk space reasons), with similar odd results...