Closed raerne closed 5 years ago
Over to @msisov, who should be back in a couple of weeks. As for the wayland-scanner error, it's been fixed again in #278
Hi,
if you use "use_system_minigbm=false", you have to specify exact driver to let the minigbm choose "right" implementation. https://cs.chromium.org/chromium/src/third_party/minigbm/BUILD.gn?q=use_system_minigbm&dr=C&l=16. Otherwise, gbm_create_device just fails, and Chromium falls back to software rendering (when --in-process-gpu is not used), or it uses wl_egl_surface (when --in-process-gpu is used).
I suppose this can be closed
Hello
I finally got chromium to compile with the following setup
To be able to compile I had to set the following gn arguments
notice the
use_system_minigbm
is set to false, otherwise it didn't compile. Now running chromium as root gives me the following outputFrom issue #214 i see that i can fix this using the
--in-process-gpu
flag, however I am not sure how this affects (or disables) the hardware acceleration. Also the effect of the system/non-system gbm / minigbm / drm arguments during the build is a bit confusing to me.Any help would be appreciated. Ramon