You'll love KDE. It has always been one of my favorites. Plus the close integration with Qt makes it even better.

I've used gnome a lot lately too though. A lot of people hated the new Gnome 3 changes, but I didn't mind them.

It's not as full featured or nice as KDE though. But sometimes KDE acts a little weird due to some of the opengl stuff.

And if all else fails, you can try arch. It isn't an easy to set up distribution but it's cutting edge. So everything is the newest of the new. Makes for a lot cooler of a linux experience in my opinion. :)

Setup is not for the faint of heart though. There's no GUI, and I usually use a linux boot disk to get it going (one from sysreccd).

@koahnig
Thanks , it worked

@Wieland: Thanks for the heads-up, I upvoted and subscribed for that bug report.

@Stefan-Monov76

Since I am not using qml I am not sure what requirements there are.

I am working with C++ where you distinguish between source (.cpp) and header (.h included in *.cpp) files. The compiler requires basically only the *.cpp files for compiling. The header files are found through INCLUDEPATH or also other means settings.

Being lazy you could think of just added *.cpp files to your .pro. However, this is a really bad idea, because Qt creator cannot detect that those have changed respectively there might be no dependency on includes in your make.

Sometimes you simply forget an include to add to .pro and I have noticed that those includes are searched.

That it is working for you now, may have something to do with a rerun of qmake. Just wait and see, if teh problem comes back. Eventually for some reason qmake was not triggered.

Note: Since I am not working with qml at all, I am not sure, if you are actually using qmake. Checkout if you actually have "Run qmake" under "Buld" available.