From: Thomas Senyk <thomas.senyk@pelagicore.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>, Bruno CELDRAN <celdran@xap.fr>
Subject: Re: Problem with shader compiler
Date: Fri, 01 Feb 2013 17:55:24 +0100 [thread overview]
Message-ID: <1602552.78WQBhWFYX@rudolf> (raw)
In-Reply-To: <CAP9ODKpQgpKgxyA5C8Le9hzdyr=rhJ8bmjdWO3AHDnjcMvFLKw@mail.gmail.com>
On Wed, January 30, 2013 15:28:55 Otavio Salvador wrote:
> On Wed, Jan 30, 2013 at 3:09 PM, Thomas Senyk
>
> <thomas.senyk@pelagicore.com> wrote:
> > On Wed, January 30, 2013 16:23:28 Bruno CELDRAN wrote:
> >> Otavio Salvador <otavio@...> writes:
> >> > > Which BSP are your refferring for, and where could I download it ?
> >> >
> >> > Exactly this one. The 1.1.0. I did not test Qt5 on it yet but Thomas
> >> > might have more information. Thomas?
> >
> > I haven't tested 1.1.0 yet ... so many patches to apply ... ;)
> > Maybe I find some time tomorrow.
> >
> > .. if I got it right from the mailing-list all the upsteam patches are
> >
> > checked in, right?
>
> Not yet; the OE-Core/Poky patches got the Acked-by today but are not
> yet applied. So please apply those (3 patches actually) manually.
>
> > .. so if I use repo with '-b master' I just need to repo sync and apply
> > the
> >
> > meta-fsl-arm patches, right?
>
> For the rest, yes.
Ok I came along to do a quick test before I'm out-of-office next week.
I only selected patches I need as I'm building without 'x11' in
DISTRO_FEATURES
So just used patch 01 and 08 (maybe/properly I missed something this way?)
(and some manual adjustments to patch01 due to 'no-x11')
... the other patches were already upstream (e.g. firmware).. I think ;)
Anyway Qt5/eglfs can create the EGLDisplay and the background gets cleared
with 'white' ... so opengl/egl basically works, but I get following errors:
vertex shader compilation error:
fragment shader compilation error:
program link error: No vertex shader attached.
... with and without the 'mediump/heighp/#define'-workaround
The error-messages are not very ... verbose ;)
Maybe I missed something in the hurry .. not sure.
Anyway I'm going to do a complete clean build of everything in the week after
next week and come back to you about the state then.
gotta go now.
>
> --
> Otavio Salvador O.S. Systems
> E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
> Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
next prev parent reply other threads:[~2013-02-01 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 12:49 Problem with shader compiler Erik Botö
2013-01-17 14:37 ` Thomas Senyk
2013-01-17 14:40 ` Thomas Senyk
2013-01-17 20:24 ` Otavio Salvador
2013-01-30 15:55 ` Bruno CELDRAN
2013-01-30 16:02 ` Otavio Salvador
2013-01-30 16:23 ` Bruno CELDRAN
2013-01-30 17:09 ` Thomas Senyk
2013-01-30 17:28 ` Otavio Salvador
2013-02-01 16:55 ` Thomas Senyk [this message]
2013-02-08 5:58 ` Mattias Sahlén
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=1602552.78WQBhWFYX@rudolf \
--to=thomas.senyk@pelagicore.com \
--cc=celdran@xap.fr \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.