From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 and display
Date: Sun, 1 May 2016 17:00:05 +0200 [thread overview]
Message-ID: <572619F5.2060403@gmail.com> (raw)
In-Reply-To: <87lh3usvx4.fsf@dell.be.48ers.dk>
Hi,
I compiled Qt5 in Buildroot 2016.05-git-01124-g70fc85f-dirty with both
X11 and eglfs support, because I would like to try both.
Console application runs fine, but when I launch a visual application
(i.e. qml) I get:
> Could not open display
Currently I have no X server running so I'm launching my application
with -platform eglfs
exporting QT_DEBUG_PLUGINS=1 leads to this output:
> QML debugging is enabled. Only use this in a safe environment.
> QFactoryLoader::QFactoryLoader() checking directory path
> "/usr/lib/qt/plugins/platforms" ...
> QFactoryLoader::QFactoryLoader() looking at
> "/usr/lib/qt/plugins/platforms/libqeglfs.so"
> Found metadata in lib /usr/lib/qt/plugins/platforms/libqeglfs.so,
> metadata=
> {
> "IID":
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
> "MetaData": {
> "Keys": [
> "eglfs"
> ]
> },
> "className": "QEglFSIntegrationPlugin",
> "debug": false,
> "version": 329216
> }
>
>
> Got keys from plugin meta data ("eglfs")
> QFactoryLoader::QFactoryLoader() looking at
> "/usr/lib/qt/plugins/platforms/libqminimal.so"
> Found metadata in lib /usr/lib/qt/plugins/platforms/libqminimal.so,
> metadata=
> {
> "IID":
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
> "MetaData": {
> "Keys": [
> "minimal"
> ]
> },
> "className": "QMinimalIntegrationPlugin",
> "debug": false,
> "version": 329216
> }
>
>
> Got keys from plugin meta data ("minimal")
> QFactoryLoader::QFactoryLoader() looking at
> "/usr/lib/qt/plugins/platforms/libqminimalegl.so"
> Found metadata in lib /usr/lib/qt/plugins/platforms/libqminimalegl.so,
> metadata=
> {
> "IID":
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
> "MetaData": {
> "Keys": [
> "minimalegl"
> ]
> },
> "className": "QMinimalEglIntegrationPlugin",
> "debug": false,
> "version": 329216
> }
>
>
> Got keys from plugin meta data ("minimalegl")
> QFactoryLoader::QFactoryLoader() looking at
> "/usr/lib/qt/plugins/platforms/libqoffscreen.so"
> Found metadata in lib /usr/lib/qt/plugins/platforms/libqoffscreen.so,
> metadata=
> {
> "IID":
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
> "MetaData": {
> "Keys": [
> "offscreen"
> ]
> },
> "className": "QOffscreenIntegrationPlugin",
> "debug": false,
> "version": 329216
> }
>
>
> Got keys from plugin meta data ("offscreen")
> QFactoryLoader::QFactoryLoader() looking at
> "/usr/lib/qt/plugins/platforms/libqxcb.so"
> Found metadata in lib /usr/lib/qt/plugins/platforms/libqxcb.so, metadata=
> {
> "IID":
> "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
> "MetaData": {
> "Keys": [
> "xcb"
> ]
> },
> "className": "QXcbIntegrationPlugin",
> "debug": false,
> "version": 329216
> }
>
>
> Got keys from plugin meta data ("xcb")
> QFactoryLoader::QFactoryLoader() checking directory path
> "/opt/QmlTest/bin/platforms" ...
> loaded library "/usr/lib/qt/plugins/platforms/libqeglfs.so"
> QFactoryLoader::QFactoryLoader() checking directory path
> "/usr/lib/qt/plugins/egldeviceintegrations" ...
> QFactoryLoader::QFactoryLoader() looking at
> "/usr/lib/qt/plugins/egldeviceintegrations/libqeglfs-x11-integration.so"
> Found metadata in lib
> /usr/lib/qt/plugins/egldeviceintegrations/libqeglfs-x11-integration.so, metadata=
> {
> "IID":
> "org.qt-project.qt.qpa.egl.QEGLDeviceIntegrationFactoryInterface.5.5",
> "MetaData": {
> "Keys": [
> "eglfs_x11"
> ]
> },
> "className": "QEglFSX11IntegrationPlugin",
> "debug": false,
> "version": 329216
> }
>
>
> Got keys from plugin meta data ("eglfs_x11")
> QFactoryLoader::QFactoryLoader() checking directory path
> "/opt/QmlTest/bin/egldeviceintegrations" ...
> loaded library
> "/usr/lib/qt/plugins/egldeviceintegrations/libqeglfs-x11-integration.so"
> Could not open display
> Aborted
> Application finished with exit code 134.
I never had this kind of problem with all previous Buildroot
environments I compiled.
This is due to my configuration? I attach the .config file.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/xml
Size: 84242 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160501/07ad3c71/attachment-0001.wsdl>
prev parent reply other threads:[~2016-05-01 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 17:57 [Buildroot] Bluetooth BCM20702A1 Marco Trapanese
2016-04-30 20:07 ` Peter Korsgaard
2016-05-01 15:00 ` Marco Trapanese [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=572619F5.2060403@gmail.com \
--to=marcotrapanese@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox