From: Thomas Senyk <thomas.senyk@pelagicore.com>
To: meta-freescale@yoctoproject.org
Subject: Re: RFC regarding glimagesink
Date: Tue, 30 Jul 2013 11:06:46 +0200 [thread overview]
Message-ID: <1668084.tg0izVmCeg@rudolf> (raw)
In-Reply-To: <CACb8hfFJs2srU-p9V3fsS3V5SaVJHfZUfTZKbwON7hRoWz59-A@mail.gmail.com>
On Monday, 29 July, 2013 16:06:17 Rogerio Nunes wrote:
> On Mon, Jul 29, 2013 at 3:54 PM, Eric Nelson
>
> <eric.nelson@boundarydevices.com> wrote:
> > Hi Rogerio,
> >
> > On 07/29/2013 12:29 PM, Rogerio Nunes wrote:
> >> My apologies, Eric.
> >>
> >> I misread your email the first time.
> >>
> >> I'm trying a clean build now with master-next, but I'm having dependency
> >> issues.
> >> As soon as I fix this I'll look into glimagesink.
> >
> > I had some dependency issues as well, and I had to revert
> > Abhijit's wayland patch (78936c1994cb2db102bd200123be976a7c051b98)
> > to get past them.
> >
> > For some reason, with that patch, I was seeing the wayland version
> > of some libraries, so configure failed on gst-plugins-gl.
>
> That's exactly the same issue I'm having here... no fb* symbols in
> libEGL, so configure fails to link...
I wonder if the fb* symbols should actually vanish?
In a wl enabled version I've tested before I had both, wl_* and fb* symbols.
.. and IMO this is the right way, because it enabled you to have opengl-
based compositors and wayland-egl based clients with the same libraries.
Also from a include/define perspective only if EGL_API_FB is set, it makes
sense to set WL_EGL_PLATFORM.
quote from eglvivante.h:
...
#elif defined(LINUX) && defined(EGL_API_FB) && !defined(__APPLE__)
#if defined(WL_EGL_PLATFORM)
...
Does anyone know the reason why fb* symbols got removed from libEGL-wl.so?
Greet
Thomas
>
> Thanks.
>
> > Regards,
> >
> >
> > Eric
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
next prev parent reply other threads:[~2013-07-30 9:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 23:44 RFC regarding glimagesink Eric Nelson
2013-07-29 14:35 ` Rogerio Nunes
2013-07-29 15:08 ` Eric Nelson
2013-07-29 19:29 ` Rogerio Nunes
2013-07-29 19:54 ` Eric Nelson
2013-07-29 20:06 ` Otavio Salvador
2013-07-29 20:11 ` Rogerio Nunes
2013-07-29 20:12 ` Eric Nelson
2013-07-29 20:24 ` Rogerio Nunes
2013-07-29 20:28 ` Rogerio Nunes
2013-07-29 20:06 ` Rogerio Nunes
2013-07-30 9:06 ` Thomas Senyk [this message]
2013-07-30 9:52 ` Abhijit Potnis
2013-07-30 10:58 ` Thomas Senyk
2013-07-30 14:14 ` Rogerio Nunes
2013-07-30 14:38 ` Thomas Senyk
2013-07-30 17:26 ` Rogerio Nunes
2013-08-01 8:47 ` Abhijit Potnis
2013-08-01 12:50 ` Otavio Salvador
2013-08-01 13:05 ` Rogerio Nunes
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=1668084.tg0izVmCeg@rudolf \
--to=thomas.senyk@pelagicore.com \
--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.