kconfig.git/autotests/kconfig_compiler, branch v5.8.0 hurd kconfig.git Replace nullptr with Q_NULLPTR. 2014-09-18T15:37:08+00:00 Nicolás Alvarez nicolas.alvarez@gmail.com 2014-09-18T15:37:08+00:00 a26008ef6773e3d473fccc8bc8f8aaf902a49121 gcc 4.5 doesn't have nullptr. 
gcc 4.5 doesn't have nullptr.
Simple Cleanups 2014-06-12T22:14:16+00:00 Thomas Braxton kde.braxton@gmail.com 2014-06-11T13:40:44+00:00 ac6703215ba5e152379173ba503f5ba3bd7e8a85 - use Q_NULLPTR instead of 0 or NULL - simplify some foreach loops - use QStringLiteral in a few places - added a few consts REVIEW: 118666 
- use Q_NULLPTR instead of 0 or NULL
- simplify some foreach loops
- use QStringLiteral in a few places
- added a few consts

REVIEW: 118666
Revert "adapt to ECMAddTests change" 2014-05-10T13:53:00+00:00 Alex Richardson arichardson.kde@gmail.com 2014-05-10T13:53:00+00:00 08c778f7cbc4aa76c2aff51bec57aceab44b3ae3 This reverts commit 88c9a9664e99b639df4cde2be22dbe44df228879. 
This reverts commit 88c9a9664e99b639df4cde2be22dbe44df228879.
adapt to ECMAddTests change 2014-05-09T22:12:25+00:00 Alex Richardson arichardson.kde@gmail.com 2014-05-09T22:12:25+00:00 88c9a9664e99b639df4cde2be22dbe44df228879 






Generate MOC files for kconfig_compiler outputs in tests.
2014-05-07T17:43:36+00:00

Matthew Dawson
matthew@mjdsystems.ca

2014-05-07T17:43:36+00:00

c61df3e92947592a99c71da121356eb1600fb161

The MOC files for generated output from kconfig_compiler are not automatically
generated.  Re-add the code that does this, fixing the build.

I'm assuming this isn't an issue on Windows, as I don't have any machines to
test on.  Please let me know if this isn't the case.

CC: arichardson.kde@gmail.com





The MOC files for generated output from kconfig_compiler are not automatically
generated.  Re-add the code that does this, fixing the build.

I'm assuming this isn't an issue on Windows, as I don't have any machines to
test on.  Please let me know if this isn't the case.

CC: arichardson.kde@gmail.com







fix kconfig_compiler test on windows
2014-05-07T13:59:57+00:00

Alex Richardson
arichardson.kde@gmail.com

2014-05-07T13:59:57+00:00

69000672e974ad5444b5d6df5187db13eab279de

We have to generate the files in the same directory as the test executables
otherwise QFINDTESTDATA will fail





We have to generate the files in the same directory as the test executables
otherwise QFINDTESTDATA will fail







Use ecm_add_test(s) instead of own macro
2014-05-06T23:56:13+00:00

Alex Richardson
arichardson.kde@gmail.com

2014-05-06T23:56:13+00:00

a3d6957ec5f63b3d668a57b2ada13a3ce9715848

This also fixes running 'nmake test' on Windows.





This also fixes running 'nmake test' on Windows.







Stop re-loading values inside KCoreConfigSkeleton::save().
2014-03-28T16:08:05+00:00

Matthew Dawson
matthew@mjdsystems.ca

2014-03-28T15:59:51+00:00

4846b50aea0bc2262238963a85ab3556c22412e4

The extra load of values in KCoreConfigSkeleton is not documented anywhere
that it happens, and in normal circumstances re-loading new values isn't
expecterd during a save operation.

Update various mentions of readConfig/writeConfig to read/save.

Update documentation to match the new names of functions.

Rename writeConfig() to save() and usrWriteConfig() to usrSave()

Rename functions to match the new naming conventions.  Also create old deprecated
instances of both functions to ensure that old code continues to operate
correctly.  Also make save() non-virtual, for the same reasons read() is
now non-virtual.

Rename usrReadConfig to usrRead, to be consistent with the new name for readConfig.

Rename usrReadConfig to usrRead, and mark the former as deprecated.  To maintain
compatibility, usrRead still calls usrReadConfig in its default implementation.
usrReadConfig remains empty.

REVIEW: 117010





The extra load of values in KCoreConfigSkeleton is not documented anywhere
that it happens, and in normal circumstances re-loading new values isn't
expecterd during a save operation.

Update various mentions of readConfig/writeConfig to read/save.

Update documentation to match the new names of functions.

Rename writeConfig() to save() and usrWriteConfig() to usrSave()

Rename functions to match the new naming conventions.  Also create old deprecated
instances of both functions to ensure that old code continues to operate
correctly.  Also make save() non-virtual, for the same reasons read() is
now non-virtual.

Rename usrReadConfig to usrRead, to be consistent with the new name for readConfig.

Rename usrReadConfig to usrRead, and mark the former as deprecated.  To maintain
compatibility, usrRead still calls usrReadConfig in its default implementation.
usrReadConfig remains empty.

REVIEW: 117010







Rename the kconfig_compiler_kf5 target to kconfig_compiler
2014-03-24T11:49:49+00:00

Alex Merry
alex.merry@kde.org

2014-03-23T14:38:14+00:00

892e693f616297a91835d3d79353926b96bd1201

Just because the executable has the "_kf5" suffix, that does not mean
the target should have it.  This is ugly API, and will be unnecessary
porting effort for KF6.

REVIEW: 116995





Just because the executable has the "_kf5" suffix, that does not mean
the target should have it.  This is ugly API, and will be unnecessary
porting effort for KF6.

REVIEW: 116995







Add KCoreConfigSkeleton::read() which doesn't call reparseConfiguration.
2014-03-23T22:00:03+00:00

David Faure
faure@kde.org

2014-03-16T22:30:59+00:00

c1980dbc51c9aa2770d09850e69529ea2211924b

Call it from generated singletons, since the constructor creates
a KConfig from a filename, which already loads from disk.
This removes the need for using DelayedParsing.

REVIEW: 116845





Call it from generated singletons, since the constructor creates
a KConfig from a filename, which already loads from disk.
This removes the need for using DelayedParsing.

REVIEW: 116845