| Age | Commit message (Collapse) | Author |
|---|
|
This adds an application icon to an executable from PNG files for
Windows and Mac OS X. Unlike the similar kde4_add_app_icon macro from
kdelibs, this requires icons to be explicitly listed as arguments
(meaning CMake can tell when ones are added or deleted and reconfigure
as appropriate), and it works with Matthias Benkmann's png2ico tool, as
well as the KDE-Win tool of the same name.
Currently missing unit tests. Also completely untested (except that
`make test` runs on Linux, so there are no obvious syntax errors).
With thanks to Ralf Habacker for the inital work on porting
kde4_add_app_icon.
CHANGELOG: Add ECMAddAppIcon module to add icons to executable targets
on Windows and Mac OS X.
|
|
While the search is unlikely to succeed on Windows, having different
behaviour between the platforms (eg: find_package(Wayland REQUIRED) was
not fatal on Windows, even though Wayland_FOUND would always be FALSE)
is not ideal, and if someone did port them to Windows for some reason,
the find modules should support that.
If applications actually want different behaviour between platforms
(like requiring a module on Unix, but not on Windows), they should
implement that logic themselves (since they will have to deal with
targets not being defined, etc, anyway).
REVIEW: 120481
|
|
Add a couple of find modules for wayland-scanner and qtwaylandscanner.
These modules find the respective executables and create a target that
points to the executable.
Targets are respectively Wayland::Scanner and Wayland::QtScanner.
There are also macros to generate C protocols with wayland-scanner and
C++ wrappers with qtwaylandscanner.
REVIEW: 120034
|
|
add FindLibGit2.cmake + doc link
scripts tries to detect version not by pkgconfig to work on windows without pkgconfig, too
REVIEW: 120196
|
|
REVIEW: 117780
|
|
ECMUseFindModules allows find modules to be copied to a local directory.
These find modules may use ECMFindModuleHelpers, but they will not be in
the same relative location to ECMFindModuleHelpers.cmake and there is no
guarantee that ECMFindModulesHelpers.cmake will be in the CMake module
path.
To solve this, we make sure there is always a stub file in the same
directory as the find modules that includes the real
ECMFindModuleHelpers.cmake. The one installed with ECM just includes
"../modules/ECMFindModuleHelpers.cmake", while ecm_use_find_modules
generates a stub that uses an absolute path.
REVIEW 117658
|
|
The traditional *_LIBRARIES, *_INCLUDE_DIRS and *_DEFINITIONS do have
some uses - they make it easier to create package config files that use
found libraries in their link interface. So this makes sure these
variables are set by ecm_find_package_handle_library_components() (and
hence by FindWayland.cmake and FindXCB.cmake).
REVIEW: 117585
|
|
Imported target, version handling, package description etc.
REVIEW: 117491
|
|
- Add version handling
- Improve the docs
- mark cache variables as advanced
- make the pkg-config call actually work
REVIEW: 117490
|
|
This is deliberately modelled very closely on CMake's documentation
system. It's a hefty patch, because it involved changing all the
documentation to be in reStructuredText format. I also cleaned up the
copyright/license statements at the same time.
Note that the find modules contain the full license, due to the fact
that ecm_use_find_module() copies them out of the ECM distribution.
|
|
This currently mostly contains macros for handling components;
FindWayland and FindXCB are ported to use this module, which comes with
various improvements for them.
REVIEW: 116653
|
|
The thumbnail: ioslave from kde-runtime needs it.
Reviewed-By: Alex Merry
|
|
REVIEW: 116616
|
|
First part of the diff makes sure find_package_handle_standard_args()
gets a version number to check against.
Second part ensures we get proper results from pkg-config even if not all
components are available. find_package(Wayland COMPONENTS Client Egl)
was failing for me because I have Client installed but not Egl, causing
pkg_check_modules() to not set any PKG_Wayland_${comp} variable.
REVIEW: 116598
|
|
These are only really useful to kdoctools, so they may as well live
there.
REVIEW: 115897
|
|
* define imported targets for all components
* add version information
* print message on Windows
* add package properties
* use handle components
REVIEW: 116046
|
|
Inspired by the FindXCB module it's using components to simplify
finding just the parts which are really required.
REVIEW: 116018
|
|
This module finds the egl library through pkg-config.
REVIEW: 116014
|
|
This is used by many projects (including any that install any extra mime
info).
REVIEW: 115749
|
|
The functionality of it is now provided by a KF5Config.cmake file.
Remember to remove it from your install prefix to avoid future
confusion.
CCMAIL: kde-frameworks-devel@kde.org
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There is no need for the package to tell us its install dir.
|
|
It is redundant and obsolete.
Some frameworks can have erroneous values (eg KConfigWidgets currently
sets FooBar_LIBRARIES). Downstreams are expected to use the imported
target name instead.
CCMAIL: kde-frameworks-devel@kde.org
|
|
It is redundant and obsolete. The framework template does not set it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Instead of finding all or nothing from XCB it becomes components aware.
So a user can just specify which XCB components it needs and compilation
doesn't fail if a not-needed unrelated component is not found. It also
allows to have some components as required and some as optional.
REVIEW: 112151
|
|
|
|
|
|
It approprietly sets the _FOUND variables, we were defining the all
uppercase instead.
Sorry for the mess!
CCMAIL: neundorf@kde.org
|
|
Reviewed-by: Alexander Neundorf
|
|
REVIEW: 112451
|
|
|
|
|
|
|
|
|
