All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Cattell <matthew@thorio.net>
To: meta-freescale@yoctoproject.org
Subject: Building Qt5 for i.MX6 tx6dl
Date: Fri, 4 Dec 2015 11:04:53 +0100	[thread overview]
Message-ID: <56616545.1020703@thorio.net> (raw)

Hello,

I started using yocto quite recently and successfully built Qt5 for the 
raspberry pi.

  In the last week I've been trying to get the same process to work to 
build the eglfs backend for Qt5 for the karo TRITON-TX6DL. In all 
attempts, the X server or the egl backend have failed to start when 
invoking a Qt application such as qmlscene. Running eglfs results in a 
segfault and attempting to open any of the applications in the X11 
backend build of the Qt5 based demo results in a GL error with no useful 
debug output, even after setting the debug environment variable for Qt.

I have tried following the steps here: 
http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard

and this gets me the closest to a working environment for the board - it 
just means the eglfs graphics won't work for graphical apps. The rest of 
Qt seems to be fine.

Also, the recent master build of yocto doesn't work at all since the 
patched ka-ro kernel that I've been using is 3.16 and this is not 
compatible with gcc5. What am I to do since I don't know which commits 
to cherry pick in order to get the recent changes that might fix the 
problem.

Searching for other similar problems potentially experienced by other 
users resulted in this:

http://stackoverflow.com/questions/20020898/qt-on-i-mx6-with-platform-eglfs-segmentation-fault

This appears to be related to the binaries required by the galcore 
kernel driver.

Does anyone have any ideas?

Thankyou




                 reply	other threads:[~2015-12-04 10:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=56616545.1020703@thorio.net \
    --to=matthew@thorio.net \
    --cc=meta-freescale@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.