Without wanting to say anything on behalf of others, let me just give my personal 2 cents. We develop based on CMake projects with a group of people and with shadow builds. Most of us use Qt Creator, this works quite well. The only thing that is a hassle is the .user file and the settings therein.
When we quickly want to hand over a project, we pack the root directory of the source tree, i.e., the one that also holds the CMakeLists.txt. Unfortunately, also the CMakeLists.txt.user file is located here, and hence it gets distributed. This is a pain, because the build-directory and run-working-directory could (so far) not be defined relative to a user-defined location and/or an environment variable. Fortunately, this has been fixed quickly after I reported this (http://bugreports.qt.nokia.com/browse/QTCREATORBUG-2377), thanks for that. >From the discussion above, I have learned that we should just not distribute the .user file. >From my perspective, it would be preferable to have the build settings and run settings removed from the .user file and store these in separate files like you suggested, which then can be saved in the source tree. I would suggest then that the .user file is stored in the build directory, not in the source tree. I will consider making patches if this is something that people would like to have. However, I am not familiar with the internals of Qt Creator so far, so it would take me a while and I'm not sure about the quality... Regards, Theo. 2010/9/20 Tobias Hunger <tobias.hun...@nokia.com>: > On 17.09.2010 20:33, ext Bryce Schober wrote: >> I'm extremely disappointed. I'm using Qt Creator exclusively for generic >> Makefile development. It has had its warts for that purpose, but this >> makes it much worse, because now there is no way for me to share build >> configurations with others. > > What could be done to improve your use case? > > So you just want a set of additional make targets to be (pre-)defined > for users as well as a list of things that can be run? Would it help if > we added some more files to make those known to creator? > >> This is going to completely kill my usage >> scenario if it continues. > > What is you usage scenario? > > From our point of view we are not "continuing", but just made our users > aware about something that has never worked before. We had lots of > complaints about trouble due to sharing a .user-file. Since there is > little we can do to make it share better we had to at least provide a > warning. > >> Maybe this is just one of those "you're not >> our customer" situations, but it's pretty disappointing. Now generic >> project support is even more of an orphan than it was. > > We are willing to accept merge requests to improve any part of creator > including the different build system integrations. Unfortunately we do > not have much time ourselves to improve the generic project support:-( > > Some of us are using the generic project to contribute to open source > projects that are not qmake based, so it is regularly excersied and > tested and we do make sure to not break those use cases. > > Best Regards, > Tobias > > -- > Tobias Hunger > Software Engineer > Nokia, Qt Development Frameworks > > Nokia gate5 GmbH > Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany > Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B > Umsatzsteueridentifikationsnummer: DE 812 845 193 > Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori > _______________________________________________ > 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
