On Thursday 15 March 2012 22:19:43 Mathias Hasselmann wrote: > Excuse my ignorance if this option was discussed and dismissed already, > or if just entirely miss the point... > > But how about choosing "Import Project" -> "Import Existing Project" > from the project wizard? Sure, adding and removing files in such an > imported Makefile project is painful, so in the long run you might want > to convert the project. But for getting started, for understanding the > project structure, for finishing some initial tasks, this approach > should be good enough.
And this is what we do at my work. We "Import(ed) Existing project", so that the make commands are available for free (and this gives us priceless compiling error parsing towards the "Issues" pane). And we just added a target (called qtcreator_config) to our makefile that generates "manually" (by some nicely crafted grep(1)s and find(1)s) the myproject.files and myproject.includes files (we even add library includes to the .includes file). And with the latest qtcreator (master?), each time we add/remove a file to the project we just make qtcreator_config and QtCreator automatically rereads the thusly refreshed .files and .includes. Pure joy . Hope this helps -- Cristian Tibirna KDE developer .. [email protected] .. http://www.kde.org _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
