From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] AM3517 Neon, OpenGL & EGLFS support
Date: Fri, 7 Jun 2013 10:08:24 +0200 [thread overview]
Message-ID: <20130607100824.2cc5e5e0@skate> (raw)
In-Reply-To: <CALo-6+h9Hm4BdgLa=ATXmZsyyQnmYYsszBFJ9zaXcu5vt2kyxA@mail.gmail.com>
Dear Charles Krinke,
On Thu, 6 Jun 2013 11:20:05 -0700, Charles Krinke wrote:
> Your new patch looks like the only difference is the line changing
> package/opengl/libgles/libgles.mk from
>
> -ifeq ($(LIBGLES_DEPENDENCIES),)
> +ifeq ($(LIBGLES_DEPENDENCIES),y)
The first line is the correct one. The second line was the one
originally introduced, but it was a bug. The idea here is that if
LIBGLES has no dependencies, then it means that no OpenGL
implementation was selected.
> I still get the same error when compiling Qt and that is:
>
> patching file mkspecs/common/posix/qplatformdefs.h
> >>> libgles undefined Configuring
> >>> libgles undefined Building
> >>> libgles undefined Installing to target
> >>> libegl undefined Extracting
> >>> libegl undefined Patching package/opengl//libegl
> >>> libegl undefined Configuring
> echo "No libEGL implementation selected. Configuration error."
This happens when no package provides a libEGL implementation, i.e
LIBEGL_DEPENDENCIES is empty.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-06-07 8:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 17:36 [Buildroot] AM3517 Neon, OpenGL & EGLFS support Charles Krinke
2013-06-05 18:05 ` Wojciech Sleńska
2013-06-05 18:17 ` Charles Krinke
2013-06-05 22:16 ` Charles Krinke
2013-06-06 17:16 ` Wojciech Sleńska
2013-06-06 18:20 ` Charles Krinke
2013-06-06 18:26 ` Charles Krinke
2013-06-06 19:26 ` Wojciech Sleńska
2013-06-07 8:08 ` Thomas Petazzoni [this message]
2013-06-07 14:44 ` Charles Krinke
2013-06-07 15:23 ` Thomas Petazzoni
2013-06-07 15:40 ` Charles Krinke
2013-06-07 16:48 ` Thomas Petazzoni
2013-06-07 17:06 ` Charles Krinke
2013-06-07 20:18 ` [Buildroot] [RFC] ti-gfx: add new package Spenser Gilliland
2013-06-11 17:58 ` Charles Krinke
2013-06-12 17:33 ` Spenser Gilliland
2013-06-12 17:55 ` Charles Krinke
2013-06-12 18:37 ` Spenser Gilliland
2013-06-13 8:03 ` Naumann Andreas
2013-06-13 14:11 ` Charles Krinke
2013-06-14 20:22 ` Thomas Petazzoni
2013-06-14 20:58 ` Charles Krinke
2013-06-14 23:12 ` Yann E. MORIN
2013-06-15 16:28 ` Thomas Petazzoni
2013-06-15 9:37 ` Sundareson, Prabindh
2013-06-13 14:58 ` Spenser Gilliland
2013-06-17 13:35 ` Andreas Naumann
2013-06-17 16:26 ` Spenser Gilliland
2013-06-13 16:49 ` Arnout Vandecappelle
2013-06-14 2:20 ` Sundareson, Prabindh
2013-06-15 16:33 ` Thomas Petazzoni
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=20130607100824.2cc5e5e0@skate \
--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 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.