See also "C:/Users/andrew/src/mesos/build/CMakeFiles/CMakeOutput.log". Configuring incomplete, errors occurred! The CXX compiler identification is unknownĬMake Error at CMakeLists.txt:25 (project): The C compiler identification is unknown ![]() G "Visual StuWin64" -T "host=圆4" -DENABLE_LIBEVENT=1 -DHAS_AUTHENTICATION=0 PS C:\Users\andrew\src\mesos\build> cmake. CMake 3.7.2 on CLI PS C:\Users\andrew\src\mesos\build> cmake -versionĬMake suite maintained and supported by Kitware (/cmake). It seems that Visual Studio originally invokes CMake "specially" shomehow as it finds the tools for the top-level project,īut does not retain this environment when $ is invoked from within the build. (used to include third-party CMake driven projects) re-invokes CMake, at which point it fails to find the compilers. This becomes problematic when using the Visual Studio CMake tools because the ExternalProject_Add macro Using CMake 3.8.1 (current CMake release), the tools can be found no problem. This is reproducing for me using Visual Studio 2017 with individual components selected. ![]() The 3.7.2 version of CMake bundled with Visual Studio 2017 (latest update) cannot on its own find the Visual Studio 2017 build tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |