You can use the list function to manipulate the list, for example: list(REMOVE_ITEM <list> <value> [<value> …]) In your case, maybe something like this will work: list(REMOVE_ITEM lib_srcs “IlmImf/b44ExpLogTable.cpp”)
What is CMake for? According to Wikipedia: CMake is […] software for managing the build process of software using a compiler-independent method. It is designed to support directory hierarchies and applications that depend on multiple libraries. It is used in conjunction with native build environments such as make, Apple’s Xcode, and Microsoft Visual Studio. With … Read more
CMake favours passing the full path to link libraries, so assuming libbingitup.a is in ${CMAKE_SOURCE_DIR}, doing the following should succeed: add_executable(main main.cpp) target_link_libraries(main ${CMAKE_SOURCE_DIR}/libbingitup.a)
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
These keywords are used to tell when the list of include directories you’re passing to the target are needed. By when, it means if those include directories are needed: To compile that target itself. To compile other targets that depend on that target (like using its public headers). In both of the above situations. When … Read more
Delete the CMakeCache.txt file and try this: cmake -G %1 -DBUILD_SHARED_LIBS=ON -DBUILD_STATIC_LIBS=ON -DBUILD_TESTS=ON .. You have to enter all your command-line definitions before including the path.
You can use the ctest –output-on-failure option, or set the environment variable CTEST_OUTPUT_ON_FAILURE, which will show you any output from the test program whenever the test fails. One way to do this when using Makefiles and the command line would be as follows: env CTEST_OUTPUT_ON_FAILURE=1 make check This Stack Overflow question and answer shows how to … Read more
In modern CMake, the following works well: if(MSVC) target_compile_options(${TARGET_NAME} PRIVATE /W4 /WX) else() target_compile_options(${TARGET_NAME} PRIVATE -Wall -Wextra -Wpedantic -Werror) endif() My colleague suggested an alternative version: target_compile_options(${TARGET_NAME} PRIVATE $<$<CXX_COMPILER_ID:MSVC>:/W4 /WX> $<$<NOT:$<CXX_COMPILER_ID:MSVC>>:-Wall -Wextra -Wpedantic -Werror> ) Replace ${TARGET_NAME} with the actual target name. -Werror is optional, it turns all warnings into errors. Or use add_compile_options(…) if … Read more
If you are creating a shared library and your source cpp files #include the headers of another library (Say, QtNetwork for example), but your header files don’t include QtNetwork headers, then QtNetwork is a PRIVATE dependency. If your source files and your headers include the headers of another library, then it is a PUBLIC dependency. … 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