FindCanberra

Try to find Canberra event sound library.

This will define the following variables:

If Canberra_FOUND is TRUE, it will also define the following imported target:

In general we recommend using the imported target, as it is easier to use. Bear in mind, however, that if the target is in the link interface of an exported library, it must be made available by the package config file.

Since 5.56.0.

FindEGL

Try to find EGL.

This will define the following variables:

If EGL_FOUND is TRUE, it will also define the following imported target:

In general we recommend using the imported target, as it is easier to use. Bear in mind, however, that if the target is in the link interface of an exported library, it must be made available by the package config file.

Since pre-1.0.0.

FindFontconfig

Try to find Fontconfig. Once done this will define the following variables:

If Fontconfig_FOUND is TRUE, it will also define the following imported target:

Fontconfig::Fontconfig

Since 5.57.0.

FindGLIB2

Try to locate the GLib2 library. If found, this will define the following variables:

If GLIB2_FOUND is TRUE, it will also define the following imported target:

Since 5.41.0.

FindGperf

Try to find GNU gperf.

If the gperf executable is not in your PATH, you can provide an alternative name or full path location with the Gperf_EXECUTABLE variable.

This will define the following variables:

If Gperf_FOUND is TRUE, it will also define the following imported target:

and the following public function:

Run gperf on <GperfInput> to generate <OutputFile>, adding it to the <OutputVariable> variable which contains the source for the target where <OutputFile> is going to be built. The optional GENERATION_FLAGS argument is needed to pass extra parameters to gperf (note you cannot override that way the output file).

A simple invocation would be:

ecm_gperf_generate(simple.gperf ${CMAKE_CURRENT_BINARY_DIR}/simple.h MySources)

Since 5.35.0.

FindGradle

Provides the ability to build Android AAR libraries using Gradle.

This relies on the Qt provided Gradle, so a Qt for Android installation is required.

This builds an Android AAR library using the given build.gradle file.

Installs a Android AAR library that has been created with gradle_add_aar.

Since 5.76.0.

FindIcoTool

Try to find icotool.

If the icotool executable is not in your PATH, you can provide an alternative name or full path location with the IcoTool_EXECUTABLE variable.

This will define the following variables:

If IcoTool_FOUND is TRUE, it will also define the following imported target:

Since 5.49.

FindInotify

This will define the following variables:

On Linux, the libraries and include directories are empty, even though Inotify_FOUND may be set to TRUE. This is because no special includes or libraries are needed. On other systems these may be needed to use inotify.

Since 5.32.0.

FindKF5

Find KDE Frameworks 5 with a single find_package() call.

This will use the package config files provided by the individual frameworks. For example, if you wish to find KArchive, which presents itself to CMake as KF5Archive (ie: you would do find_package(KF5Archive) to find it directly), you can do

find_package(KF5 COMPONENTS Archive)

If all the required components (those given in the COMPONENTS argument, but not those given in the OPTIONAL_COMPONENTS argument) are found, KF5_FOUND will be set to true. Otherwise, it will be set to false.

Since pre-1.0.0.

FindLibExiv2

Try to find the Exiv2 library.

This will define the following variables:

If LibExiv2_FOUND is TRUE, it will also define the following imported target:

In general we recommend using the imported target, as it is easier to use. Bear in mind, however, that if the target is in the link interface of an exported library, it must be made available by the package config file.

Since 5.53.0.

FindLibGit2

Try to find libgit2 on a Unix system.

This will define the following variables:

If LIBGIT2_FOUND is TRUE, it will also define the following imported target:

In general we recommend using the imported target, as it is easier to use. Bear in mind, however, that if the target is in the link interface of an exported library, it must be made available by the package config file.

Since 1.3.0.

FindOpenEXR

Try to find the OpenEXR libraries.

This will define the following variables:

and the following imported targets:

In general we recommend using the imported target, as it is easier to use. Bear in mind, however, that if the target is in the link interface of an exported library, it must be made available by the package config file.

Since pre-1.0.0.

FindPhoneNumber

Try to find PhoneNumber.

