extra-cmake-modules.git/modules, branch v5.63.0-rc1

new module ECMSourceVersionControl

2019-10-01T10:30:21+00:00

Summary:
simply sets a variable when the source is under version control. use it to
auto-enable Debug builds. there are also plans to switch special assertion
logic on in KIO when used from git, so there definitely is a more generic
use case of wanting to control behavior based on whether it the source is
likely used to make a development or production build.

conceivably the module could be used in the future to get git rev-parse or
the like, hence the generic name.

Test Plan: with .git the var is true, without it is false

Reviewers: kde-buildsystem, dfaure

Reviewed By: dfaure

Subscribers: apol, kossebau, kde-frameworks-devel

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D24159

API dox: fix ":" to "::"

2019-09-18T17:24:38+00:00

As intended by original code, to generate consistent output per
this document for the given lists of variables

GIT_SILENT

ECMAddQch: add INCLUDE_DIRS argument

2019-09-14T23:53:21+00:00

Summary:
Allows to have headers be found by doxygen, e.g. to properly process
preprocessor macros.

Reviewers: #build_system, dfaure

Reviewed By: dfaure

Subscribers: dfaure, kde-frameworks-devel, kde-buildsystem

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D23791

ECMAddQtDesignerPlugin: pass code sample indirectly via variable name arg

2019-09-06T19:41:19+00:00

Summary:
The initial API asked to have custom C++ code to be parsed as string
arguments. As any ";" in such strings would be treated as list separators,
the initial API as workaround required to encode those in the passed
code text with "@SEMICOLON@".

As alternative variant the approach from the GENERATE_EXPORT_HEADER()
macro and its CUSTOM_CONTENT_FROM_VARIABLE is now used, where instead
the name of the variable is passed, from which then the full code could
be fetched and directly used.
As API user one no longer can pass code snippets directly inline as
argument, but no longer needs to use the awkward @SEMICOLON@.

As ECMAddQtDesignerPlugin is not yet part of a released version,
the API can be still changed.

Reviewers: #frameworks, #build_system, vkrause

Subscribers: kde-frameworks-devel, kde-buildsystem

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D23725

Add ECMAddQtDesignerPlugin

2019-08-05T17:16:45+00:00

Summary:
ECMAddQtDesignerPlugin provides two macros that can be used to
replace the usage of the tool kgendesignerplugin from KDesignerPlugin.
This allows to have ECM-using libraries to create Qt Designer plugins without
the need for another separate tool.

For that purpose option structure & defaults are inspired from that one, to
allow simple porting. Main difference is that ECMAddQtDesignerPlugin
expects the widget metadata definition to be done in CMake code,
using a dedicated function, instead of in a ini-style separate ".widgets" file.

Porting of ".widgets" files basically means:
copy content into cmake, transform ini code into arguments to util method.
Key names need a bit of adaption, current names are open for dicussion.

Porting example:
```
[KActionSelector]
IncludeFile=kactionselector.h
ToolTip=A widget for selecting and arranging actions/objects
Group=Views (KF5)
```
gets
```
ecm_qtdesignerplugin_widget(KActionSelector
    INCLUDE_FILE kactionselector.h
    TOOLTIP "A widget for selecting and arranging actions/objects"
    GROUP "Views (KF5)"
)
```

Reviewers: #build_system, #frameworks

Subscribers: apol, kde-frameworks-devel, kde-buildsystem

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D22724

Re-enable the setting of QT_PLUGIN_PATH, without the strange backslash.

2019-03-31T18:30:16+00:00

Let's see if purpose unittests still work on Windows (which was the
reason this got commented out, kio_file wasn't found anymore).

CCMAIL: bcooksley@kde.org, kfunk@kde.org

ECMGeneratePkgConfigFile: make all vars dependent on ${prefix}

2019-03-05T14:40:26+00:00

Summary:
Note that the first test had a comment "without optional arguments"
so I removed the INCLUDE_INSTALL_DIR variable to test what happens by
default. The other tests still pass an absolute path there (which is
unusual in practice, and breaks the idea of using ${prefix}).

Test Plan: `ctest -R PkgConfig` passes

Reviewers: kossebau, apol, cgiboudeaux

Reviewed By: apol

Subscribers: kde-frameworks-devel, kde-buildsystem, fazevedo

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D19538

Fix harmless warnings when creating the doc.

2019-03-04T12:49:40+00:00

GIT_SILENT

ECMGeneratePkgConfigFile: add variables used by pkg_check_modules

2019-03-04T12:35:46+00:00

Summary:
If we ever end up in a situation where the generated .pc file is
actually used by cmake's pkg_check_modules, then we need the
includedir and libdir variables; pkg_check_modules ignores the
Makefile-like Libs and Cflags lines of the .pc file.

Context: craft adds a cmake buildsystem for sqlite3, which is then
found using pkgconfig in akonadi.

Test Plan: Filipe Azevedo is doing all the testing, I'm just providing patches :)

Reviewers: apol, fazevedo, cgiboudeaux

Reviewed By: fazevedo, cgiboudeaux

Subscribers: cgiboudeaux, fazevedo, kde-buildsystem, kde-frameworks-devel

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D19506

ECMGeneratePkgConfigFile API dox: fix "Since" for DESCRIPTION arg

2019-02-11T16:55:29+00:00

Summary: Also place "Since" next to both argument and argument description.

Reviewers: cgiboudeaux

Reviewed By: cgiboudeaux

Subscribers: kde-frameworks-devel, kde-buildsystem

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D18913