All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11926] Cross compiled Qt applications aren't working anymore
Date: Wed, 05 Feb 2020 15:40:24 +0000	[thread overview]
Message-ID: <bug-11926-163-9Od71b2n82@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11926-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11926

--- Comment #6 from Martin <martinv1985@gmail.com> ---
I was having similar issues when compiling a image with qt for arm. Even
qtdiag, which was also build using buildroot, had the error that the EGL/GLES
libraries where linked using the absolute paths of the machine running
buildroot. However, when testing Qt version 5.14 this problem seems to be
resolved. The qtdiag works again and i can also compile and run one of the
example programs myself.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-02-05 15:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-02 19:51 [Buildroot] [Bug 11926] New: Cross compiled Qt applications aren't working anymore bugzilla at busybox.net
2019-06-02 19:54 ` [Buildroot] [Bug 11926] " bugzilla at busybox.net
2019-06-02 19:56 ` bugzilla at busybox.net
2019-06-02 20:14 ` bugzilla at busybox.net
2019-06-03  7:01 ` bugzilla at busybox.net
2019-06-03 14:07 ` bugzilla at busybox.net
2019-06-06 10:39 ` bugzilla at busybox.net
2020-02-05 15:40 ` bugzilla at busybox.net [this message]
2020-02-05 22:34 ` bugzilla at busybox.net
2020-02-06  9:36 ` bugzilla at busybox.net
2020-02-06  9:49 ` bugzilla at busybox.net
2020-02-17 12:04 ` bugzilla at busybox.net
2020-02-17 12:42 ` bugzilla at busybox.net

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=bug-11926-163-9Od71b2n82@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 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.