Re: [Development] [OS X/xcb] error: xp_attach_gl_context returned: 2 followed by hang during application exit
On Monday March 30 2015 08:15:09 Agocs Laszlo wrote: Hi, That has nothing to do with the platform plugins. You will want to introduce your own makespecs, or at least start customizing the standard Mac one. See e.g. mkspecs/common/mac.conf. That's what pulls in the standard GL frameworks for both the Qt libs and the app makefiles generated by qmake. I would argue that it depends on how the platform plugins are supposed to be used/usable. If the idea is that the user can load a different plugin in application X to have it render using a different platform, then yes, it has to do with the plugins and no, you cannot just rewrite the mkspec to cat for something linking to a different OpenGL library at runtime. If the plugins are not supposed to be used like that (despite the -platform commandline option), then yes, I can patch mac.conf so that it references the correct OpenGL libraries. I haven't checked, but I have a hunch that I'd have to build all of Qt like that. In the meantime, it does seem that things work well enough with the approach followed. The palette looks odd (MSWindows 95 like?) but apart from that and the reported hang-on-exit I think that there's enough basic functionality for routine testing for instance. It'll also give a nice tool to assess memory footprint (would it be smaller under X11) etc. And of course text renders much better using Freetype/Fontconfig with the Infinality-Ultimate patches than using CoreText O:-) R. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [OS X/xcb] error: xp_attach_gl_context returned: 2 followed by hang during application exit
The OpenGL libs (and potentially a number of other system libs) are not supposed to be runtime switchable. The exception is Windows, where Qt 5.4 introduced fully dynamic resolving for WGL/EGL/GL/GLES in the platform plugin. Other platforms may get similar features in the future, but OS X is unlikely to be one of them. Therefore the OS X makespecs will continue to pull in the GL frameworks in the foreseeable future. Cheers, Laszlo From: development-bounces+laszlo.agocs=theqtcompany@qt-project.org development-bounces+laszlo.agocs=theqtcompany@qt-project.org on behalf of René J.V. Bertin rjvber...@gmail.com Sent: Monday, March 30, 2015 10:42 AM Cc: Apple X11 Users' List; development@qt-project.org Subject: Re: [Development] [OS X/xcb] error: xp_attach_gl_context returned: 2 followed by hang during application exit On Monday March 30 2015 08:15:09 Agocs Laszlo wrote: Hi, That has nothing to do with the platform plugins. You will want to introduce your own makespecs, or at least start customizing the standard Mac one. See e.g. mkspecs/common/mac.conf. That's what pulls in the standard GL frameworks for both the Qt libs and the app makefiles generated by qmake. I would argue that it depends on how the platform plugins are supposed to be used/usable. If the idea is that the user can load a different plugin in application X to have it render using a different platform, then yes, it has to do with the plugins and no, you cannot just rewrite the mkspec to cat for something linking to a different OpenGL library at runtime. If the plugins are not supposed to be used like that (despite the -platform commandline option), then yes, I can patch mac.conf so that it references the correct OpenGL libraries. I haven't checked, but I have a hunch that I'd have to build all of Qt like that. In the meantime, it does seem that things work well enough with the approach followed. The palette looks odd (MSWindows 95 like?) but apart from that and the reported hang-on-exit I think that there's enough basic functionality for routine testing for instance. It'll also give a nice tool to assess memory footprint (would it be smaller under X11) etc. And of course text renders much better using Freetype/Fontconfig with the Infinality-Ultimate patches than using CoreText O:-) R. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [OS X/xcb] error: xp_attach_gl_context returned: 2 followed by hang during application exit
That has nothing to do with the platform plugins. You will want to introduce
your own makespecs, or at least start customizing the standard Mac one. See
e.g. mkspecs/common/mac.conf. That's what pulls in the standard GL frameworks
for both the Qt libs and the app makefiles generated by qmake.
Best regards,
Laszlo
From: development-bounces+laszlo.agocs=theqtcompany@qt-project.org
development-bounces+laszlo.agocs=theqtcompany@qt-project.org on behalf of
René J.V. Bertin rjvber...@gmail.com
Sent: Monday, March 30, 2015 12:03 AM
To: Jeremy Huddleston Sequoia
Cc: Apple X11 Users' List; development@qt-project.org
Subject: Re: [Development] [OS X/xcb] error: xp_attach_gl_context returned:
2 followed by hang during application exit
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
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [OS X/xcb] error: xp_attach_gl_context returned: 2 followed by hang during application exit
On Monday March 30 2015 08:54:48 Agocs Laszlo wrote: The OpenGL libs (and potentially a number of other system libs) are not supposed to be runtime switchable. The exception is Windows, where Qt 5.4 introduced fully dynamic resolving for WGL/EGL/GL/GLES in the platform plugin. More or less like what GLEW does to encapsulate OpenGL (or was that another project, it's been a while I manhandled OpenGL...)? Such an approach shouldn't be (too) platform-dependent, and thus relatively straightforward to bring to other platforms, no? Other platforms may get similar features in the future, but OS X is unlikely to be one of them. Therefore the OS X makespecs will continue to pull in the GL frameworks in the foreseeable future. I wasn't expecting anything else. But: FWIW, I think there might be interest in bringing X11/xcb support back to OS X, which could justify bringing those similar features on to OS X too. I'm not volunteering though (but wouldn't mind being paid for doing this either ;)). ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Add widgets into qt3d window
Hi , I have created a simple qt3d application in c++, which has a rotating cube. I would like to add buttons to the windows to stop/start rotating the cube. I am not able to see such an example anywhere in the qt3d examples which has support for widgets. Could anyone please help me? Thanks Regards Arjun ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Switching remote url for qt5 git clone
On Thu, 26 Mar 2015, Adam Light wrote: I'd like to move my checkout to git://code.io.qt. I got reminded of your mail when I just did a new clone: http://wiki.qt.io/Building_Qt_5_from_Git suggests the usage of: git clone git://code.qt.io/git/qt/qt5.git but the /git/ part is probably just an oversight? Harri. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Errors in release mode only
QEventLoop: Cannot be used without QApplication Says everything. Show your code. Regards, Konstantin 2015-03-30 23:21 GMT+04:00 raven-worx Software i...@raven-worx.net: Hi, i get the following print outs to the console and absolutley have no clue why: SHIMVIEW: ShimInfo(Complete) QEventLoop: Cannot be used without QApplication QObject::connect: Cannot connect (null)::aboutToQuit() to QNativeWifiEngine::closeHandle() But this only happens in RELEASE MODE! DEBUG mode works fine and these print outs are not showing up. I even get these print outs when my main() only returns 0, so no QApplication is instantiated meaning as soon as i link against Qt binaries. Once the application starts up i also noticed that (queued) signals from other threads are not delivered anymore, which most probably involves the QEventLoop error message somehow. But on the other hand events from the OS are delivered. I am using: QtCreator 3.3.1, MSVC2012, Qt 5.4.1 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Errors in release mode only
As i said, i get it even when i just compile this piece of code and
link to Qt binaries (core, gui, widgets, network) and only in release:
int main(int argc, char *argv[])
{
QApplication app(argc, argv);
return app.exec();
}
I guess this is only an issue on Windows.
QEventLoop: Cannot be used without QApplication
Says everything.
Show your code.
Regards,
Konstantin
2015-03-30 23:21 GMT+04:00 raven-worx Software i...@raven-worx.net:
Hi,
i get the following print outs to the console and absolutley have no clue
why:
SHIMVIEW: ShimInfo(Complete)
QEventLoop: Cannot be used without QApplication
QObject::connect: Cannot connect (null)::aboutToQuit() to
QNativeWifiEngine::closeHandle()
But this only happens in RELEASE MODE! DEBUG mode works fine and these
print outs are not showing up.
I even get these print outs when my main() only returns 0, so no
QApplication is instantiated meaning as soon as i link against Qt
binaries.
Once the application starts up i also noticed that (queued) signals
from other threads are not delivered anymore, which most probably
involves the QEventLoop error message somehow. But on the other hand
events from the OS are delivered.
I am using:
QtCreator 3.3.1, MSVC2012, Qt 5.4.1
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Add widgets into qt3d window
On 31/03/15 01:08, Arjun Das wrote: Hi , I have created a simple qt3d application in c++, which has a rotating cube. I would like to add buttons to the windows to stop/start rotating the cube. I am not able to see such an example anywhere in the qt3d examples which has support for widgets. I recently came across this, but can't remember if it was on this list or stackoverfow. Anyway, there is a solution that allows you to make the Qt3D::Window behave as a widget, I think twiddling with it's Qt::WindowFlags is enough, something like view-setFlags(Qt::Widget). Krys Could anyone please help me? Thanks Regards Arjun ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Errors in release mode only
Hi, i get the following print outs to the console and absolutley have no clue why: SHIMVIEW: ShimInfo(Complete) QEventLoop: Cannot be used without QApplication QObject::connect: Cannot connect (null)::aboutToQuit() to QNativeWifiEngine::closeHandle() But this only happens in RELEASE MODE! DEBUG mode works fine and these print outs are not showing up. I even get these print outs when my main() only returns 0, so no QApplication is instantiated meaning as soon as i link against Qt binaries. Once the application starts up i also noticed that (queued) signals from other threads are not delivered anymore, which most probably involves the QEventLoop error message somehow. But on the other hand events from the OS are delivered. I am using: QtCreator 3.3.1, MSVC2012, Qt 5.4.1 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] QtWebKit: Turning off NPAPI plugin
Hello! Recently I was wondering how to unload specific NPAPI-based plugin (e.g. flash player) via QtWebKit and haven't succeed so far. Do you guys have any ideas on is it possible or not? Ideally, I'd like to propogate a method to QWebView, which will unload() npapi module there, but I am not sure that I know where it's (PluginPackage) is being stored inside QtWebKit. Thanks! ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Errors in release mode only
On Monday 30 March 2015 22:36:04 raven-worx Software wrote:
As i said, i get it even when i just compile this piece of code and
link to Qt binaries (core, gui, widgets, network) and only in release:
int main(int argc, char *argv[])
{
QApplication app(argc, argv);
return app.exec();
}
I guess this is only an issue on Windows.
Not all Windows. Just MSVC, when you mix different versions of Qt DLLs.
Anyway, not a Qt bug. This is a known issue with Windows DLLs and runtimes
since at least Qt 2.0. The bug is in your buildsystem.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Switching remote url for qt5 git clone
It is an oversight. I fixed it. Thank you for pointing it out. -- Alex From: development-bounces+alexander.blasche=theqtcompany@qt-project.org development-bounces+alexander.blasche=theqtcompany@qt-project.org on behalf of Harri Porten por...@froglogic.com Sent: Monday, March 30, 2015 18:31 To: development@qt-project.org Subject: Re: [Development] Switching remote url for qt5 git clone On Thu, 26 Mar 2015, Adam Light wrote: I'd like to move my checkout to git://code.io.qt. I got reminded of your mail when I just did a new clone: http://wiki.qt.io/Building_Qt_5_from_Git suggests the usage of: git clone git://code.qt.io/git/qt/qt5.git but the /git/ part is probably just an oversight? Harri. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
