From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/kodi: broken with sunxi mali package
Date: Wed, 5 Jul 2017 22:19:24 +0200 [thread overview]
Message-ID: <20170705221924.79f20c24@windsurf> (raw)
In-Reply-To: <20170705163254.15156-1-bernd.kuhls@t-online.de>
Hello,
On Wed, 5 Jul 2017 18:32:52 +0200, Bernd Kuhls wrote:
> diff --git a/package/kodi/Config.in b/package/kodi/Config.in
> index 658670139..00e4fbaef 100644
> --- a/package/kodi/Config.in
> +++ b/package/kodi/Config.in
> @@ -22,16 +22,21 @@ config BR2_PACKAGE_KODI_EGL_GLES
> depends on BR2_PACKAGE_HAS_LIBEGL
> depends on BR2_PACKAGE_HAS_LIBGLES
> depends on !BR2_PACKAGE_KODI_GL_EGL # prefer GL if available
> + depends on !BR2_PACKAGE_SUNXI_MALI
I'm not super happy with this solution. A quick Google search for
"invalid use of incomplete type ?class CEGLNativeType?" shows up a
bunch of results, and not with sunxi-mali.
According to https://github.com/ValveSoftware/steamlink-sdk/issues/93,
it seemed to be a pkg-config issue.
Perhaps some more investigation would be useful here?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-05 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 16:32 [Buildroot] [PATCH v2 1/3] package/kodi: broken with sunxi mali package Bernd Kuhls
2017-07-05 16:32 ` [Buildroot] [PATCH v2 2/3] package/kodi: remove -DCMAKE_C_FLAGS needed for sunxi-mali Bernd Kuhls
2017-07-05 16:32 ` [Buildroot] [PATCH v2 3/3] package/kodi: Add support for more archs Bernd Kuhls
2017-07-05 20:26 ` Samuel Martin
2017-07-05 20:19 ` Thomas Petazzoni [this message]
2017-07-15 15:50 ` [Buildroot] [PATCH v2 1/3] package/kodi: broken with sunxi mali package Bernd Kuhls
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=20170705221924.79f20c24@windsurf \
--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