kconfig.git/autotests/kconfig_compiler, branch v5.50.0 hurd kconfig.git KConfigCompiler_Test: Update test_signal.h.ref to follow the generated file 2018-05-16T06:39:11+00:00 Maximiliano Curia maxy@gnuservers.com.ar 2018-05-15T09:31:06+00:00 c1fa17e99ad98763261886906d977d516bfffe1b Summary: Since "Use override" (3985f2a0) kconfig_compiler.cpp generates usrSave with override instead of Q_DECL_OVERRIDE. This causes the KConfigCompiler_Test to fail [1], as the reference file of the test was not updated. [1]: https://build.kde.org/job/Frameworks%20kconfig%20kf5-qt5%20SUSEQt5.10/32/ Reviewers: #frameworks, mlaurent Reviewed By: mlaurent Subscribers: kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D12892 
Summary:
Since "Use override" (3985f2a0) kconfig_compiler.cpp
generates usrSave with override instead of Q_DECL_OVERRIDE. This causes
the KConfigCompiler_Test to fail [1], as the reference file of the test
was not updated.

[1]: https://build.kde.org/job/Frameworks%20kconfig%20kf5-qt5%20SUSEQt5.10/32/

Reviewers: #frameworks, mlaurent

Reviewed By: mlaurent

Subscribers: kde-frameworks-devel

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D12892
Fix autotest 2018-04-06T11:21:23+00:00 Laurent Montel montel@kde.org 2018-04-06T11:21:23+00:00 9c8c3a7d4c3eb9a7371179244848a575b46c7212 






Remove not necessary QtCore and co
2018-03-11T12:36:48+00:00

Laurent Montel
montel@kde.org

2018-03-11T12:36:48+00:00

610fe76bac95b7eb9f1fa44d05e4b4040707304f












Fix some clazy warning
2017-11-30T12:36:08+00:00

Montel Laurent
montel@kde.org

2017-11-30T12:36:08+00:00

ee2b394599ffe1242e3b7ae7d40b3469485dcd97












tests: use QIODevice::Text in kconfigcompiler_test
2017-05-25T22:57:35+00:00

Pino Toscano
pino@kde.org

2017-05-25T22:57:35+00:00

1fad6902629191558e53ea9b58a8a67a0bfc9440

This way, different newline endings in OSes are handled as \n when
reading, and thus fixing the comparison on non-\n OSes.





This way, different newline endings in OSes are handled as \n when
reading, and thus fixing the comparison on non-\n OSes.







tests: use right QProcess API in kconfigcompiler_test
2017-05-25T22:40:20+00:00

Pino Toscano
pino@kde.org

2017-05-25T22:40:20+00:00

97ec146bd109109ac11e3c573625b47bfa4fd4ff

Use the QProcess::start() variant with explicit (empty, in this case)
arguments, so the program string is not parsed as shell command, thus
preserving paths with spaces as such.





Use the QProcess::start() variant with explicit (empty, in this case)
arguments, so the program string is not parsed as shell command, thus
preserving paths with spaces as such.







Prefer nullptr over Q_NULLPTR
2017-01-16T17:17:34+00:00

Kevin Funk
kfunk@kde.org

2017-01-16T17:17:34+00:00

2034e3ce7593f04d251b634bfe2d71b30f15ea3a












This should now use nullptr
2017-01-08T16:23:38+00:00

David Faure
faure@kde.org

2017-01-08T16:23:38+00:00

d3de5a2a79d2786207d0cfbbc9828e00dabd148d












Generate an instance with KSharedConfig::Ptr for singleton and arg
2017-01-06T08:52:45+00:00

Martin Gräßlin
mgraesslin@kde.org

2016-11-16T13:59:28+00:00

e0db2422362260a2fea3a8e1de4c64011d2f183d

Summary:
In case a kcfg with arg="true" was used and singleton the static
instance method only accepted a QString config name. This made it
impossible to combine a singleton config with an already existing and
open KSharedConfig::Ptr.

With this change an overloaded instance method is added which takes a
KSharedConfig::Ptr as argument. The private ctor, though, only takes a
KSharedConfig::Ptr and the instance method taking a QString argument
uses KSharedConfig::openConfig on the config file name.

The change is source-incompatible in the following situation:
* kcfgfile arg="true"
* Singleton = true
* Inherits is specified

In this situation the previous revision created an instance method with
a QString argument and passed that to the parent constructor. This is
not in accordance with the documentation. Any user of this behavior was
relying on a bug. With this change now the call to the parent
constructor carries a KSharedConfigPtr.

Test Plan:
kconfigcompiler tests still pass and a config with singleton
and arg="true" generates the code as I need it

Reviewers: #frameworks, dfaure, mdawson

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





Summary:
In case a kcfg with arg="true" was used and singleton the static
instance method only accepted a QString config name. This made it
impossible to combine a singleton config with an already existing and
open KSharedConfig::Ptr.

With this change an overloaded instance method is added which takes a
KSharedConfig::Ptr as argument. The private ctor, though, only takes a
KSharedConfig::Ptr and the instance method taking a QString argument
uses KSharedConfig::openConfig on the config file name.

The change is source-incompatible in the following situation:
* kcfgfile arg="true"
* Singleton = true
* Inherits is specified

In this situation the previous revision created an instance method with
a QString argument and passed that to the parent constructor. This is
not in accordance with the documentation. Any user of this behavior was
relying on a bug. With this change now the call to the parent
constructor carries a KSharedConfigPtr.

Test Plan:
kconfigcompiler tests still pass and a config with singleton
and arg="true" generates the code as I need it

Reviewers: #frameworks, dfaure, mdawson

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







kconfig_compiler: Use nullptr in generated code
2016-12-16T11:45:40+00:00

Kevin Funk
kfunk@kde.org

2016-12-16T11:35:32+00:00

e6c88f67e2cb660e049a478a8d55220c235aa9c5

Reviewers: #frameworks, davidedmundson

Reviewed By: davidedmundson

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





Reviewers: #frameworks, davidedmundson

Reviewed By: davidedmundson

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