kconfig.git/autotests/kconfig_compiler, branch v5.92.0 hurd kconfig.git KConfigCompiler: support ItemAccessors=true with signalling items 2022-02-18T22:24:41+00:00 Friedrich W. H. Kossebau kossebau@kde.org 2022-02-09T12:55:14+00:00 3583e0d2ed951365777122ae4b2ab4641125f756 






Make singleton teardown work with Qt6 as well
2022-01-22T11:35:06+00:00

Volker Krause
vkrause@kde.org

2022-01-21T15:01:35+00:00

41d37407e80f5ccd110cf303c20a181f95fa7e73

In Qt6 the Q_GLOBAL_STATIC will already report to be null while it is in
the process of being deleted, we therefore cannot access it anymore from
destruction code path as we did before.

This problem is hit for example by the Breeze style, making all 6 based
widgets applications crash on exit without this.





In Qt6 the Q_GLOBAL_STATIC will already report to be null while it is in
the process of being deleted, we therefore cannot access it anymore from
destruction code path as we did before.

This problem is hit for example by the Breeze style, making all 6 based
widgets applications crash on exit without this.







WIP: Change the build system to enable building with Qt 6
2021-12-16T18:05:02+00:00

Ahmad Samir
a.samirh78@gmail.com

2021-12-03T20:33:28+00:00

10c4a4b4bdfdd468e52ae0fbbf84c77b64df2f8f

This was built with:
-DQT_MAJOR_VERSION=6 \
-DEXCLUDE_DEPRECATED_BEFORE_AND_AT=5.90.0 \
-DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x055a00

Move the include(KDEInstallDirs) call before the first find_package(Qt*,
the former is what auto-detects the Qt version, and defaults to 5. This is
needed to be able to build against Qt5 by default.

All unit tests still pass.





This was built with:
-DQT_MAJOR_VERSION=6 \
-DEXCLUDE_DEPRECATED_BEFORE_AND_AT=5.90.0 \
-DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x055a00

Move the include(KDEInstallDirs) call before the first find_package(Qt*,
the former is what auto-detects the Qt version, and defaults to 5. This is
needed to be able to build against Qt5 by default.

All unit tests still pass.







Add the enum group test to the kconfigcompiler_test
2021-11-23T14:36:57+00:00

Tomaz Canabrava
tcanabrava@kde.org

2021-11-17T16:29:50+00:00

0d742a8daf55311f048a6959d6641a9a95a2eb04

Making sure that it runs and not segfaults





Making sure that it runs and not segfaults







Add a proper test for the enumms within groups
2021-11-23T14:36:57+00:00

Tomaz Canabrava
tcanabrava@kde.org

2021-11-17T16:16:21+00:00

148ea287a0a7b9de96dc299db56254c65aec3385












Add missing changes
2021-11-23T14:36:57+00:00

Tomaz Canabrava
tcanabraba@kde.org

2021-10-21T08:51:16+00:00

829cc003ee4f21e91d806a2e2a353ae709ab999f












unbreak kconfig with enums, mutators and properties.
2021-11-23T14:36:57+00:00

Tomaz Canabrava
tcanabraba@kde.org

2021-10-21T08:30:49+00:00

e16ab18ed8e588ea14b219d5738e9dc9f5fc5cf6












Demonstrate build failure with kconfig generated code
2021-11-23T14:36:57+00:00

Tomaz Canabrava
tcanabraba@kde.org

2021-10-17T10:10:36+00:00

10dee5131d940316cf0136516013e2ed3aeee012












Allow KConfigXT to use KSharedConfig::openStateConfig
2021-09-19T05:50:10+00:00

Alexander Lohnau
alexander.lohnau@gmx.de

2021-09-14T05:30:32+00:00

0b0a4464fb3d1145eb612b1ab7edacfa9581c8c9

Otherwise we force consumers to use the config location for state data,
which is what we are trying to avoid.

Task: https://phabricator.kde.org/T12549





Otherwise we force consumers to use the config location for state data,
which is what we are trying to avoid.

Task: https://phabricator.kde.org/T12549







kconfig_compiler: add override to generated destructors
2021-04-05T12:23:47+00:00

David Faure
faure@kde.org

2021-04-04T11:52:53+00:00

27f1d268d9f960b72081b74b0688fdc5fc212ff5

This fixes the clang warning
globalsettings_kmail.h:58:5: warning: '~GlobalSettingsBase' overrides a destructor but is not marked 'override' [-Wsuggest-destructor-override]





This fixes the clang warning
globalsettings_kmail.h:58:5: warning: '~GlobalSettingsBase' overrides a destructor but is not marked 'override' [-Wsuggest-destructor-override]