Creator's session system and the .user file schema are deeply flawed. This has been discussed several times on the list. The best thing you can do is keep as many of your project's settings inside the build system master file(s) (the .pro files for qmake, the CMakeLists.txts for cmake etc). Ignore the 'Project' tab completely.
With qmake it's actually possible to create project 'solutions' with sub projects, dependencies, global includes and build settings all inside the .pro file. The current wizards do not demonstrate any of this however so you'll have to research it on your own. I'm actually planning to write some tutorials on qmake as Creator has forced me to become quite knowledgeable in it :) Creator still has a long, long way to compete with MSVC or XCode in regard to simple project management, even at version 2.0. The priority at Nokia is to push QML and mobile-platform support as unique features of Creator as opposed to addressing is fundamental shortcomings as an IDE. When I attended the 2009 Qt Dev days it was repeatedly emphasised by Nokia that Creator was considered an supplement to 'proper' desktop development tools only. It has even been stated on this list by Qt employees that Creator is an editor, not an IDE. That said it is a great editor and if you stick with it you'll learn a lot more about your platform, build tools and software development than just using the wizards to create projects in MSVC. I think it's wonderful that with qmake, you can compile a 'real' application with so few settings in a text file and it sure beats writing makefiles. It has the potential to be a wonderful teaching tool for c/c++ and Qt. On 11 Mar 2010, at 23:36, Bryce Schober wrote: > I've gone through the process of figuring out how to use Qt Creator with our > strange project tree and Makefile structure (even semi-auto-updating the > files list). The only little thing left in my way (I'm so close!!!) is Qt > Creator's behavior of "disallowing" an empty build directory spec. I put that > in quotes, because it actually builds just fine with an empty builddir spec, > since it defaults to the project file's directory. But it saves that abs-path > default back into the *.creator.user file, which makes it impossible to > easily check it into source control and share the project settings with other > users, or even just other sandboxes for the same user. > > -- > Bryce Schober > _______________________________________________ > Qt-creator mailing list > Qt-creator@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-creator _______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
