aboutsummaryrefslogtreecommitdiff
path: root/autotests/kconfig_compiler/CMakeLists.txt
AgeCommit message (Collapse)Author
2014-05-10Revert "adapt to ECMAddTests change"Alex Richardson
This reverts commit 88c9a9664e99b639df4cde2be22dbe44df228879.
2014-05-10adapt to ECMAddTests changeAlex Richardson
2014-05-07Generate MOC files for kconfig_compiler outputs in tests.Matthew Dawson
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
2014-05-07fix kconfig_compiler test on windowsAlex Richardson
We have to generate the files in the same directory as the test executables otherwise QFINDTESTDATA will fail
2014-05-07Use ecm_add_test(s) instead of own macroAlex Richardson
This also fixes running 'nmake test' on Windows.
2014-03-24Rename the kconfig_compiler_kf5 target to kconfig_compilerAlex Merry
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
2014-02-20Make kconfig_compiler signals actually useful + add unit testAlex Richardson
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
2014-01-09rename kconfig_compiler to kconfig_compiler_kf5Jonathan Riddell
2013-12-18Move kconfig code to the root directory.Jenkins CI