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

[Danny Price]

On 19 Apr 2010, at 09:49, Tobias Hunger 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?





I've attached a simple project - three separate projects. A static lib, a dynamic lib that depends on the static lib and an app that loads the dynamic lib and calls a function. There is no subdir project - these were added separately to the session in the way that Creator *wants*.

I put this together on OSX so the the pro file may need some tweaking to get it working on other platforms.

In previous versions of Creator (without the default shadow build), this project built fine. But if I import it into the latest snapshots, I will get build errors like this: 

error: No rule to make target `../Lib/./Debug/libMyLib.a', needed by `Debug/libMyDynamicLib.1.0.0.dylib'.  Stop.

Because the Creator is ignoring the DESTDIR variable. This completely beaks my project.

 
> 
> 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:-/

Yeah I think this is case I'm describing. And the problem that EVERY user of my project will face if they try to build it with Creator. 

BUT, if I turn OFF the shadow build, I get this error

error: [Debug/MyLib.o] Error 1

Even with shadow build off, it will not build. I must delete the makefiles to get it working again. And for Creator will not clear down the makefiles even if I clean the project. Imagine having to do this with multiple projects with multiple configurations!!!

> 
>> 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.

Sounds like the problems I'm experiencing now that shadow builds are turned *on* by default :)

> 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.

I'm not sold on why shadow builds should default to on. Yes, it's nice to have qmake-style behavior where the objects and binaries are placed in seperate directories but surely all this can be accomplished via pro files and qmake? Creator should be a front end to qmake - it shouldn't interfere with my pro file settings. 

> 
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20100424/c4a4a44b/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TestProjects.zip
Type: application/zip
Size: 8944 bytes
Desc: not available
Url : http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20100424/c4a4a44b/attachment.zip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-creator-old/attachments/20100424/c4a4a44b/attachment-0001.html