Comment # 42
on bug 110781
from Andrew Randrianasulu
(In reply to Rui Salvaterra from comment #41) > Hi, guys > > 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 way. I > applied the patch, configured with no DRI drivers and only the r300g driver, > compiled and installed to the default location > (/usr/local/lib/x86_64-linux-gnu, it seems). Unfortunately, glxinfo can'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 know 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=/usr/X11R7 rest_of_options (obviously, for x86-64 prefix will be diffeent, I just wanted to say I have non-standard X prefix and install mesa into it just fine) full line in my case looks like: meson ../ --prefix=/usr/X11R7 --strip --buildtype debugoptimized -Degl=true -Ddri-drivers=r100,r200,i965,nouveau -Dplatforms=drm,x11 -Dgallium-drivers=i915,r600,radeonsi,swrast,virgl,nouveau,r300 -Dvulkan-drivers=amd,intel -Dgallium-nine=true -Dgallium-opencl=icd -Dgallium-va=true -Dgallium-xvmc=true -Dgallium-xa=false You probably want to add --reconfigure if you re-run meson after some git pull from same BUILD directory.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
