Comme=
nt # 42
on bug 11078=
1
from Andrew Randrianasulu
(In reply to Rui Salvaterra from comment #41)
> Hi, guys
>=20
> I haven't tried Marek's solution yet. It's the first time I build Mesa=
from
> scratch and I've never used Meson before, so I'm studying along the wa=
y. I
> applied the patch, configured with no DRI drivers and only the r300g d=
river,
> compiled and installed to the default location
> (/usr/local/lib/x86_64-linux-gnu, it seems). Unfortunately, glxinfo ca=
n't
> find the libraries when I point the environment variables to them, so =
I must
> have done something stupid. Will dig deeper.
> (I know this isn't a developer support thread, I just wanted you to kn=
ow I
> haven't given up or stopped!)
meson actually accepts prefix , so I use it like this (from BUILD dir inside
mesa tree):
meson ../ --prefix=3D/usr/X11R7 rest_of_options (obviously, for x86-64 pref=
ix
will be diffeent, I just wanted to say I have non-standard X prefix and ins=
tall
mesa into it just fine)
full line in my case looks like:
meson ../ --prefix=3D/usr/X11R7 --strip --buildtype debugoptimized -Degl=3D=
true
-Ddri-drivers=3Dr100,r200,i965,nouveau -Dplatforms=3Ddrm,x11
-Dgallium-drivers=3Di915,r600,radeonsi,swrast,virgl,nouveau,r300
-Dvulkan-drivers=3Damd,intel -Dgallium-nine=3Dtrue -Dgallium-opencl=3Dicd
-Dgallium-va=3Dtrue -Dgallium-xvmc=3Dtrue -Dgallium-xa=3Dfalse
You probably want to add --reconfigure if you re-run meson after some git p=
ull
from same BUILD directory.