This is a component-based find module, which makes use of the COMPONENTS and OPTIONAL_COMPONENTS arguments to find_module. The following components are available:

PhoneNumber  GeoCoding

If no components are specified, this module will act as though all components were passed to OPTIONAL_COMPONENTS.

This module will define the following variables, independently of the components searched for or found:

For each searched-for components, PhoneNumber_<component>_FOUND will be set to TRUE if the corresponding library was found, and FALSE otherwise. If PhoneNumber_<component>_FOUND is TRUE, the imported target PhoneNumber::<component> will be defined.

Since 5.54.0.

FindPoppler

Try to find Poppler.

This is a component-based find module, which makes use of the COMPONENTS and OPTIONAL_COMPONENTS arguments to find_module. The following components are available:

Core  Cpp  Qt5  Qt4  Glib

If no components are specified, this module will act as though all components were passed to OPTIONAL_COMPONENTS.

This module will define the following variables, independently of the components searched for or found:

For each searched-for components, Poppler_<component>_FOUND will be set to TRUE if the corresponding Poppler library was found, and FALSE otherwise. If Poppler_<component>_FOUND is TRUE, the imported target Poppler::<component> will be defined. This module will also attempt to determine Poppler_*_VERSION variables for each imported target, although Poppler_VERSION should normally be sufficient.

In general we recommend using the imported targets, as they are easier to use and provide more control. Bear in mind, however, that if any target is in the link interface of an exported library, it must be made available by the package config file.

Since 5.19

FindPulseAudio

Try to locate the PulseAudio library. If found, this will define the following variables:

If PulseAudio_FOUND is TRUE, it will also define the following imported target:

Since 5.41.0.

FindQtWaylandScanner

Try to find qtwaylandscanner.

If the qtwaylandscanner executable is not in your PATH, you can provide an alternative name or full path location with the QtWaylandScanner_EXECUTABLE variable.

This will define the following variables:

If QtWaylandScanner_FOUND is TRUE, it will also define the following imported target:

This module provides the following functions to generate C++ protocol implementations:

ecm_add_qtwayland_client_protocol(<source_files_var>


                                  PROTOCOL <xmlfile>


                                  BASENAME <basename>


                                  [PREFIX <prefix>])

Generate C++ wrapper to Wayland client protocol files from <xmlfile> XML definition for the <basename> interface and append those files to <source_files_var>. Pass the <prefix> argument if the interface names don’t start with qt_ or wl_.

WaylandScanner is required and will be searched for.

ecm_add_qtwayland_server_protocol(<source_files_var>


                                  PROTOCOL <xmlfile>


                                  BASENAME <basename>


                                  [PREFIX <prefix>])

Generate C++ wrapper to Wayland server protocol files from <xmlfile> XML definition for the <basename> interface and append those files to <source_files_var>. Pass the <prefix> argument if the interface names don’t start with qt_ or wl_.

WaylandScanner is required and will be searched for.

Since 1.4.0.

FindSasl2

Try to find the SASL2 library.

This will define the following variables:

If Sasl2_FOUND is TRUE, the following imported target will be available:

Since 5.41.0.

FindSeccomp

Try to locate the libseccomp library.

This will define the following variables:

If Seccomp_FOUND is TRUE, it will also define the following imported target:

Since 5.44.0.

FindSharedMimeInfo

Try to find the shared-mime-info package.

This will define the following variables:

and the following imported targets:

The follow macro is available:

update_xdg_mimetypes(<path>)

Updates the XDG mime database at install time (unless the $DESTDIR environment variable is set, in which case it is up to package managers to perform this task).

Since pre-1.0.0.

FindTaglib

Try to find the Taglib library.

This will define the following variables:

If Taglib_FOUND is TRUE, it will also define the following imported target:

Since 5.72.0

SPDX-FileCopyrightText: 2006 Laurent Montel <montel@kde.org> SPDX-FileCopyrightText: 2019 Heiko Becker <heirecka@exherbo.org> SPDX-FileCopyrightText: 2020 Elvis Angelaccio <elvis.angelaccio@kde.org> SPDX-License-Identifier: BSD-3-Clause

