<feed xmlns='http://www.w3.org/2005/Atom'>
<title>extra-cmake-modules.git/docs/module, branch v5.92.0</title>
<subtitle>hurd extra-cmake-modules.git</subtitle>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/'/>
<entry>
<title>Add missing doc links</title>
<updated>2022-02-16T13:03:42+00:00</updated>
<author>
<name>Julius Künzel</name>
<email>jk.kdedev@smartlab.uber.space</email>
</author>
<published>2022-02-16T13:03:42+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=40c21b97bc02cdf0394cfc6e02f4b42808c1690f'/>
<id>40c21b97bc02cdf0394cfc6e02f4b42808c1690f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Rename KDEDeprecationSettings to ECMDeprecationSettings</title>
<updated>2022-01-09T19:23:30+00:00</updated>
<author>
<name>Alexander Lohnau</name>
<email>alexander.lohnau@gmx.de</email>
</author>
<published>2022-01-09T19:22:30+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=2ce35e24ba218ed5e79b2d70f4589e408e01db5c'/>
<id>2ce35e24ba218ed5e79b2d70f4589e408e01db5c</id>
<content type='text'>
Semantically this is an ECM module, because it can be used to manage deprecated
Qt API and from any project which use ecm_generate_export_headers
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Semantically this is an ECM module, because it can be used to manage deprecated
Qt API and from any project which use ecm_generate_export_headers
</pre>
</div>
</content>
</entry>
<entry>
<title>Introduce plausibility check for outbound licenes</title>
<updated>2020-09-26T10:32:56+00:00</updated>
<author>
<name>Andreas Cord-Landwehr</name>
<email>cordlandwehr@kde.org</email>
</author>
<published>2020-09-26T10:32:56+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=7e73f1a972f13699c3c2cb80ad50c834b8a8464e'/>
<id>7e73f1a972f13699c3c2cb80ad50c834b8a8464e</id>
<content type='text'>
When creating a library or executable, several source files are combined
into a binary artifact that has an outbound license of its own. This test
generator allows to check if the combined source files are compatible
with the desired outbound license.

Requirements for using these tests:
- input source files must contain the SPDX-License-Information tag
- python3 must be available
- the "reuse spdx" tool must be available
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When creating a library or executable, several source files are combined
into a binary artifact that has an outbound license of its own. This test
generator allows to check if the combined source files are compatible
with the desired outbound license.

Requirements for using these tests:
- input source files must contain the SPDX-License-Information tag
- python3 must be available
- the "reuse spdx" tool must be available
</pre>
</div>
</content>
</entry>
<entry>
<title>Add ecm_generate_dbus_service_file</title>
<updated>2020-07-10T13:12:25+00:00</updated>
<author>
<name>Henri Chain</name>
<email>henri.chain@enioka.com</email>
</author>
<published>2020-07-10T13:12:25+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=01f7fe8f78e72dcda6000c70fd8b1d5bfefc46f2'/>
<id>01f7fe8f78e72dcda6000c70fd8b1d5bfefc46f2</id>
<content type='text'>
Summary:
It serves as a replacement for `kdbusaddons_generate_dbus_service_file`.

An application can be a DBus-activated service just fine without using KDBusAddons.
Moreover, this new module uses named arguments for future-proofing, and adds support for specifying a `SystemdService`.
It also cleans up the confusion on what the "path" is about: Rather than requiring to specify executable and path separately, we just extract the executable file name on Windows, if necessary.

Usage:
```
ecm_generate_dbus_service_file(NAME org.kde.kded5
                               EXECUTABLE ${KDE_INSTALL_FULL_BINDIR}/kded5
                               SYSTEMD_SERVICE plasma-kded)
```

Test Plan:
* Was able to generate a kded service file
* Was able to generate a kded service file with `SystemdUnit`
* Verified that it moaned when executable wasn't an absolute path
* Untested on Windwos

Reviewers: #frameworks, davidedmundson, kossebau, kfunk, habacker

Subscribers: kde-frameworks-devel, kde-buildsystem

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D29051
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Summary:
It serves as a replacement for `kdbusaddons_generate_dbus_service_file`.

An application can be a DBus-activated service just fine without using KDBusAddons.
Moreover, this new module uses named arguments for future-proofing, and adds support for specifying a `SystemdService`.
It also cleans up the confusion on what the "path" is about: Rather than requiring to specify executable and path separately, we just extract the executable file name on Windows, if necessary.

Usage:
```
ecm_generate_dbus_service_file(NAME org.kde.kded5
                               EXECUTABLE ${KDE_INSTALL_FULL_BINDIR}/kded5
                               SYSTEMD_SERVICE plasma-kded)
```

