There is no interactive debugger for CMake, however there are also the flags -Wdev, –debug-output and –trace which might help. Also remember to check the log files CMakeFiles\CMakeOutput.log and CMakeFiles\CMakeError.log which mainly collect outputs of processes called by CMake (for example while checking for presence of a type or header). Since version 3.7, CMake now … Read more
There are ways to add .c as a valid file extension for the CXX compiler. Even this being very advanced CMake stuff, you may need – if you are bound to support older versions of CMake – a “make rules overwrite script” anyway. So I’ve successfully tested the following: CryptoppMakeRulesOverwrite.cmake list(APPEND CMAKE_CXX_SOURCE_FILE_EXTENSIONS c) CMakeLists.txt cmake_minimum_required(VERSION … Read more
CMake developers suggest to use given pattern for change default value of CMAKE_INSTALL_PREFIX inside CMakeLists.txt: # Use this snippet *after* PROJECT(xxx): IF(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT) SET(CMAKE_INSTALL_PREFIX <path> CACHE PATH <comment> FORCE) ENDIF(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT) Using that approach # Use this snippet *before* PROJECT(xxx): SET(CMAKE_INSTALL_PREFIX <path> CACHE PATH <comment>) is not recommended: .. solution depends on the implementation details of the … Read more
I’ve done this in my projects with target_link_libraries(): target_link_libraries( myProgram ${CMAKE_CURRENT_SOURCE_DIR}/libs/obj.o ) Any full path given to target_link_libraries() is assumed a file to be forwarded to the linker. For CMake version >= 3.9 there are the add_library(… OBJECT IMPORTED ..) targets you can use. See Cmake: Use imported object And – see also the answer … Read more
While I’m not at all pleased with this solution, posting since I stumbled on this page and didn’t see it mentioned. You can add a custom target that references a missing file, eg: if(EXISTS ${CMAKE_CURRENT_BINARY_DIR}/__header.h) message(FATAL_ERROR “File \”${CMAKE_CURRENT_BINARY_DIR}/__header.h\” found, \ this should never be created, remove!”) endif() add_custom_target( my_custom_target_that_always_runs ALL DEPENDS ${CMAKE_CURRENT_BINARY_DIR}/__header.h ) add_custom_command( OUTPUT … Read more
Yes, you can append compiler and linker options. But there are two things you have to differentiate in CMake: the first call to generate the build environment and all consecutive calls for regenerating that build environment after changes to your CMakeLists.txt files or dependencies. Here are some of the possibilities (excluding the more complex toolchain … Read more
You need to set the flags after the project command in your CMakeLists.txt. Also, if you’re calling include(${QT_USE_FILE}) or add_definitions(${QT_DEFINITIONS}), you should include these set commands after the Qt ones since these would append further flags. If that is the case, you maybe just want to append your flags to the Qt ones, so change … Read more
It sounds like you want an out of source build. There are a couple of ways you can create an out of source build. Do what you were doing, run cd /path/to/my/build/folder cmake /path/to/my/source/folder which will cause cmake to generate a build tree in /path/to/my/build/folder for the source tree in /path/to/my/source/folder. Once you’ve created it, … Read more
Here is what worked for me – create a file called PreLoad.cmake in your project dir containing this: set (CMAKE_GENERATOR “Unix Makefiles” CACHE INTERNAL “” FORCE)
I think you’re mixing up two different paradigms here. As you noted, the highly flexible ExternalProject module runs its commands at build time, so you can’t make direct use of Project A’s import file since it’s only created once Project A has been installed. If you want to include Project A’s import file, you’ll have … Read more