[Qt-creator] build settings for cross platform? multiple svn checkouts on each development computer

[Danny Price]

I think the settings in the .pro file should always take priority. This is
allows for automated builds and builds outside of Creator. It shouldn't be
muddied up to handle Creator special-cases. That sets a precedent.

I'm not sold on the idea that Creator must turn on shadow builds by default.
If it's an issue as stated by Tobias, why not simple turn it on in via the
Project screen/pro.user file for the projects that require it as was the
case previously? The functionality is identical.

Tobias, your statement seems to imply that the Nokia/Qt devs are also
throwing away their pro.user files to get builds working which is the
underlying issue. If that's the case, why not fix pro.user files once and
for all? Fix the problem at source?

On Mon, Apr 19, 2010 at 2:56 PM, Coda Highland <coda at bobandgeorge.com>wrote:

> As a thought... How troublesome would it be to have something like a
> CREATOR_PRAGMA variable in the .pro file that directs these kinds of
> things? qmake could simply ignore it, after all. This would allow some
> settings -- like, for instance, shadow builds -- to be overridden by
> the .pro file.
>
> /s/ Adam
>
> On Mon, Apr 19, 2010 at 3:49 AM, Tobias Hunger <tobias.hunger at nokia.com>
> wrote:
> > Hi Danny!
> >
> > Yes, using the .pro-file for settings to be shared between developers is
> > the right thing to do. Thanks for explaining that so well!
> >
> > On 19.04.2010 10:16, ext Danny Price wrote:
> >> However, I've noticed that the latest snapshots turn on the shadow build
> >> feature by default. This is a problem because it overrides the build
> >> paths specified in the .pro file. And if I turn off the feature it will
> >> be turned on again the next time the .pro.user is generated (ie. when
> >> someone checks out my code).
> >
> > Can you please describe your directory layout? Are you using your own
> > shadow building setup? Which variables are ignored by our use of shadow
> > builds? Can you send us a .pro-file that breaks for you so that we can
> > improve the situation?
> >
> > A existing in-source build should get detected and get imported using
> > the settings used to create the build. This is of course not a help in
> > the fresh-checkout use-case you mention:-/
> >
> >  > I hope Nokia revert this to the previous behavior (turn off shadow
> >  > builds by default).
> >
> > We did turn on shadow-building by default since we need to improve the
> > multiple platform use-case. That is a real pain with pre-2.0beta
> > creators since switching platforms totally confuses make, thus resulting
> > in broken builds and all kinds of strangeness. There is just too many
> > complaints about this to ignore;-). So shadow-building is -- from our
> > perspective -- a must have for the next version.
> >
> > However we are open for suggestions on how to minimize the impact on
> > other 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 at trolltech.com
> > http://lists.trolltech.com/mailman/listinfo/qt-creator
> >
>
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20100419/27bf6159/attachment.html