Agreed, and a possible solution is to use $$PWD/lib in your .pro files.
this should replace pwd with the directory the .pro file is sitting in.

On 06/24/2010 11:05 PM, ext Danny Price wrote:
> The shadow build option is stored in the pro.user file so if it ever
> gets regenerated, you'll have the same issues again.
>
> It's worth updating your code to account for the shadow build. If you
> have multiple projects with inter-dependencies, the easiest solution
> is to add them to a subdir. That way Creator will generate a single
> shadow-build directory for all projects so your (relative) build paths
> will still work.
>
>
> On Thu, Jun 24, 2010 at 1:16 PM, <[email protected]
> <mailto:[email protected]>> wrote:
>
>     Bingo - "shadow build" - that was it!
>
>     Turn it off and everything works just fine again...
>
>     Thanks a lot: I would have never ever ever found this problem by
>     my own!
>     (Even after 35 years of programming...)
>
>     Greetings,
>     Cornelis
>
>     _____________________
>
>     Cornelis Bockemühl
>     Holcim Group Support Ltd
>     Cement Manufacturing Services
>     Materials Technology
>     Reserve Evaluation and Quarry Planning
>     Im Schachen
>     CH-5113 Holderbank
>     Phone +41 58 858 51 30
>     Fax +41 58 858 51 51
>     [email protected] <mailto:[email protected]>
>     www.holcim.com <http://www.holcim.com>
>     This e-mail is confidential and intended only for the use of the above
>     named addressee. If you have received this e-mail in error, please
>     delete
>     it immediately and notify us by e-mail or telephone.
>
>
>     _______________________________________________
>     Qt-creator mailing list
>     [email protected] <mailto:[email protected]>
>     http://lists.trolltech.com/mailman/listinfo/qt-creator
>
>


-- 
Bill King, Software Engineer
Qt Development Frameworks, Nokia Pty Ltd
Brisbane Office

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator

Reply via email to