>>> 1) I have a session with about 20 projects loaded. It would be very >>> helpful if there was a way to set the tool chain for all of the >>> projects at once rather than having to set them individually. > It should select the same defaults that were used previously for qmake > based projects. > > Generic Makefile based projects are not really covered well. I'll check > whether I can update the code to select a reasonable toolchain (MinGW on > windows or GCC everywhere else), if one is auto detected. That is pretty > much what we had assumed before. Would that help? I don't think that would do much for us. We don't really play nice with, well anyone. We sometimes allow our developers to select the compiler and sometimes we force the compiler depending on which platform is being built.
The only thing this appears to affect for generic make projects is the compiler output parsing. Somehow that worked pretty well in 2.1 so perhaps there is a way to revert to that behavior for generic make projects. That sounds a little haphazard so you might want to leave it alone. >>> 2) It also seems like for our gmake projects the tool chain selection >>> doesn't really have any effect on which compiler or flags are used to >>> compile a project. Is there something we can do differently in our >>> make files to listen to this setting? > The tool chain selection does not really effect the build settings yet, > that is true. I'll improve this post-2.2 for the qmake projects (and > maybe CMAke ones, too). > > For generic projetcs there is too little known to really make the tool > chain data available to the build system. We could maybe set CC or CXX > environment variables and hope for the best... which will probably > confuse some projects and get ignored by others. Or maybe we should just > not expose the data at all. Tough call on this one for generic projects. For my projects, setting CC and CXX would be good enough (except those times when the make system appears to know best) but I can see how that might cause trouble for more general cases. > PS: You can of course always write a script to update the .user files. > They are XML, so that should not be too hard to do with your scripting > language of choice. The files tend to be one item per line, so maybe you > can even get by without a actual XML parser;-) True enough. A little sed magic might just do the trick! _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
