Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] the problem with Xorg, QT5 and imx vivant dirver
Date: Tue, 2 Aug 2016 21:30:44 +0200	[thread overview]
Message-ID: <20160802213044.264e63f8@free-electrons.com> (raw)
In-Reply-To: <CAMWiJUu_C8sJ+gaQdxQjAUS5wk_HEwzOdtEp4komzqOeB5XCBA@mail.gmail.com>

Hello,

On Tue, 2 Aug 2016 17:21:25 +0200, Zhaozhou Meng wrote:
> Hello,
> 
> I'am new to buildroot and I'am working on the buildroot 2016.05 for a
> project based on the board nitrogen6x, freescale imx6q.
> I want to build the QT5 using eglfs, egl and opengl and the Xorg using the
> imx vivant driver.

eglfs is about using Qt5 *without* X.org.

In Qt5, you have the following possibilities

 - linuxfb (raw framebuffer, no acceleration)
 - directfb
 - xcb (which means with X.org support, potentially with OpenGL)
 - eglfs (OpenGL ES without X.org, i.e by using EGL)

> So I choosed :
> X11 as freescale imx-gpu-viv output option ,
> xf86-video-imx-viv as X11R7 driver,
> QT5 Desktop Opengl as opengl support

I don't think you can select Qt5 Desktop OpenGL, as this depends on
full OpenGL support, while the i.MX6 GPU only provides OpenGL ES.

> Another question is that when I choosed the xf86-video-imx-viv as X11R7
> driver, the mesa3D is choosed, it means the imx vivant driver depends on
> mesa3D ?

I'm not sure to remember why Mesa3D is needed for the
xf86-video-imx-viv. Maybe Gary can chime in.

> The output of building like this:
> 
> ln -s libQt5Widgets.so.5.6.0 libQt5Widgets.so
> ln -s libQt5Widgets.so.5.6.0 libQt5Widgets.so.5
> ln -s libQt5Widgets.so.5.6.0 libQt5Widgets.so.5.6
> rm -f ../../lib/libQt5Widgets.so.5.6.0
> mv -f libQt5Widgets.so.5.6.0  ../../lib/
> rm -f ../../lib/libQt5Widgets.so
> rm -f ../../lib/libQt5Widgets.so.5
> rm -f ../../lib/libQt5Widgets.so.5.6
> mv -f libQt5Widgets.so ../../lib/
> mv -f libQt5Widgets.so.5 ../../lib/
> mv -f libQt5Widgets.so.5.6 ../../lib/
> Makefile:45 : la recette pour la cible ? sub-src-make_first ? a ?chou?e
> make[2]: *** [sub-src-make_first] Erreur 2
> package/pkg-generic.mk:195 : la recette pour la cible
> ? /home/plateau/Zhaozhou/buildroot-2016.05/output/build/qt5base-5.6.0/.stamp_built
> ?
> a ?chou?e
> make[1]: ***
> [/home/plateau/Zhaozhou/buildroot-2016.05/output/build/qt5base-5.6.0/.stamp_built]
> Erreur 2
> Makefile:36 : la recette pour la cible ? _all ? a ?chou?e
> make: *** [_all] Erreur 2

Please provide a longer build log: here you're not showing the
interesting message.

Alternatively, please provide the Buildroot .config file that allows to
reproduce the issue.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-08-02 19:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 15:21 [Buildroot] the problem with Xorg, QT5 and imx vivant dirver Zhaozhou Meng
2016-08-02 19:30 ` Thomas Petazzoni [this message]
2016-08-03  9:03   ` Zhaozhou Meng
2016-08-03  9:53     ` Thomas Petazzoni
2016-08-03 12:57       ` Gary Bisson
2016-08-03 15:42         ` Zhaozhou Meng
2016-08-04  9:54           ` Gary Bisson
2017-06-30  6:12             ` gomsis

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=20160802213044.264e63f8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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