Closed fcbertoldi closed 6 years ago
Hmm. I can't recall having tried with VS2017 yet. Are you using Community Edition?
This week is a bit of a mess for me, but I can try to take a look at this over the weekend. 😬
That's fine, I just wanted to report the problem, no need to hurry. 🙂
The problem occurred in both VS2013 and VS2017 Professional Edition.
In my home PC with VS2017 Community Edition I applied the fix without first reproducing the problem, and it worked.
Hm, I wasn't able to reproduce this locally. I did some research online -- looks like this is actually a CMake bug. If it's not too much trouble, would you mind updating your cmake installation and trying again?
For what it's worth, ${PROJECT_CONFIGS}
is only needed if you want CMakeLists.txt
and Readme.md
and such to show in the Solution Explorer. If you don't need to modify those much, your workaround is probably fine. 🙂
Closing for now, per my previous comment, and there has not been an update in a while. Feel free to reopen if this comes up again. 🙂
When building the project with Visual Studio 2017 I had the following error (translated, original message was in portuguese):
Removing
${PROJECT_CONFIGS}
from the list of sources inadd_executable
solves the problem.PC settings: Windows 10 version 1803 CMake version: 3.11.0. Visual Studio 2017 version 15.7.2