I have seen this problem more than a few times and with a 45 minute build time
for our project it is starting to get in the way. Our project is CMake based (I
am using CMake 3.8 or 3.9 depending on the particular workstation that I am
using at the time) and also uses Qt 5.9.1 64 bit. All the code is C++. What
will happen is that I load the project, QtCreator properly configures for the
build (Debug) and I build the project successfully. I quit QtCreator. Relaunch
QtCreator and when I click Debug for our application QtCreator will pretty much
rebuild the entire project. NOTHING changed between when I last built, quit
QtCreator and relaunched QtCreator. I use ninja as the build tool.
Just to sanity check our CMake code I dropped out to a command line and went
into a clean build directory, ran CMake, built, ran cmake again and built and
the second build did nothing as nothing needed to be done. I can replicate this
on a semi regular basis but I can't pin down what is happening inside of
QtCreator that forces something to be regenerated on the CMake side. Our CMake
codes do generate some header files which I think is somehow interacting with
QtCreator's cmake support to somehow regenerate those files when the probably
should not have been generated?
Thoughts on this is much appreciated.
--
Michael Jackson | Owner, President
BlueQuartz Software
[e] [email protected]
[w] www.bluequartz.net
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator
