Trenton Schulz wrote: >On 2009-03-14 17:12:11 +0100, Axel Jäger <[email protected]> said: >> Hi, >> I develop a plugin and over the years I got used to the very >> conservative Qt plugin loader that only loads a plugin when it is >> absolutely sure that the plugin will fit into the application testing >> buildkey, configuration, version or whatever. >> >> Now I have two versions of Qt on my mac: One built with carbon, the >> other one with cocoa and I see that my cocoa application tries to load >> a carbon plugin and it crashes. I'm wondering wether this should be >> case given the fact that the one and only reason for having such a >> mechanism is to prevent this situation. > >Ideally, one shouldn't have this problem, but we might have to include >this information. What does your crash log look like?
I was thinking about this too. The cross-platform Qt API should be
maintaining ABI compatibility between cocoa and carbon.
However, there is Cocoa-specific API in the QMacCocoa* classes. So yes, I
think we need to add "cocoa" to the buildkey.
--
Thiago Macieira - thiago.macieira (AT) nokia.com
Senior Product Manager - Nokia, Qt Software
Sandakerveien 116, NO-0402 Oslo, Norway
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt4-preview-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
