When building app-text/mupdf with uSE="opengl", please make mupdf using the mupdf-gl port by default. It is advised to use that port over mupdf-x11 as the GL-based port beside using OpenGL has lot of advanced shortcuts like smart browsing and full history stack known from vim. Here with Installed versions: 1.10a-r2(09:07:30 06.04.2017)(X curl opengl openssl -javascript -libressl -static -static-libs -vanilla) the symlink is using the x11 port by default: /usr/bin/mupdf -> mupdf-x11* The GL port should work on modern Linux using mesa and most probably gallium rendering and thus should be the default. Reproducible: Always
commit 7e51c0aae90d1611ff7674963a0e3989e6124e5d Author: Michael Weber <xmw@gentoo.org> Date: Fri Apr 28 11:33:04 2017 +0200 app-text/mupdf: Version bump (bug 616652), make mupdf-gl default if available (bug 616654), thanks Massimo Burcheri. Package-Manager: Portage-2.3.5, Repoman-2.3.2 app-text/mupdf/Manifest app-text/mupdf/files/mupdf-1.11-CFLAGS.patch app-text/mupdf/files/mupdf-1.11-openssl-curl-x11.patch app-text/mupdf/files/mupdf-1.11-system-glfw.patch app-text/mupdf/mupdf-1.11.ebuild
Just fyi `mupdf` fails to launch in the scenario where `media-libs/glfw USE=wayland` but the Gnome session is launched via X11 fallback. `mupdf` launch the fails with `glfw` failing to connect to a Wayland display.
I think I found a typo in mupdf-1.11-openssl-curl-x11.patch. On line 27, it says: +WANT_X!! ?= yes I think that should be: +WANT_X11 ?= yes as the next line says: +ifeq "$(WANT_X11)" "yes"