FindUDev

Try to find the UDev library.

This will define the following variables:

If UDev_FOUND is TRUE, it will also define the following imported target:

Since 5.57.0.

FindWayland

Try to find Wayland.

This is a component-based find module, which makes use of the COMPONENTS and OPTIONAL_COMPONENTS arguments to find_module. The following components are available:

Client  Server  Cursor  Egl

If no components are specified, this module will act as though all components were passed to OPTIONAL_COMPONENTS.

This module will define the following variables, independently of the components searched for or found:

For each searched-for components, Wayland_<component>_FOUND will be set to TRUE if the corresponding Wayland library was found, and FALSE otherwise. If Wayland_<component>_FOUND is TRUE, the imported target Wayland::<component> will be defined. This module will also attempt to determine Wayland_*_VERSION variables for each imported target, although Wayland_VERSION should normally be sufficient.

In general we recommend using the imported targets, as they are easier to use and provide more control. Bear in mind, however, that if any target is in the link interface of an exported library, it must be made available by the package config file.

Since pre-1.0.0.

FindWaylandProtocols

Try to find wayland-protocols on a Unix system.

This will define the following variables:

FindWaylandScanner

Try to find wayland-scanner.

If the wayland-scanner executable is not in your PATH, you can provide an alternative name or full path location with the WaylandScanner_EXECUTABLE variable.

This will define the following variables:

If WaylandScanner_FOUND is TRUE, it will also define the following imported target:

This module provides the following functions to generate C protocol implementations:

ecm_add_wayland_client_protocol(<source_files_var>


                                PROTOCOL <xmlfile>


                                BASENAME <basename>)

Generate Wayland client protocol files from <xmlfile> XML definition for the <basename> interface and append those files to <source_files_var>.

ecm_add_wayland_server_protocol(<source_files_var>


                                PROTOCOL <xmlfile>


                                BASENAME <basename>)

Generate Wayland server protocol files from <xmlfile> XML definition for the <basename> interface and append those files to <source_files_var>.

Since 1.4.0.

FindX11_XCB

Try to find the X11 XCB compatibility library.

This will define the following variables:

If X11_XCB_FOUND is TRUE, it will also define the following imported target:

In general we recommend using the imported target, as it is easier to use. Bear in mind, however, that if the target is in the link interface of an exported library, it must be made available by the package config file.

Since pre-1.0.0.

FindXCB

Try to find XCB.

This is a component-based find module, which makes use of the COMPONENTS and OPTIONAL_COMPONENTS arguments to find_module. The following components are available:

XCB
ATOM         AUX          COMPOSITE    CURSOR       DAMAGE
DPMS         DRI2         DRI3         EVENT        EWMH
GLX          ICCCM        IMAGE        KEYSYMS      PRESENT
RANDR        RECORD       RENDER       RENDERUTIL   RES
SCREENSAVER  SHAPE        SHM          SYNC         UTIL
XEVIE        XF86DRI      XFIXES       XINERAMA     XINPUT
XKB          XPRINT       XTEST        XV           XVMC

If no components are specified, this module will act as though all components except XINPUT (which is considered unstable) were passed to OPTIONAL_COMPONENTS.

This module will define the following variables, independently of the components searched for or found:

For each searched-for components, XCB_<component>_FOUND will be set to true if the corresponding xcb library was found, and false otherwise. If XCB_<component>_FOUND is true, the imported target XCB::<component> will be defined. This module will also attempt to determine XCB_*_VERSION variables for each imported target, although XCB_VERSION should normally be sufficient.

In general we recommend using the imported targets, as they are easier to use and provide more control. Bear in mind, however, that if any target is in the link interface of an exported library, it must be made available by the package config file.

Since pre-1.0.0.

Findepoxy

Try to find libepoxy on a Unix system.

This will define the following variables:

If epoxy_FOUND is TRUE, it will also define the following imported target:

In general we recommend using the imported target, as it is easier to use. Bear in mind, however, that if the target is in the link interface of an exported library, it must be made available by the package config file.