Test Plan:
* Was able to generate a kded service file
* Was able to generate a kded service file with `SystemdUnit`
* Verified that it moaned when executable wasn't an absolute path
* Untested on Windwos

Reviewers: #frameworks, davidedmundson, kossebau, kfunk, habacker

Subscribers: kde-frameworks-devel, kde-buildsystem

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D29051
</pre>
</div>
</content>
</entry>
<entry>
<title>Introduce function ecm_install_configured_file</title>
<updated>2020-07-10T12:12:58+00:00</updated>
<author>
<name>David Edmundson</name>
<email>kde@davidedmundson.co.uk</email>
</author>
<published>2020-06-08T14:29:40+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=0ae520199d0e0523f4f0aa847b7567d72ae9553d'/>
<id>0ae520199d0e0523f4f0aa847b7567d72ae9553d</id>
<content type='text'>
Summary:
This, as the name suggests, configures a file and installs it.

It's not very complicated but it's a repeated pattern in plasma that
gets quite messy dealing with temporary files.

Test Plan: Used in a project

Reviewers: #build_system

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

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D28355
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Summary:
This, as the name suggests, configures a file and installs it.

It's not very complicated but it's a repeated pattern in plasma that
gets quite messy dealing with temporary files.

Test Plan: Used in a project

Reviewers: #build_system

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

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D28355
</pre>
</div>
</content>
</entry>
<entry>
<title>Add ECMGenerateExportHeader, for improved handling of deprecated API</title>
<updated>2019-10-10T20:50:03+00:00</updated>
<author>
<name>Friedrich W. H. Kossebau</name>
<email>kossebau@kde.org</email>
</author>
<published>2019-09-04T17:19:27+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=7b15c20dafc9133f93bbc65354ec3a36af168fd3'/>
<id>7b15c20dafc9133f93bbc65354ec3a36af168fd3</id>
<content type='text'>
Summary:
Generates additional macros in the export header which can be used for
fine-grained disabling of warnings &amp; visibility as well as excluding from
the build.

Reviewers: #frameworks, #build_system

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

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D23789
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Summary:
Generates additional macros in the export header which can be used for
fine-grained disabling of warnings &amp; visibility as well as excluding from
the build.

Reviewers: #frameworks, #build_system

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

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D23789
</pre>
</div>
</content>
</entry>
<entry>
<title>new module ECMSourceVersionControl</title>
<updated>2019-10-01T10:30:21+00:00</updated>
<author>
<name>Harald Sitter</name>
<email>sitter@kde.org</email>
</author>
<published>2019-09-23T14:00:59+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=f3f4893b5bd20a32dd48b147fdd243c3226a06f3'/>
<id>f3f4893b5bd20a32dd48b147fdd243c3226a06f3</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>Add ECMAddQtDesignerPlugin</title>
<updated>2019-08-05T17:16:45+00:00</updated>
<author>
<name>Friedrich W. H. Kossebau</name>
<email>kossebau@kde.org</email>
</author>
<published>2019-07-24T17:55:58+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=6709de184aa397b6b4f9f4d11d21cd8fce9d708c'/>
<id>6709de184aa397b6b4f9f4d11d21cd8fce9d708c</id>
<content type='text'>
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 &amp; 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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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 &amp; 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
</pre>
</div>
</content>
</entry>
<entry>
<title>API dox: add missing entries for some find-modules &amp; modules</title>
<updated>2019-01-07T23:35:39+00:00</updated>
<author>
<name>Friedrich W. H. Kossebau</name>
<email>kossebau@kde.org</email>
</author>
<published>2019-01-07T23:35:39+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=efdca205db4b230b068da480267e665e28b48423'/>
<id>efdca205db4b230b068da480267e665e28b48423</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Add ECMSetupQtPluginMacroNames</title>
<updated>2018-03-17T21:46:04+00:00</updated>
<author>
<name>Friedrich W. H. Kossebau</name>
<email>kossebau@kde.org</email>
</author>
<published>2018-02-22T17:23:00+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=36d42640576e92f8ddb3a66d35738f8fe75d1b8c'/>
<id>36d42640576e92f8ddb3a66d35738f8fe75d1b8c</id>
<content type='text'>
Summary:
This macro helps with setting up all the boilerplate CMake code needed
to instruct automoc about the custom C++ macros used to define Qt-style
plugin class instances.

Reviewers: #build_system, #frameworks, apol

Reviewed By: apol

Subscribers: apol

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D10749
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Summary:
This macro helps with setting up all the boilerplate CMake code needed
to instruct automoc about the custom C++ macros used to define Qt-style
plugin class instances.

Reviewers: #build_system, #frameworks, apol

Reviewed By: apol

Subscribers: apol

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D10749
</pre>
</div>
</content>
</entry>
</feed>
