Is there a fix for Qt-Raspi EGL/GLES names mismatch?
-
Since Raspbian Stretch, Qt and Raspberry Pi use different names to refer to EGL/GLES shared objects and this is making some people very upset (and with good reason).
The issue is described in this and this bug reports and has been around for a long time.
There are some possible solutions to that problem:
None of them worked for me.
So I'm here to ask:
- Are there plans to put Qt and Raspbian on the same page again in the future?
- Does anyone know a solution (that really works) to the problem?
-
It's working now.
The problem was linux-rasp-pi3-g++'s
qmake.conf
file. If we're building Qt for RPi3 we need to create a newqmake.conf
based on linux-rasp-pi-g++ and replace the build flags with those from linux-rasp-pi3-g++.The fix is described in this guide.
-
Since Raspbian Stretch, Qt and Raspberry Pi use different names to refer to EGL/GLES shared objects and this is making some people very upset (and with good reason).
The issue is described in this and this bug reports and has been around for a long time.
There are some possible solutions to that problem:
None of them worked for me.
So I'm here to ask:
- Are there plans to put Qt and Raspbian on the same page again in the future?
- Does anyone know a solution (that really works) to the problem?
- Are there plans to put Qt and Raspbian on the same page again in the future?
That's a question for the Qt company. This is a users drvien forum...
- Does anyone know a solution (that really works) to the problem?
Have you check this guide? See step #6 regarding EGL libraries naming which uses the edit qmake.conf approach.
-
- Are there plans to put Qt and Raspbian on the same page again in the future?
That's a question for the Qt company. This is a users drvien forum...
- Does anyone know a solution (that really works) to the problem?
Have you check this guide? See step #6 regarding EGL libraries naming which uses the edit qmake.conf approach.
-
@pablo-j-rogina said in Is there a fix for Qt-Raspi EGL/GLES names mismatch?:
Have you check this guide? See step #6 regarding EGL libraries naming which uses the edit qmake.conf approach.
Yes. I tried that before.
@rrd0 said in Is there a fix for Qt-Raspi EGL/GLES names mismatch?:
I tried that before.
so? did it worked for you?
According to the guide I pointed out, it's a solution for the scenario you mentioned
-
@rrd0 said in Is there a fix for Qt-Raspi EGL/GLES names mismatch?:
I tried that before.
so? did it worked for you?
According to the guide I pointed out, it's a solution for the scenario you mentioned
-
It's working now.
The problem was linux-rasp-pi3-g++'s
qmake.conf
file. If we're building Qt for RPi3 we need to create a newqmake.conf
based on linux-rasp-pi-g++ and replace the build flags with those from linux-rasp-pi3-g++.The fix is described in this guide.