kconfig.git/autotests, branch v4.98.0

Stop re-loading values inside KCoreConfigSkeleton::save().

2014-03-28T16:08:05+00:00

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

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

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

Normalize vars to avoid odd bugs: QT_REQUIRED_VERSION => REQUIRED_QT_VERSION

2014-03-13T10:01:07+00:00

kconfigtest: write everything into a subdirectory

2014-03-05T10:32:59+00:00

This test keeps deleting the whole ~/.qttest directory. By moving all
data into a subdirectory it is now possible to run multiple tests that
use kconfig in parallel.

REVIEW: 115875

Make kconfig_compiler signals actually useful + add unit test

2014-02-20T17:14:24+00:00

Previously the classes generated by kconfig_compiler would only emit
the defined signals when using the setters provided by that class.
However, when using e.g. KConfigDialog which uses
KConfigSkeletonItem::setProperty() to change the items no signal was
generated.
This patch fixes this by using a wrapper KConfigSkeletonItem
subclass that calls a private itemChanged() method in the generated
class which updates the set of changed properties. As soon as the item
is saved (usrWriteConfig() in the generated class is called) the signal
will be emitted

REVIEW: 115635
REVIEW: 115634

Print the diff to stdout on comparison failure

2014-02-19T07:00:10+00:00

Previously the output of diff -u was written to a file when the
generated file did not match the expectations. Having the output printed
to stdout makes it easier to see the exact error without having to know
that a diff exists in a certain file somewhere in the build directory.

REVIEW: 115832

Improve dependency specifications.

2014-01-15T05:52:51+00:00

QtTest and QtConcurrent are only required for autotests, so no need
to find them unconditionally.
QtWidgets is not actually used - QtGui is instead.

REVIEW: 114962

Make Qt5Test an optional dependency

2014-01-13T16:31:38+00:00

It is only needed for building the autotests

further rename of kconfig_compiler to kconfig_compiler_kf5

2014-01-09T18:12:58+00:00