OSX/CI: kig fails to build on branch master (when using Qt version below 5.4)

[Marko Käning]

Hi folks,

I just wonder why it is already _required_ to have the latest Qt version for kig:

---
Building CXX object CMakeFiles/kigpart.dir/scripting/script_mode.cc.o
/Users/marko/WC/KDECI-builds/kf5-qt5/kig/kig/kig_part.cpp:1111:88: error: no member named 'AppDataLocation' in 'QStandardPaths'; did you mean 'DataLocation'?
  const QDir writeableDataLocation ( QStandardPaths::writableLocation( QStandardPaths::AppDataLocation ) );
                                                                       ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~
                                                                                       DataLocation
/opt/kde/install/darwin/mavericks/clang/kf5-qt5/qt5/inst/include/QtCore/qstandardpaths.h:66:9: note: 'DataLocation' declared here
        DataLocation,
        ^
/Users/marko/WC/KDECI-builds/kf5-qt5/kig/kig/kig_part.cpp:1131:88: error: no member named 'AppDataLocation' in 'QStandardPaths'; did you mean 'DataLocation'?
  const QDir writeableDataLocation ( QStandardPaths::writableLocation( QStandardPaths::AppDataLocation ) );
                                                                       ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~
                                                                                       DataLocation
/opt/kde/install/darwin/mavericks/clang/kf5-qt5/qt5/inst/include/QtCore/qstandardpaths.h:66:9: note: 'DataLocation' declared here
        DataLocation,
        ^
[100%] Building CXX object CMakeFiles/kigpart.dir/kigpart_automoc.cpp.o
...
1 warning and 2 errors generated.
make[2]: *** [CMakeFiles/kigpart.dir/kig/kig_part.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
---

just because of QSP::AppDataLocation... Is that really necessary?


I know that the projects dependencies of Jenkins already define Qt 5.4.1 as a must for the master branch, but
still I wonder about it, as kig seems to be the first application which accesses its data files like this,
instead of still making use of QSP::DataLocation.

Well, I could imagine that quite a wave of such changes is going to come for all projects, but I wasn’t expecting
it that soon. ;-)

Greets,
Marko