And the .user files aren't project files. They're intended for local preferences, not global build settings.
The one thing Creator could add that would really make a difference would be for Creator to be able to identify build targets in the makefile other than just the default one and "clean" -- that way you could put all of the relevant logic in the makefile and simply select the appropriate target. You wouldn't be the first user I've talked to that would find this behavior useful -- one of the developers of Leges Motus has expressed that this was the one shortcoming that kept Creator from being suitable for that project. /s/ Adam On Fri, Sep 17, 2010 at 3:35 PM, Bryce Schober <bryce.scho...@gmail.com> wrote: > Well, I suppose it is a bit of a collision between the deficiencies of our > Makefiles and Qt Creator... but different build and run modes are nice to > remember in a project file. And when they can be reasonably expressed, > depending on relative paths or environmental variables to abstract away the > user-specificity, then of course you'd want them to be shared. If for no > other reason than that it's a pain for even a single user to copy them > around when they're maintaining multiple sandboxes. > > On Fri, Sep 17, 2010 at 1:02 PM, Coda Highland <c...@bobandgeorge.com> > wrote: >> >> You know, I have to ask why you feel the need to use a generic project >> in the first place if you're just going to tie the build system to >> Creator. Usually people want to use bare Makefiles in order to be able >> to customize the build process in the makefile itself -- and certainly >> makefiles are expressive enough to do everything you could possibly >> want it to do. >> >> What part of your use case isn't accommodated here? What is it that >> you're trying to do that can't be done in the makefile itself? >> >> /s/ Adam >> >> On Fri, Sep 17, 2010 at 1:33 PM, Bryce Schober <bryce.scho...@gmail.com> >> 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. This is going to completely kill my usage >> > scenario if it continues. 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. >> > On Fri, Sep 17, 2010 at 7:28 AM, Coda Highland <c...@bobandgeorge.com> >> > wrote: >> >> >> >> A properly configured .pro file should be able to satisfy your needs; >> >> Qt is designed to be able to handle building apps at the command line >> >> without needing to use Creator at all, and that doesn't use the >> >> .pro.user file, so you should be able to put all of the necessary >> >> configuration in the .pro file. >> >> >> >> /s/ Adam >> >> >> >> On Fri, Sep 17, 2010 at 5:17 AM, anshul mehta <ansme...@gmail.com> >> >> wrote: >> >> > I understand that the .pro.user should be shared between users but >> >> > the >> >> > build >> >> > and run settings are stored in pro.user. I want a feature in >> >> > qtcreator >> >> > that >> >> > allows build/run settings in terms of and environmental that any user >> >> > can >> >> > setup appropriately and build/run settings can be made part of .pro >> >> > so >> >> > that >> >> > they can be shared. >> >> > ie. The build directory could be something like $BLDDIR/projectname >> >> > and >> >> > user >> >> > can setup $BLDDIR to desired value before starting Qt Creator and >> >> > similarly >> >> > executable to be run in the run settings would be specified as >> >> > $BLDDIR/projectname/executablename. >> >> > >> >> > Regards >> >> > Anshul >> >> > On Fri, Sep 17, 2010 at 3:31 PM, Tobias Hunger >> >> > <tobias.hun...@nokia.com> >> >> > wrote: >> >> >> >> >> >> On 16.09.2010 20:46, ext Bryce Schober wrote: >> >> >> > Since switching to the head nightlies, my .creator.user files >> >> >> > (Generic >> >> >> > projects) now have a ProjectExplorer.Project.Updater.EnvironmentId >> >> >> > variable that is changing when nothing else is. >> >> >> >> >> >> The ID is used to check which Creator last opened the file. This is >> >> >> to >> >> >> warn about people using the same .user-file in different >> >> >> environments >> >> >> (OSes, computers, etc.). >> >> >> >> >> >> > This is going to pretty >> >> >> > annoying if it continues to clutter my check-ins. >> >> >> >> >> >> In addition to cluttering up your checkins it should also trigger >> >> >> warnings about sharing a .user-file when loading the project. >> >> >> >> >> >> Please do not check in the .user file. It is highly dependent on the >> >> >> environment and can not get savely shared! >> >> >> >> >> >> Best Regards, >> >> >> Tobias >> >> >> >> >> >> PS: Having an unique ID is a privacy concern, so I want to point out >> >> >> that we do *NOT* use the ID anywhere but in the .user-file and that >> >> >> this >> >> >> is the only UUID we generate. We have thought hard on how to avoid >> >> >> generating one in the first place. Unfortunately this seems to be >> >> >> the >> >> >> only robust way to warn about sharing .user-files. >> >> >> >> >> >> -- >> >> >> 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 >> >> > >> >> > >> >> >> >> _______________________________________________ >> >> Qt-creator mailing list >> >> Qt-creator@trolltech.com >> >> http://lists.trolltech.com/mailman/listinfo/qt-creator >> > >> > >> > >> > -- >> > 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 > > > > -- > 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
