![]() This method is therefore useful if many support libraries are installed into the same location. CMake will check these directories for any package it requires. What worked: Deleting the build folder entirely. CMake was unable to find a build program corresponding to 'Ninja'. others Ninja ought to fit perfectly into other meta-build software. If any support libraries are installed in non-default locations, CMake can be instructed where to find them by one of the following methods. First, the option CMAKE_PREFIX_PATH can be set to a colon-separated list of base directories where the libraries are installed, for example -DCMAKE_PREFIX_PATH=/path/where/my/sw/is/installed. Newer versions of CMake support generating Ninja files on Windows and Mac OS X too. For example, using CMAKE_CXX_FLAGS="-O2 -mtune=native" sets options for better optimisation. ![]() Further the variable CMAKE_CXX_FLAGS can be used to set compiler flags for optimisation or debugging. ![]() This can be overwritten by setting the environment variables CC, CXX and F77, before the call to cmake, to set the preferred compiler. The C, C++ and Fortran compilers are chosen by CMake. Now we move on the question of how to tell CMake to generate the right compilation lines.Additional flags to pass to the C++ compilerĪdditional flags to pass to the C compilerĪdditional flags to pass to the Fortran compiler Reminder on the compilation line with g++ For example, in our case, within quantize/share/CMakeLists.txt, that variable holds quantize/build/share.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |