On Tue, 18 Feb 2014 11:12:01 -0800
Bill Spitzak spit...@gmail.com wrote:
Maybe you can correct my guess as to how all this software talks to each
other:
1. An EGL-using wayland client talks to mesa's libEGL.
You have to ensure it actually gets the Mesa version of libEGL.
2. Somehow mesa
On Tue, 18 Feb 2014 23:58:41 -0800
Bill Spitzak spit...@gmail.com wrote:
Okay, a bit more luck, in that I can compile weston.
I mostly discovered that there are parts of mesa you just cannot turn
off, no matter how much you are certain they are not used. Mesa
internally has calls into
Okay, a bit more luck, in that I can compile weston.
I mostly discovered that there are parts of mesa you just cannot turn
off, no matter how much you are certain they are not used. Mesa
internally has calls into various functions in these modules from others
so they cannot be removed.
My
On Fri, 07 Feb 2014 09:54:36 -0800
Bill Spitzak spit...@gmail.com wrote:
Okay, removing everything with gallium in it's name from the
install worked. But make install in mesa puts it all back!
Would clean fix this?
What I am really interested in is the proper configure line for
mesa. I am
In order to try to compile the new xserver for wayland, I updated mesa
to the latest git version, and now wayland does not work at all!
Considering it has worked for a long time I would like to try to fix
this, it is really unfortunate.
It does appear the problem is in egl gallium and it's
The new mesa you built has no egl_gallium.so (since you have
--disable-gallium-egl), but you have not removed the old egl_gallium.so,
and it tries to load it, since it is here.
Axel Davy
Le 07/02/2014 18:30, Bill Spitzak a écrit :
In order to try to compile the new xserver for wayland, I
