Thanks for the heads-up. Out of interest, how can you use rpath with qmake, in the pro. file? I still use excutable_path, run as a post-link command on my dylibs.
On Mon, Nov 1, 2010 at 2:21 PM, <eike.zil...@nokia.com> wrote: > I'm wondering if anyone actually compiles Qt Creator on Mac OS 10.4 by > themselves (we don't provide binary packages for that platform anymore). > > If you do so, read on. > > A recent change (49b86e771761b3a9a1799d11f777b13077c6305e) requires you to > specify that you want to build Qt Creator 10.4-compatible by either > a) setting the env var QTC_TIGER_COMPAT=1, or > b) calling qmake -r TIGER_COMPAT_MODE=1 > > Technical reason is a switch to use @rpath instead of @executable_path, > because the latter is an inflexible beast (and @loader_path too) and makes > using the Qt Creator libs directly in e.g. tests next to impossible. > > Please notify me of any problems you encounter. > > ++ Eike > _______________________________________________ > Qt-creator mailing list > Qt-creator@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-creator >
_______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
