From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] qt5, eglfs and xcb
Date: Sun, 30 Mar 2014 15:47:43 +0200 [thread overview]
Message-ID: <5338207F.9010807@gmail.com> (raw)
Hello,
when you try to build qt5 with the X support (xcb), selecting one of the
following modules: qtquick*, qt5declarative, qt5graphicaleffects and
qt5multimedia, leads to force the selection of the eglfs support.
After three days of build failures (due to the same constants defined
both from xbc and eglfs) I asked an aid to a company which offer a
technical support about Qt. The says only qtquick2 requires the opengl
acceleration and this one is provided also from xbc.
So it shouldn't required at all the eglfs plugin if you're using X.
Please, might you verify this?
If they are right, could you fix the dependencies so we can build a
working buildroot image with Qt5 and xcb?
Thanks!
Marco
next reply other threads:[~2014-03-30 13:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 13:47 Marco Trapanese [this message]
2014-03-30 15:21 ` [Buildroot] qt5, eglfs and xcb Thomas Petazzoni
2014-04-01 10:05 ` Marco Trapanese
2014-04-01 12:40 ` Thomas Petazzoni
2014-04-01 16:16 ` Jérôme Pouiller
2014-04-01 16:16 ` [Buildroot] [PATCH 1/2] qt5declarative: Reduce dependencies to GLes2 only Jérôme Pouiller
2014-04-20 9:18 ` Thomas Petazzoni
2014-07-15 8:26 ` Hadrien Boutteville
2014-07-15 14:03 ` Fatih Aşıcı
2014-07-15 16:24 ` Jérôme Pouiller
2014-07-15 17:03 ` Thomas Petazzoni
2014-04-01 16:16 ` [Buildroot] [PATCH 2/2] Add supporit for Vivante xdriver Jérôme Pouiller
2014-04-20 10:13 ` Thomas Petazzoni
2014-09-16 14:46 ` Thomas Petazzoni
2014-09-16 17:07 ` Jérôme Pouiller
2014-09-16 17:59 ` Thomas Petazzoni
2014-04-01 16:18 ` [Buildroot] qt5, eglfs and xcb Marco Trapanese
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=5338207F.9010807@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