cmake and auto-generated sources

René J.V. Bertin rjvbertin at
Fri Sep 21 13:46:53 BST 2018


I've asked this before on a KDE list, so apologies if you've seen the question already.

Is there a way to generate all the autogen stuff after running cmake? Often, if you import a fresh source tree of a cmake-based project into an IDE like kdevelop, cmake will be run to figure out the project content and dependencies, where headers are etc. Afterwards most parsing will thus succeed, but not that which requires headers and other stuff that is generated during a build (moc files, translated .ui files, ...). That is quite annoying for large projects.
I think qmake-based projects generate those things as the first step during a make, while cmake-based projects generate them on an as-needed basis.

Presuming that qmake-based projects have a dedicated target that could be built in isolation on user request, would it be possible to achieve this with cmake as well, without need to patch cmake itself?

On a related topic: it would be great if those auto-generated files didn't use relative include paths. That can break the build if you access a build directory during a make via a path containing symlinks on a system that does not normalise paths.


More information about the KDevelop mailing list