CMake
is a tool that helps simplify the build process for development projects across different platforms.
CMake
automates the generation of buildsystems such as Makefiles and Visual Studio project files.
CMake
是第 3 方工具,具有自己的
文档编制
. The rest of this topic details the specifics of how to use Qt 5 with
CMake
. The minimum version required to use Qt5 is
CMake
3.1.0.
The first requirement when using
CMake
is to use
find_package
to locate the libraries and header files shipped with Qt. These libraries and header files can then be used to build libraries and applications based on Qt.
The recommended way to use Qt libraries and headers with
CMake
is to use the
target_link_libraries
command. This command automatically adds appropriate include directories, compile definitions, the position-independent-code flag, and links to the qtmain.lib library on Windows.
To build a helloworld GUI executable, typical usage would be:
cmake_minimum_required(VERSION 3.1.0) project(helloworld) set(CMAKE_AUTOMOC ON) set(CMAKE_AUTORCC ON) set(CMAKE_AUTOUIC ON) if(CMAKE_VERSION VERSION_LESS "3.7.0") set(CMAKE_INCLUDE_CURRENT_DIR ON) endif() find_package(Qt5 COMPONENTS Widgets REQUIRED) add_executable(helloworld mainwindow.ui mainwindow.cpp main.cpp resources.qrc ) target_link_libraries(helloworld Qt5::Widgets)
In order for
find_package
to be successful, Qt 5 must be found below the CMAKE_PREFIX_PATH, or the
Qt5_DIR
must be set in the
CMake
缓存为位置对于
Qt5Config.cmake
file. The easiest way to use
CMake
is to set the CMAKE_PREFIX_PATH environment variable to the install prefix of Qt 5.
The CMAKE_AUTOMOC setting runs moc automatically when required. For more on this feature see the CMake AUTOMOC 文档编制
Imported targets are created for each Qt module. Imported target names should be preferred instead of using a variable like Qt5<Module>
_LIBRARIES
in CMake commands such as
target_link_libraries
. The actual path to the library can be obtained using the
LOCATION property
:
find_package(Qt5 COMPONENTS Core REQUIRED) get_target_property(QtCore_location Qt5::Core LOCATION)
Note however that it is rare to require the full location to the library in
CMake
code. Most
CMake
APIs are aware of imported targets and can automatically use them instead of the full path.
Each module in Qt 5 has a library target with the naming convention Qt5::<Module> which can be used for this purpose.
Imported targets are created with the configurations Qt was configured with. That is, if Qt was configured with the -debug switch, an imported target with the configuration DEBUG will be created. If Qt was configured with the -release switch an imported target with the configuration RELEASE will be created. If Qt was configured with the -debug-and-release switch (the default on windows), then imported targets will be created with both RELEASE and DEBUG configurations.
If your project has custom CMake build configurations, it may be necessary to set a mapping from your custom configuration to either the debug or release Qt configuration.
find_package(Qt5 COMPONENTS Core REQUIRED) set(CMAKE_CXX_FLAGS_COVERAGE "${CMAKE_CXX_FLAGS_RELEASE} -fprofile-arcs -ftest-coverage") # set up a mapping so that the Release configuration for the Qt imported target is # used in the COVERAGE CMake configuration. set_target_properties(Qt5::Core PROPERTIES MAP_IMPORTED_CONFIG_COVERAGE "RELEASE")
Plugins are also available as
IMPORTED
targets in CMake. The
Qt Network
,
Qt SQL
,
Qt GUI
,和
Qt Widgets
modules have plugins associated. They provide a list of plugins in the
Qt5
<Module>
_PLUGINS
变量。
foreach(plugin ${Qt5Network_PLUGINS}) get_target_property(_loc ${plugin} LOCATION) message("Plugin ${plugin} is at location ${_loc}") endforeach()
The result of a
find_package
call is that imported targets will be created for use with
target_link_libraries
, some variables will be populated with information required to configure the build, and macros will be made available for use. The name of the imported target for each module matches the name of the module with a prefix of 'Qt5::', for example
Qt5::Widgets
. All of the package-specific variables have a consistent name with a prefix of the name of the package. For example,
find_package(Qt5 COMPONENTS Widgets)
will make the following variables available if successfully found:
Equivalents of those variables will be available for all packages found with a
find_package
call. Note that the variables are case-sensitive.
Additionally, several other variables are available which do not relate to a particular package, but to the Qt installation itself.
qt5_add_big_resources | 将大型二进制资源编译成对象代码 |
qt5_add_binary_resources | 从 Qt 资源文件列表创建 RCC 文件 |
qt5_add_resources | 将二进制资源编译成源代码 |
qt5_generate_moc | 当输入文件时调用 moc |
qt5_wrap_cpp | 从源代码创建 .moc 文件 |
qt5_wrap_ui | 创建 .ui 文件的源 |
qt5_add_dbus_adaptor | 为 D-Bus 接口生成适配器类 |
qt5_add_dbus_interface | 生成实现 D-Bus 接口描述文件接口的 C++ 源 |
qt5_add_dbus_interfaces | 生成实现 D-Bus 接口描述文件接口的 C++ 源 |
qt5_generate_dbus_interface | 从头文件生成 D-Bus 接口 |
qt5_add_translation | 将 Qt Linguist .ts 文件编译成 .qm 文件 |
qt5_create_translation | 设置 Qt Linguist 翻译工具链 |