On 2009-01-29 09:41:10 +0100, Martin Knelleken <[email protected]> said:
> Thanks Richard (and Thanks Winfried for your private mail)! > > Yes, it works this way. Even, if it is bit tricky to start our > application directly from XCode (due to some special scripts, > env vars and other things). That's why I used 'attach' in the past. > But this has nothing to do with Qt and is off-topic here. > At least, I am able to debug now :-) > > However I wonder why this qFatal message happens. > I get the same error when I move the Qt Frameworks/Libs to > another location and adapt the dylib pathes via install_name_tool. > The move and the path adaption is done by a script and as I already > mentioned this works fine with Carbon Qts. > > Maybe it's my fault. I am still not sure. I have to investigate > a bit more but if there is principal problem which you are aware > of, please let me know. Martin, this usually happens when two Qt libraries get loaded. Likely what is happening is that you are loading plugins that point to the OTHER QtGui on your system. You can create a qt.conf file in your bundle that will do stop Qt for looking for other plugins. Or you can do the same trick with your plugins. The macdeployqt tool should do all of this magic for you. -- Trenton _______________________________________________ Qt4-preview-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
