1ECM-FIND-MODULES(7) Extra CMake Modules ECM-FIND-MODULES(7)
2
6 ecm-find-modules - ECM Find Modules Reference
7
9 Find modules are used by the CMake find_package command to search for
10 packages that do not provide their own CMake package config files.
11 CMake provides an extensive set of find modules, and Extra CMake Mod‐
12 ules (ECM) adds to that.
13 To use ECM’s find modules, you need to tell CMake to find the ECM pack‐
15 age, and then add either ${ECM_MODULE_PATH} or ${ECM_FIND_MODULE_DIR}
16 to the CMAKE_MODULE_PATH variable:
17 find_package(ECM REQUIRED NO_MODULE)
19 set(CMAKE_MODULE_PATH ${ECM_FIND_MODULE_DIR})
20 Using ${ECM_MODULE_PATH} will also make the modules intended for direct
22 use by CMake scripts available (see ecm-modules(7) and ecm-kde-mod‐
23 ules(7)).
24 You can also make local copies of find modules using the
26 ecm_use_find_modules function from ECMUseFindModules, which is automat‐
27 ically included when ECM is found:
28 find_package(ECM REQUIRED NO_MODULE)
30 ecm_use_find_modules(
31 DIR "${CMAKE_BINARY_DIR}/cmake"
32 MODULES FindEGL.cmake
33 )
34 set(CMAKE_MODULE_PATH "${CMAKE_BINARY_DIR}/cmake")
35 This allows selective use of ECM’s find modules, and the NO_OVERRIDE
37 argument can be used to ensure that if CMake ships its own version of
38 that find module, it will be used instead.
39
41 FindCanberra
42 Try to find Canberra event sound library.
43 This will define the following variables:
45 Canberra_FOUND
47 True if (the requested version of) Canberra is available
48 Canberra_VERSION
50 The version of Canberra
51 Canberra_LIBRARIES
53 The libraries of Canberra for use with target_link_libraries()
54 Canberra_INCLUDE_DIRS
56 The include dirs of Canberra for use with target_include_direc‐
57 tories()
58 If Canberra_FOUND is TRUE, it will also define the following imported
60 target:
61 Canberra::Canberra
63 The Canberra library
64 In general we recommend using the imported target, as it is easier to
66 use. Bear in mind, however, that if the target is in the link inter‐
67 face of an exported library, it must be made available by the package
68 config file.
69 Since 5.56.0.
71 FindEGL
73 Try to find EGL.
74 This will define the following variables:
76 EGL_FOUND
78 True if (the requested version of) EGL is available
79 EGL_VERSION
81 The version of EGL; note that this is the API version defined in
82 the headers, rather than the version of the implementation (eg:
83 Mesa)
84 EGL_LIBRARIES
86 This can be passed to target_link_libraries() instead of the
87 EGL::EGL target
88 EGL_INCLUDE_DIRS
90 This should be passed to target_include_directories() if the
91 target is not used for linking
92 EGL_DEFINITIONS
94 This should be passed to target_compile_options() if the target
95 is not used for linking
96 If EGL_FOUND is TRUE, it will also define the following imported tar‐
98 get:
99 EGL::EGL
101 The EGL library
102 In general we recommend using the imported target, as it is easier to
104 use. Bear in mind, however, that if the target is in the link inter‐
105 face of an exported library, it must be made available by the package
106 config file.
107 Since pre-1.0.0.
109 FindFontconfig
111 Try to find Fontconfig. Once done this will define the following vari‐
112 ables:
113 Fontconfig_FOUND
115 True if Fontconfig is available
116 Fontconfig_INCLUDE_DIRS
118 The include directory to use for the Fontconfig headers
119 Fontconfig_LIBRARIES
121 The Fontconfig libraries for linking
122 Fontconfig_DEFINITIONS
124 Compiler switches required for using Fontconfig
125 Fontconfig_VERSION
127 The version of Fontconfig that has been found
128 If Fontconfig_FOUND is TRUE, it will also define the following imported
130 target:
131 Fontconfig::Fontconfig
133 Since 5.57.0.
135 FindGLIB2
137 Try to locate the GLib2 library. If found, this will define the fol‐
138 lowing variables:
139 GLIB2_FOUND
141 True if the GLib2 library is available
142 GLIB2_INCLUDE_DIRS
144 The GLib2 include directories
145 GLIB2_LIBRARIES
147 The GLib2 libraries for linking
148 GLIB2_INCLUDE_DIR
150 Deprecated, use GLIB2_INCLUDE_DIRS
151 GLIB2_LIBRARY
153 Deprecated, use GLIB2_LIBRARIES
154 If GLIB2_FOUND is TRUE, it will also define the following imported tar‐
156 get:
157 GLIB2::GLIB2
159 The GLIB2 library
160 Since 5.41.0.
162 FindGperf
164 Try to find GNU gperf.
165 If the gperf executable is not in your PATH, you can provide an alter‐
167 native name or full path location with the Gperf_EXECUTABLE variable.
168 This will define the following variables:
170 Gperf_FOUND
172 True if gperf is available.
173 Gperf_EXECUTABLE
175 The gperf executable.
176 If Gperf_FOUND is TRUE, it will also define the following imported tar‐
178 get:
179 GPerf::Gperf
181 The gperf executable.
182 and the following public function:
184 ecm_gperf_generate(<GperfInput> <OutputFile> <OutputVariable>
186 [GENERATION_FLAGS <flags>])
187 Run gperf on <GperfInput> to generate <OutputFile>, adding it to the
189 <OutputVariable> variable which contains the source for the target
190 where <OutputFile> is going to be built. The optional GENERATION_FLAGS
191 argument is needed to pass extra parameters to gperf (note you cannot
192 override that way the output file).
193 A simple invocation would be:
195 ecm_gperf_generate(simple.gperf ${CMAKE_CURRENT_BINARY_DIR}/simple.h MySources)
197 Since 5.35.0.
199 FindGradle
201 Provides the ability to build Android AAR libraries using Gradle.
202 This relies on the Qt provided Gradle, so a Qt for Android installation
204 is required.
205 gradle_add_aar(<target>
207 BUIDLFILE build.gradle NAME <aar-name>)
208 This builds an Android AAR library using the given build.gradle file.
210 gradle_install_aar(<target>
212 DESTINATION <dest>)
213 Installs a Android AAR library that has been created with gra‐
215 dle_add_aar.
216 Since 5.76.0.
218 FindIcoTool
220 Try to find icotool.
221 If the icotool executable is not in your PATH, you can provide an
223 alternative name or full path location with the IcoTool_EXECUTABLE
224 variable.
225 This will define the following variables:
227 IcoTool_FOUND
229 True if icotool is available.
230 IcoTool_EXECUTABLE
232 The icotool executable.
233 If IcoTool_FOUND is TRUE, it will also define the following imported
235 target:
236 IcoTool::IcoTool
238 The icotool executable.
239 Since 5.49.
241 FindInotify
243 Try to find inotify on this system. This finds:
244 · libinotify on Unix like systems, or
246 · the kernel’s inotify on Linux systems.
248 This will define the following variables:
250 Inotify_FOUND
252 True if inotify is available
253 Inotify_LIBRARIES
255 This has to be passed to target_link_libraries()
256 Inotify_INCLUDE_DIRS
258 This has to be passed to target_include_directories()
259 On Linux, the libraries and include directories are empty, even though
261 Inotify_FOUND may be set to TRUE. This is because no special includes
262 or libraries are needed. On other systems these may be needed to use
263 inotify.
264 Since 5.32.0.
266 FindKF5
268 Find KDE Frameworks 5 with a single find_package() call.
269 This will use the package config files provided by the individual
271 frameworks. For example, if you wish to find KArchive, which presents
272 itself to CMake as KF5Archive (ie: you would do find_package(KF5Ar‐
273 chive) to find it directly), you can do
274 find_package(KF5 COMPONENTS Archive)
276 If all the required components (those given in the COMPONENTS argument,
278 but not those given in the OPTIONAL_COMPONENTS argument) are found,
279 KF5_FOUND will be set to true. Otherwise, it will be set to false.
280 Since pre-1.0.0.
282 FindLibExiv2
284 Try to find the Exiv2 library.
285 This will define the following variables:
287 LibExiv2_FOUND
289 True if (the requested version of) Exiv2 is available
290 LibExiv2_VERSION
292 The version of Exiv2
293 LibExiv2_INCLUDE_DIRS
295 The include dirs of Exiv2 for use with target_include_directo‐
296 ries()
297 LibExiv2_LIBRARIES
299 The Exiv2 library for use with target_link_libraries(). This
300 can be passed to target_link_libraries() instead of the
301 LibExiv2::LibExiv2 target
302 If LibExiv2_FOUND is TRUE, it will also define the following imported
304 target:
305 LibExiv2::LibExiv2
307 The Exiv2 library
308 In general we recommend using the imported target, as it is easier to
310 use. Bear in mind, however, that if the target is in the link inter‐
311 face of an exported library, it must be made available by the package
312 config file.
313 Since 5.53.0.
315 FindLibGit2
317 Try to find libgit2 on a Unix system.
318 This will define the following variables:
320 LIBGIT2_FOUND
322 True if (the requested version of) libgit2 is available
323 LIBGIT2_VERSION
325 The version of libgit2
326 LIBGIT2_LIBRARIES
328 This can be passed to target_link_libraries() instead of the
329 LibGit2::LibGit2 target
330 LIBGIT2_INCLUDE_DIRS
332 This should be passed to target_include_directories() if the
333 target is not used for linking
334 LIBGIT2_DEFINITIONS
336 This should be passed to target_compile_options() if the target
337 is not used for linking
338 If LIBGIT2_FOUND is TRUE, it will also define the following imported
340 target:
341 LibGit2::LibGit2
343 The libgit2 library
344 In general we recommend using the imported target, as it is easier to
346 use. Bear in mind, however, that if the target is in the link inter‐
347 face of an exported library, it must be made available by the package
348 config file.
349 Since 1.3.0.
351 FindOpenEXR
353 Try to find the OpenEXR libraries.
354 This will define the following variables:
356 OpenEXR_FOUND
358 True if OpenEXR is available
359 OpenEXR_LIBRARIES
361 Link to these to use OpenEXR
362 OpenEXR_INCLUDE_DIRS
364 Include directory for OpenEXR
365 OpenEXR_DEFINITIONS
367 Compiler flags required to link against OpenEXR
368 and the following imported targets:
370 OpenEXR::IlmImf
372 The OpenEXR core library
373 In general we recommend using the imported target, as it is easier to
375 use. Bear in mind, however, that if the target is in the link inter‐
376 face of an exported library, it must be made available by the package
377 config file.
378 Since pre-1.0.0.
380 FindPhoneNumber
382 Try to find PhoneNumber.
383 This is a component-based find module, which makes use of the COMPO‐
385 NENTS and OPTIONAL_COMPONENTS arguments to find_module. The following
386 components are available:
387 PhoneNumber GeoCoding
389 If no components are specified, this module will act as though all com‐
391 ponents were passed to OPTIONAL_COMPONENTS.
392 This module will define the following variables, independently of the
394 components searched for or found:
395 PhoneNumber_FOUND
397 True if (the requestion version of) PhoneNumber is available
398 For each searched-for components, PhoneNumber_<component>_FOUND will be
400 set to TRUE if the corresponding library was found, and FALSE other‐
401 wise. If PhoneNumber_<component>_FOUND is TRUE, the imported target
402 PhoneNumber::<component> will be defined.
403 Since 5.54.0.
405 FindPoppler
407 Try to find Poppler.
408 This is a component-based find module, which makes use of the COMPO‐
410 NENTS and OPTIONAL_COMPONENTS arguments to find_module. The following
411 components are available:
412 Core Cpp Qt5 Qt4 Glib
414 If no components are specified, this module will act as though all com‐
416 ponents were passed to OPTIONAL_COMPONENTS.
417 This module will define the following variables, independently of the
419 components searched for or found:
420 Poppler_FOUND
422 TRUE if (the requested version of) Poppler is available
423 Poppler_VERSION
425 Found Poppler version
426 Poppler_TARGETS
428 A list of all targets imported by this module (note that there
429 may be more than the components that were requested)
430 Poppler_LIBRARIES
432 This can be passed to target_link_libraries() instead of the
433 imported targets
434 Poppler_INCLUDE_DIRS
436 This should be passed to target_include_directories() if the
437 targets are not used for linking
438 Poppler_DEFINITIONS
440 This should be passed to target_compile_options() if the targets
441 are not used for linking
442 For each searched-for components, Poppler_<component>_FOUND will be set
444 to TRUE if the corresponding Poppler library was found, and FALSE oth‐
445 erwise. If Poppler_<component>_FOUND is TRUE, the imported target Pop‐
446 pler::<component> will be defined. This module will also attempt to
447 determine Poppler_*_VERSION variables for each imported target,
448 although Poppler_VERSION should normally be sufficient.
449 In general we recommend using the imported targets, as they are easier
451 to use and provide more control. Bear in mind, however, that if any
452 target is in the link interface of an exported library, it must be made
453 available by the package config file.
454 Since 5.19
456 FindPulseAudio
458 Try to locate the PulseAudio library. If found, this will define the
459 following variables:
460 PulseAudio_FOUND
462 True if the system has the PulseAudio library of at least the
463 minimum version specified by either the version parameter to
464 find_package() or the variable PulseAudio_MINIMUM_VERSION
465 PulseAudio_INCLUDE_DIRS
467 The PulseAudio include directory
468 PulseAudio_LIBRARIES
470 The PulseAudio libraries for linking
471 PulseAudio_MAINLOOP_LIBRARY
473 The libraries needed to use PulseAudio Mainloop
474 PulseAudio_VERSION
476 The version of PulseAudio that was found
477 PulseAudio_INCLUDE_DIR
479 Deprecated, use PulseAudio_INCLUDE_DIRS
480 PulseAudio_LIBRARY
482 Deprecated, use PulseAudio_LIBRARIES
483 If PulseAudio_FOUND is TRUE, it will also define the following imported
485 target:
486 PulseAudio::PulseAudio
488 The PulseAudio library
489 Since 5.41.0.
491 FindQtWaylandScanner
493 Try to find qtwaylandscanner.
494 If the qtwaylandscanner executable is not in your PATH, you can provide
496 an alternative name or full path location with the QtWaylandScan‐
497 ner_EXECUTABLE variable.
498 This will define the following variables:
500 QtWaylandScanner_FOUND
502 True if qtwaylandscanner is available
503 QtWaylandScanner_EXECUTABLE
505 The qtwaylandscanner executable.
506 If QtWaylandScanner_FOUND is TRUE, it will also define the following
508 imported target:
509 Wayland::QtScanner
511 The qtwaylandscanner executable.
512 This module provides the following functions to generate C++ protocol
514 implementations:
515 · ecm_add_qtwayland_client_protocol
517 · ecm_add_qtwayland_server_protocol
519 ecm_add_qtwayland_client_protocol(<source_files_var>
521 PROTOCOL <xmlfile>
522 BASENAME <basename>
523 [PREFIX <prefix>])
524 Generate C++ wrapper to Wayland client protocol files from <xmlfile>
526 XML definition for the <basename> interface and append those files to
527 <source_files_var>. Pass the <prefix> argument if the interface names
528 don’t start with qt_ or wl_.
529 WaylandScanner is required and will be searched for.
531 ecm_add_qtwayland_server_protocol(<source_files_var>
533 PROTOCOL <xmlfile>
534 BASENAME <basename>
535 [PREFIX <prefix>])
536 Generate C++ wrapper to Wayland server protocol files from <xmlfile>
538 XML definition for the <basename> interface and append those files to
539 <source_files_var>. Pass the <prefix> argument if the interface names
540 don’t start with qt_ or wl_.
541 WaylandScanner is required and will be searched for.
543 Since 1.4.0.
545 FindSasl2
547 Try to find the SASL2 library.
548 This will define the following variables:
550 Sasl2_FOUND
552 System has SASL2.
553 Sasl2_VERSION
555 The version of SASL2.
556 Sasl2_INCLUDE_DIRS
558 This should be passed to target_include_directories() if the
559 target is not used for linking.
560 Sasl2_LIBRARIES
562 The SASL2 library. This can be passed to tar‐
563 get_link_libraries() instead of the Sasl2::Sasl2 target
564 If Sasl2_FOUND is TRUE, the following imported target will be avail‐
566 able:
567 Sasl2::Sasl2
569 The SASL2 library
570 Since 5.41.0.
572 FindSeccomp
574 Try to locate the libseccomp library.
575 This will define the following variables:
577 Seccomp_FOUND
579 True if the seccomp library is available
580 Seccomp_INCLUDE_DIRS
582 The seccomp include directories
583 Seccomp_LIBRARIES
585 The seccomp libraries for linking
586 If Seccomp_FOUND is TRUE, it will also define the following imported
588 target:
589 Seccomp::Seccomp
591 The Seccomp library
592 Since 5.44.0.
594 FindSharedMimeInfo
596 Try to find the shared-mime-info package.
597 This will define the following variables:
599 SharedMimeInfo_FOUND
601 True if system has the shared-mime-info package
602 UPDATE_MIME_DATABASE_EXECUTABLE
604 The update-mime-database executable
605 and the following imported targets:
607 SharedMimeInfo::UpdateMimeDatabase
609 The update-mime-database executable
610 The follow macro is available:
612 update_xdg_mimetypes(<path>)
614 Updates the XDG mime database at install time (unless the $DESTDIR
616 environment variable is set, in which case it is up to package managers
617 to perform this task).
618 Since pre-1.0.0.
620 FindTaglib
622 Try to find the Taglib library.
623 This will define the following variables:
625 Taglib_FOUND
627 True if the system has the taglib library of at least the mini‐
628 mum version specified by the version parameter to find_package()
629 Taglib_INCLUDE_DIRS
631 The taglib include dirs for use with target_include_directories
632 Taglib_LIBRARIES
634 The taglib libraries for use with target_link_libraries()
635 Taglib_VERSION
637 The version of taglib that was found
638 If Taglib_FOUND is TRUE, it will also define the following imported
640 target:
641 Taglib::Taglib
643 The Taglib library
644 Since 5.72.0
646 SPDX-FileCopyrightText: 2006 Laurent Montel <montel@kde.org> SPDX-File‐
648 CopyrightText: 2019 Heiko Becker <heirecka@exherbo.org> SPDX-FileCopy‐
649 rightText: 2020 Elvis Angelaccio <elvis.angelaccio@kde.org>
650 SPDX-License-Identifier: BSD-3-Clause
651 FindUDev
653 Try to find the UDev library.
654 This will define the following variables:
656 UDev_FOUND
658 System has UDev.
659 UDev_INCLUDE_DIRS
661 The libudev include directory.
662 UDev_LIBRARIES
664 The libudev libraries.
665 UDev_VERSION
667 The libudev version.
668 If UDev_FOUND is TRUE, it will also define the following imported tar‐
670 get:
671 UDev::UDev
673 The UDev library
674 Since 5.57.0.
676 FindWayland
678 Try to find Wayland.
679 This is a component-based find module, which makes use of the COMPO‐
681 NENTS and OPTIONAL_COMPONENTS arguments to find_module. The following
682 components are available:
683 Client Server Cursor Egl
685 If no components are specified, this module will act as though all com‐
687 ponents were passed to OPTIONAL_COMPONENTS.
688 This module will define the following variables, independently of the
690 components searched for or found:
691 Wayland_FOUND
693 TRUE if (the requested version of) Wayland is available
694 Wayland_VERSION
696 Found Wayland version
697 Wayland_TARGETS
699 A list of all targets imported by this module (note that there
700 may be more than the components that were requested)
701 Wayland_LIBRARIES
703 This can be passed to target_link_libraries() instead of the
704 imported targets
705 Wayland_INCLUDE_DIRS
707 This should be passed to target_include_directories() if the
708 targets are not used for linking
709 Wayland_DEFINITIONS
711 This should be passed to target_compile_options() if the targets
712 are not used for linking
713 Wayland_DATADIR
715 The core wayland protocols data directory Since 5.73.0
716 For each searched-for components, Wayland_<component>_FOUND will be set
718 to TRUE if the corresponding Wayland library was found, and FALSE oth‐
719 erwise. If Wayland_<component>_FOUND is TRUE, the imported target Way‐
720 land::<component> will be defined. This module will also attempt to
721 determine Wayland_*_VERSION variables for each imported target,
722 although Wayland_VERSION should normally be sufficient.
723 In general we recommend using the imported targets, as they are easier
725 to use and provide more control. Bear in mind, however, that if any
726 target is in the link interface of an exported library, it must be made
727 available by the package config file.
728 Since pre-1.0.0.
730 FindWaylandProtocols
732 Try to find wayland-protocols on a Unix system.
733 This will define the following variables:
735 WaylandProtocols_FOUND
737 True if (the requested version of) wayland-protocols is avail‐
738 able
739 WaylandProtocols_VERSION
741 The version of wayland-protocols
742 WaylandProtocols_DATADIR
744 The wayland protocols data directory
745 FindWaylandScanner
747 Try to find wayland-scanner.
748 If the wayland-scanner executable is not in your PATH, you can provide
750 an alternative name or full path location with the WaylandScanner_EXE‐
751 CUTABLE variable.
752 This will define the following variables:
754 WaylandScanner_FOUND
756 True if wayland-scanner is available.
757 WaylandScanner_EXECUTABLE
759 The wayland-scanner executable.
760 If WaylandScanner_FOUND is TRUE, it will also define the following
762 imported target:
763 Wayland::Scanner
765 The wayland-scanner executable.
766 This module provides the following functions to generate C protocol
768 implementations:
769 · ecm_add_wayland_client_protocol
771 · ecm_add_wayland_server_protocol
773 ecm_add_wayland_client_protocol(<source_files_var>
775 PROTOCOL <xmlfile>
776 BASENAME <basename>)
777 Generate Wayland client protocol files from <xmlfile> XML definition
779 for the <basename> interface and append those files to
780 <source_files_var>.
781 ecm_add_wayland_server_protocol(<source_files_var>
783 PROTOCOL <xmlfile>
784 BASENAME <basename>)
785 Generate Wayland server protocol files from <xmlfile> XML definition
787 for the <basename> interface and append those files to
788 <source_files_var>.
789 Since 1.4.0.
791 FindX11_XCB
793 Try to find the X11 XCB compatibility library.
794 This will define the following variables:
796 X11_XCB_FOUND
798 True if (the requested version of) libX11-xcb is available
799 X11_XCB_VERSION
801 The version of libX11-xcb (this is not guaranteed to be set even
802 when X11_XCB_FOUND is true)
803 X11_XCB_LIBRARIES
805 This can be passed to target_link_libraries() instead of the
806 EGL::EGL target
807 X11_XCB_INCLUDE_DIR
809 This should be passed to target_include_directories() if the
810 target is not used for linking
811 X11_XCB_DEFINITIONS
813 This should be passed to target_compile_options() if the target
814 is not used for linking
815 If X11_XCB_FOUND is TRUE, it will also define the following imported
817 target:
818 X11::XCB
820 The X11 XCB compatibility library
821 In general we recommend using the imported target, as it is easier to
823 use. Bear in mind, however, that if the target is in the link inter‐
824 face of an exported library, it must be made available by the package
825 config file.
826 Since pre-1.0.0.
828 FindXCB
830 Try to find XCB.
831 This is a component-based find module, which makes use of the COMPO‐
833 NENTS and OPTIONAL_COMPONENTS arguments to find_module. The following
834 components are available:
835 XCB
837 ATOM AUX COMPOSITE CURSOR DAMAGE
838 DPMS DRI2 DRI3 EVENT EWMH
839 GLX ICCCM IMAGE KEYSYMS PRESENT
840 RANDR RECORD RENDER RENDERUTIL RES
841 SCREENSAVER SHAPE SHM SYNC UTIL
842 XEVIE XF86DRI XFIXES XINERAMA XINPUT
843 XKB XPRINT XTEST XV XVMC
844 If no components are specified, this module will act as though all com‐
846 ponents except XINPUT (which is considered unstable) were passed to
847 OPTIONAL_COMPONENTS.
848 This module will define the following variables, independently of the
850 components searched for or found:
851 XCB_FOUND
853 True if (the requestion version of) xcb is available
854 XCB_VERSION
856 Found xcb version
857 XCB_TARGETS
859 A list of all targets imported by this module (note that there
860 may be more than the components that were requested)
861 XCB_LIBRARIES
863 This can be passed to target_link_libraries() instead of the
864 imported targets
865 XCB_INCLUDE_DIRS
867 This should be passed to target_include_directories() if the
868 targets are not used for linking
869 XCB_DEFINITIONS
871 This should be passed to target_compile_options() if the targets
872 are not used for linking
873 For each searched-for components, XCB_<component>_FOUND will be set to
875 true if the corresponding xcb library was found, and false otherwise.
876 If XCB_<component>_FOUND is true, the imported target XCB::<component>
877 will be defined. This module will also attempt to determine XCB_*_VER‐
878 SION variables for each imported target, although XCB_VERSION should
879 normally be sufficient.
880 In general we recommend using the imported targets, as they are easier
882 to use and provide more control. Bear in mind, however, that if any
883 target is in the link interface of an exported library, it must be made
884 available by the package config file.
885 Since pre-1.0.0.
887 Findepoxy
889 Try to find libepoxy on a Unix system.
890 This will define the following variables:
892 epoxy_FOUND
894 True if (the requested version of) libepoxy is available
895 epoxy_VERSION
897 The version of libepoxy
898 epoxy_LIBRARIES
900 This should be passed to target_link_libraries() if the target
901 is not used for linking
902 epoxy_INCLUDE_DIRS
904 This should be passed to target_include_directories() if the
905 target is not used for linking
906 epoxy_DEFINITIONS
908 This should be passed to target_compile_options() if the target
909 is not used for linking
910 epoxy_HAS_GLX
912 True if GLX support is available
913 If epoxy_FOUND is TRUE, it will also define the following imported tar‐
915 get:
916 epoxy::epoxy
918 The epoxy library
919 In general we recommend using the imported target, as it is easier to
921 use. Bear in mind, however, that if the target is in the link inter‐
922 face of an exported library, it must be made available by the package
923 config file.
924
926 ecm(7), ecm-modules(7), ecm-kde-modules(7)
927
929 KDE Developers
9305.79 Feb 06, 2021 ECM-FIND-MODULES(7)