On Wed, Aug 26, 2009 at 3:49 PM, Kai Koehne <[email protected]> wrote:
> ext Danny Price wrote: > > > > > > On Wed, Aug 26, 2009 at 1:58 PM, Vladimir <[email protected] > > <mailto:[email protected]>> wrote: > > > > Thanks a lot, Danny! > > > > It looks like it works from first sight, but: > > 1) .user file is really huge and contains a lot of strange > information > > like my environment variables and absolute paths. So my coworkers > > probably would be unable to checkout the tree and start working. > > > > > > Yes that's why they not suitable for SVN. I'm sure the Trolls have a > > solution in the works :) > > I feel like I have to defend the current approach here. The .user files > are named .user because they are user specific - that is, they are not > meant to be shared between users! The very same is true for the session > files. I would agree with you if it were not for the fact that Creator persists project-specific build settings and dependencies (the OP's question) in .user files and sessions. A session is Creator's version of a VisualStudio solution. Without it you lose that information. The only option is to embed as much as possible into .pro files but as I said earlier, Creator handles subdirs as aggregates rather than project hierachies. If it were only used for things like color schemes and keyboard bindings then you would have a point. > > The idea behind this is that QtCreator is (primarily) an editor, not a > build system. You want to use QtCreator to work on your project - great! No, Creator is an IDE and is documented as such. There's nothing in Qt's lit. that states Creator is purely an editor. This limitation appears to be the result of a design decision rather than any technical limitation. I like Creator very much and do use it as IDE (including as a build system). > > Your colleague is a die-hard emacs fan ... well, he should be able to > just work on the project too. Same goes for Visual Studio, Eclipse ... > Forcing anyone who wants to compile your code to use a specific editor > in a specific version is IMO a very bad idea. You mean like how Qt's VisualStudio plugin does not use .pro files natively? :P > > Now one can argue that qmake needs better documentation, or lacks some > functionality when it comes to project dependencies ... but that's > another issue then. > > Regards > > Kai > > NOT an (active) QtCreator developer, just a happy user > > > -- > Kai Koehne > 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 > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-creator >
_______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
