> You might have a better chance using gl4es than switching to GLES
> where the fedora default is to use GL everywhere.
> But it's probably not something that can be supported on the fedora
> side for the same reason libhybris can't be supported. (you will need
> to link libhybris/gl4es to a propri
Le mar. 22 sept. 2020 à 13:23, rinigus a écrit :
>
> As far as I have seen, having pkgconfig(gl) in Qt devel dependencies
> brings in glvnd libs in all kinds of variants clashing with libhybris.
> Specific issue I will have to recheck tonight and get back to you.
>
> Maybe such a combination Mesa
As far as I have seen, having pkgconfig(gl) in Qt devel dependencies
brings in glvnd libs in all kinds of variants clashing with libhybris.
Specific issue I will have to recheck tonight and get back to you.
Maybe such a combination Mesa GL software rendering + hw accelerated
EGL/GLESv2 would work.
The customer whom you serve does not ask you much. Just master your work and do
not leave behind dirt and be on time always. Honesty and sincerity are the
basis of every work. Make every customer a friend to you. Good dealing with
customers brings you good luck. Repair Bazar company provides th
> > libhybris systems don't have libGL.so at all. It is for "regular"
> > Android devices transformed to glibc Linux through libhybris. So, when
> > compiling anything that links to libGL, I get into trouble.
>
> What is the hardware that you want to use via libhybris? Ultimately
> libhybris is not
> libhybris systems don't have libGL.so at all. It is for "regular"
> Android devices transformed to glibc Linux through libhybris. So, when
> compiling anything that links to libGL, I get into trouble.
What is the hardware that you want to use via libhybris? Ultimately
libhybris is not something
On Tue, Sep 22, 2020 at 7:09 AM rinigus wrote:
>
> libhybris systems don't have libGL.so at all. It is for "regular"
> Android devices transformed to glibc Linux through libhybris. So, when
> compiling anything that links to libGL, I get into trouble.
>
Why wouldn't libhybris work through glvnd s
libhybris systems don't have libGL.so at all. It is for "regular"
Android devices transformed to glibc Linux through libhybris. So, when
compiling anything that links to libGL, I get into trouble.
Rinigus
On Tue, Sep 22, 2020 at 2:02 PM Neal Gompa wrote:
>
> On Tue, Sep 22, 2020 at 6:59 AM rinig
On Tue, Sep 22, 2020 at 6:59 AM rinigus wrote:
>
> I am looking for Qt that would not depend on libGL at all, something
> like https://mitya57.me/weblog/2020/01/qt-opengl-es-packages-available.html
> for debian. I guess there are no plans for that yet.
>
Is there a good reason for doing it that w
I am looking for Qt that would not depend on libGL at all, something
like https://mitya57.me/weblog/2020/01/qt-opengl-es-packages-available.html
for debian. I guess there are no plans for that yet.
Rinigus
On Tue, Sep 22, 2020 at 1:54 PM Neal Gompa wrote:
>
> On Tue, Sep 22, 2020 at 6:31 AM rini
On Tue, Sep 22, 2020 at 6:31 AM rinigus wrote:
>
> Hi,
>
> few weeks ago we started working on porting Nemomobile to Fedora 32 as
> a base. Now I am hitting an issue when trying to make it work with
> libhybris device. On that device, I have GLESv2 and would need Qt that
> is not linked to libGL.
Hi,
few weeks ago we started working on porting Nemomobile to Fedora 32 as
a base. Now I am hitting an issue when trying to make it work with
libhybris device. On that device, I have GLESv2 and would need Qt that
is not linked to libGL. Is such Qt available for ARM on Fedora? Or
should I recompile
12 matches
Mail list logo
