[Qt4-preview-feedback] Buildkey does not contains carbon/cocoa on Mac

[Trenton Schulz]

On 2009-03-16 11:29:15 +0100, Axel Jäger <axel.jaeger at basyskom.de> said:

> Ooops, this one went to trenton in private mail...
> 
> Hi,
> my motivation is: Qt was generally picky on what plugins to load so I  
> wanted to give it several versions to pick one from so my user likely  
> does not have to compile an own plugin. Also I did not want my user  
> dig around which version of my software he has to download. Also I did  
> not want my user to have several versions of my app installed for  
> several Qt versions because I prefer to have around 3 versions or so  
> of Qt on my system. So for me, including the configuration in the  
> buildkey would greatly improve the download and it just works  
> experience.

Well, to be fair, this particular bug you are seeing is not necessarily 
build key related. It seems that the plugin path for your Carbon and 
Cocoa build are both being searched and it happens to load a Cocoa (or 
Carbon) plugin in your app and that loads it's version of Qt, which 
gets you the errors down below. You would have a similar problem if you 
had done a couple of builds of Qt in previous releases that happened to 
have both plugin paths searched. At least our warning to use 
DYLD_PRINT_LIBRARIES allows you to debug the error.

Regardless, it probably is a good idea to include whether or not it was 
build against Cocoa. While if you are using straight Qt, it really 
shouldn't matter (assuming they point to the same Qt), if you use some 
of the API that accesses underlying datastructures (i.e., winId()), bad 
things could happen. Therefore, I've done the extra work to change the 
build key for Cocoa and it should be in 4.5.1. Nothing will stop you 
from editing the buildkey yourself (though it's certanily not 
recommended).

Don't forget there is also the -buildkey argument to configure as well.

However, as a consequence of my change now. Any plugins for Cocoa built 
against for 4.5.0 will NOT LOAD with 4.5.1. You need to build your 
plugin again. Sorry for the inconvenience.

Thanks for the report,

-- Trenton