> > A properly written .pro file should indeed not break when using shadow > builds. >
There's very little documentation (other than working examples like Creator itself which are huge) on how to write a .pro file 'properly'. Creator itself confounds this by providing overly simple templates. I had to turn to google to figure out how to setup basic things like library links, include paths and change-dependencies. These are functions that the IDE should provide. Better wizards would go a long way to helping here (eg. a Wizard for setting up a library link capable of setting up the pro file 'properly' and a SUBDIR wizard). > > Of course, I can sympathize with the problems many are having now and > the lack of documentation. It was a hard choice to make between breaking > some projects by doing shadow builds by default (which can generally be > fixed), or not being able to support building against different Qt > configurations properly (desktop, Maemo, S60, Simulator, etc.) I don't understand why shadow builds were made the default - they've been an optional feature of Creator for some time now so if you needed them, they were there. Why the change? > Of course, maybe it still makes sense to have an option to disable the > "shadow-build by default" thing for those not interested in building for > different targets. > Yes this would be a good idea, a return to 1.x behavior. The problem is that the pro.user files have to be regularly being re-generated. > Regards, > Bjørn > > -- > Thorbjørn Lindeijer > Software Engineer > Nokia, Qt Development Frameworks > _______________________________________________ > 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
