All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Senyk <thomas.senyk@pelagicore.com>
To: meta-freescale@yoctoproject.org
Subject: Re: Problem with shader compiler
Date: Thu, 17 Jan 2013 15:40:20 +0100	[thread overview]
Message-ID: <3687851.a2KRPc6CnN@rudolf> (raw)
In-Reply-To: <3098459.WXlKcWq7AS@rudolf>

We can stop this ...
Just got notices that it's known and already fixed in the last BSP release 
(from Tuesday)


Thanks and sorry for the useless buzz :)
Greets
Thomas





On Thu, January 17, 2013 15:37:46 Thomas Senyk wrote:
> On Thu, January 17, 2013 13:49:46 Erik Botö wrote:
> > Hi,
> > 
> > I'm using meta-fsl-arm with an imx6 sabrelite board, kernel 3.0.35
> > + gpu-viv-bin-mx6q_12.09.01.
> > 
> > I use the sysroot from poky to build Qt5, but then run in to some problems
> > with shaders. They seem to stem from the fact that the shader compiler
> > doesn't support #define and/or #ifdef.
> > 
> > Example:
> > 
> > QOpenGLShader::compile(Fragment): (5:0) : error : syntax error
> > 
> > *** Problematic Fragment shader source code ***
> > #ifndef GL_FRAGMENT_PRECISION_HIGH
> > #define highp mediump
> > #endif
> > uniform sampler2D texture;
> > varying highp vec2 textureCoord;
> > void main() {
> > 
> >    gl_FragColor = texture2D(texture, textureCoord).bgra;
> > 
> > }
> > 
> > ***
> > 
> > It can be manually fixed by exchanging all occurences of highp with
> > mediump, instead of relying on the preprocessor macros. The shader
> > compiler
> > should support this, right?
> 
> Addition bug-report information:
> A error looks like that:
> 
> Warning: QOpenGLShader::compile(Fragment): (4:0) : error : syntax error
> Warning: *** Problematic Fragment shader source code ***
> Warning: #ifndef GL_FRAGMENT_PRECISION_HIGH
> #define highp mediump
> #endif
> varying highp vec2 qt_TexCoord;
> uniform sampler2D qt_Texture;
> void main() {
>     gl_FragColor = texture2D(qt_Texture, qt_TexCoord);
> }
> 
> If one removes the the 3 "#ifndef ... #endif" lines it works.
> Maybe the GLSL-preprocessor is broken?
> 
> 
> Greets
> Thomas
> 
> > Best Regards,
> > Erik Botö


  reply	other threads:[~2013-01-17 14:40 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 [this message]
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
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=3687851.a2KRPc6CnN@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.