Question 1

Eyescale/CMake vs CMake's built-in modules: which is better?

Accepted Answer

Eyescale/CMake provides pre-built functions for common tasks like library creation and testing, saving time on boilerplate, but it adds an external dependency. CMake's built-in modules offer more control and are lighter, but require more manual setup for advanced features.

Question 2

How to add code coverage reporting with Eyescale/CMake?

Accepted Answer

Enable the COMMON_ENABLE_COVERAGE option in your CMake configuration, and a 'coverage' target will be automatically added to generate HTML reports during debug builds, as detailed in the CommonCoverage module.

Question 3

Does Eyescale/CMake work on Windows?

Accepted Answer

Core functions like common_library() likely work on Windows, but features such as InstallDependencies are limited to Linux and macOS. You'll need to manage dependencies manually or use alternative methods on Windows.

Question 4

How to manage dependencies with common_find_package?

Accepted Answer

Use common_find_package() in your CMakeLists.txt to locate libraries, and call common_find_package_post() at the end to generate defines.h and options.cmake for feature checking, simplifying dependency handling across projects.

Question 5

What default compiler flags does CommonCompiler set?

Accepted Answer

CommonCompiler sets default flags for C++14 and enables useful warnings (e.g., for GCC and Clang), automatically applied to targets created with common_library() and common_application() to ensure consistent and secure builds.

Question 6

Can I use Eyescale/CMake with existing CMake projects?

Accepted Answer

Yes, but integration may require adjustments, especially for subproject support where you need to change CMAKE_BINARY_DIR to PROJECT_BINARY_DIR in existing scripts, as noted in the SubProject documentation.

Question 7

How to generate documentation with the doxygen target?

Accepted Answer

Include DoxygenRule.cmake in your CMakeLists.txt after all targets, and a 'doxygen' target will be created to build API documentation into PROJECT_BINARY_DIR/doc, with an optional doxycopy target for distribution.

CMake

What is CMake?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions