[Pkg-chromium-maint] Chromium browser with h264 support

Roy Kollen Svendsen svendsen at noisolation.com
Fri Jul 14 12:41:30 UTC 2017


Hi,

Thanks for your great work on getting chromium browser to support h264 on
raspberry pi.

I am trying to build chromium browser for raspberry pi 3 through yocto
using meta-raspberrypi.

The version(chromium-54.0.2810.2) is older than what is used in
rasbian(57.0.2987.98-1~deb8u1).

I get it to build and run but i get some error messages:

raspberrypi3:/usr/bin/chromium$ DISPLAY=:0.0 ./chrome

[691:691:0712/124452:ERROR:gl_surface_glx.cc(383)] glxQueryVersion failed
[691:691:0712/124452:ERROR:gl_initializer_x11.cc(130)]
GLSurfaceGLX::InitializeOneOff failed.
[691:691:0712/124452:ERROR:gpu_child_thread.cc(348)] Exiting GPU process
due to errors during initialization
[662:681:0712/124453:ERROR:browser_gpu_channel_host_factory.cc(123)] Failed
to launch GPU process.
[662:681:0712/124453:ERROR:browser_gpu_channel_host_factory.cc(123)] Failed
to launch GPU process.
[662:662:0712/124458:ERROR:navigation_entry_screenshot_manager.cc(141)]
Invalid entry with unique id: 1
[1:8:0712/124501:ERROR:WaitUntilObserver.cpp(144)] Not implemented reached
in void blink::WaitUntilObserver::reportError(const blink::ScriptValue&)
[662:775:0712/124505:ERROR:object_proxy.cc(583)] Failed to call method:
org.freedesktop.UPower.EnumerateDevices: object_path=
/org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.UPower was not provided


And i can't get h264 support in webrtc for encoding and decoding.

I've tried the following two  configurations without luck:

#PREFERRED_PROVIDER_virtual/libgl = "mesa-gl"
#PREFERRED_PROVIDER_virtual/libgles2 = "userland"
#PREFERRED_PROVIDER_virtual/egl = "userland"
#PREFERRED_PROVIDER_virtual/mesa = "mesa-gl"

PREFERRED_PROVIDER_virtual/libgl = "mesa"
PREFERRED_PROVIDER_virtual/libgles2 = "mesa"
PREFERRED_PROVIDER_virtual/egl = "mesa"
PREFERRED_PROVIDER_virtual/mesa = "mesa"

And the following package configs..

#PACKAGECONFIG ??= "use-egl build-chromedriver"
PACKAGECONFIG ??= "use-egl build-chromedriver proprietary-codecs kiosk-mode"

I have downloaded your source-packages for chromium-browser for raspberry
pi.

I was hoping you could point me in the right direction.

1. Is it possible to get h264 support in chromium-54.0.2810.2 on raspberry
pi?

2. What build parameters do I need?

2.1 I see you use the following parameters:

is_clang=false
clang_use_chrome_plugins=false
target_extra_ldflags=\"-Wl,--stats\"
target_extra_cxxflags=\"-fno-delete-null-pointer-checks\"
host_cpu=arm
is_debug=false
use_gtk3=false
use_ozone=false
use_gconf=false
use_sysroot=false
use_vulcanize=false
use_gnome_keyring=false
rtc_libvpx_build_vp9=false
treat_warnings_as_errors=false
enable_nacl=false
enable_nacl_nonsfi=false
enable_google_now=false
enable_hangout_services_extension=false
enable_iterator_debugging=false
gold_path=\"\"
linux_use_bundled_binutils=false
use_gio=true
use_gold=true
use_pulseaudio=true
link_pulseaudio=true
enable_widevine=true
proprietary_codecs=true
ffmpeg_branding=\"Chrome\"
fieldtrial_testing_like_official_build=true

--exclude chrome-sandbox

2.2 Am I missing any important parameters?

2.3 What are the most important parameters in my case?


3. What providers are necessary for videocore support and for h264 support?




Best regards,
Roy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-chromium-maint/attachments/20170714/740940f2/attachment.html>


More information about the Pkg-chromium-maint mailing list