06-18-2017, 02:45 AM
Does anyone build 64-bit Cuberite using VS 2017? I can't seem to make it work, cmake is writing weird flags into the project files etc.
Random Chitchat 2017
|
06-18-2017, 02:45 AM
Does anyone build 64-bit Cuberite using VS 2017? I can't seem to make it work, cmake is writing weird flags into the project files etc.
06-18-2017, 02:48 AM
(This post was last modified: 06-18-2017, 02:54 AM by Seadragon91.)
Did you tried a clean clone? Had tred to build a project from 2015 in 2017 and didn't worked too. With a clean clone it worked.
06-18-2017, 03:12 AM
I'm working from a clean clone. It seems that CMake doesn't generate some of the flags for MSVC - the optimizations are turned on for Debug builds, C++ exceptions are turned off, runtime libraries not set (except for SQLiteCpp, which I assume sets them explicitly).
If you do a "cmake --version", what do you get? I had 3.7.1, it didn't recognize VS2017, so I installed the newest currently available, 3.8.2, now it recognizes the VS version but writes weird configuration.
Note that on another computer I'm using VS2017 for 32-bit builds without any problems at all. It's just 64-bit builds.
06-18-2017, 03:19 AM
I have cmake 3.8.0. Did you do cmake -G "Visual Studio 15 2017 Win64" in the directory?
06-18-2017, 03:44 AM
Pulled a clean clone, installed cmake 3.8.2 and checked that visual studio was updated. After fixing Leakfinder it compiles fine on my side.
06-18-2017, 04:04 AM
I'll try again, I guess.
06-18-2017, 04:59 AM
Weird, it seems to be working now.
06-18-2017, 05:27 AM
As for the LeakFinder issue, go check PR 3777: https://github.com/cuberite/cuberite/pull/3777
06-19-2017, 03:43 AM
Oh dear, it seems I've broken VS2013 on Cuberite's sources
Code: src\Bindings\ManualBindings_World.cpp(641): fatal error C1001: An internal error has occurred in the compiler. What do I do now? It's not like it's some super-template-heavy code, just another function pointer with a nullptr default for the DoWithXYZ() bindings... |
« Next Oldest | Next Newest »
|