On Sunday March 29 2015 14:15:20 Jeremy Huddleston Sequoia wrote:

> You can run 'nm -m /opt/local/share/qt5/plugins/platforms/libqxcb.dylib | 
> grep OpenGL' to see if there is anything actually using the OpenGL.framework 
> link.  However, this linking is certainly not the source of your problems.

It's not like that doesn't produce any output, but judging from the mangled 
names they're all Qt functions (OpenGL.framework is written in C I presume?)

> > But that would just be the xcb plugin. The host applications will still be 
> > linked against {OpenGL,AGL}.framework, at least as long as I just build the 
> > xcb platform plugin as an alternative for a Qt install that uses Cocoa by 
> > (and as the supported) default.
> 
> Then that's a bug in how the application is linking and would need to be 
> fixed there as well.

Erm, no, I wouldn't call that a bug in the linking. It's more that Qt5's 
platform plugin architecture apparently hasn't been conceived to support 
platforms that use/require different OpenGL libraries. For that to work Qt 
would either have to encapsulate all OpenGL functions in the platform plugin, 
or load the libraries dynamically.

R.
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to