I am wondering about the libav dependency for chromium. I don't think it is required anymore and I have a patch(0dff75b) to remove it, but I wanted to make sure I wasn't missing anything.

Chromium has had its own copy of ffmpeg since version 44.
I have built it for x86 and x86_64 with libav removed and have seen no issues.

I am not setup to do a pull request, so I will leave it to you guys to implement this, or not.

I compiled firefox in OE, but it crashed at first startup. Subsequently started, but very unstable.
I also compiled seamonkey, which has the same code base, and it exhibited exactly the same symptoms.

I have chased down all of the reasons for the instability.
Firstly, do not use system cairo, as advised by LFS:
http://www.linuxfromscratch.org/blfs/view/7.9/xsoft/firefox.html

Quoting:

From firefox-40, using system cairo causes firefox to crash

frequently when it is doing background rendering in a tab.

#ac_add_options --enable-system-cairo

That affects stability while running. The crash at first startup, and also instability while running (crashing on certain sites, such as sourceforge.net), is due to using system icu, which is version 58.2.
You need to use the internal icu, OR, use icu 56.1 from krogoth.

What I did is get the icu 56.1 recipe from krogoth, into my layer, and I also added patches from seamonkey's internal icu -- that is seamonkey 2.48b1. Both seamonkey and firefox internally use icu 56.1.

What I cannot tell you is whether those icu patches from seamonkey are a factor in the stability or not.

Anyway, I used icu from krogoth and the icu patches from seamonkey, and internal cairo, compiled seamonkey, and it has been rock solid.

Now, sqlite. firefox cannot use system sqlite, because it can been configured with the wrong options. This is a detail that has been sorted out by distros such as Ubuntu, but not by OE. But, I will probably have to post to openembedded-core github about that.

Regards,
Barry

Hi,
I building recipes for Chromium on Yocto Toaster Morty
2.2.1, see the message below :
Required build target 'rpi-basic-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['rpi-basic-image', 'libxss']

There is no "libxss" in OpenEmbedded Layer Index:
libxss, no matching recipes in database.

Why is it integrated in this recipe?
DEPENDS += "xextproto gtk+ libxi libxss"

HI guys:
i meet a problem when do the compile operation on yocto project with command "bitbake chromium-ozone-wayland", the error verbose as follows:
[5/735] python ../../build/gn_run_binary.py yocto_native/transport_security_state_generator ../../net/http/transport_security_state_static.json ../../net/http/transport_security_state_static.pins ../../net/http/transport_security_state_static.template gen/net/http/transport_security_state_static.h
| FAILED: gen/net/http/transport_security_state_static.h

it seems somthing wrong happen when genenrate the automatic file transport_security_state_static.h, so
how to dealt with this？

much appreciate your help.

Hi, I'm using the latest meta-browser(master) . It fails during the build of chromium-x11_68.0.3440.106 for aarch64 (hikey960). I'm using the following configurations.

Build Configuration:
BB_VERSION = "1.36.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-16.04"
TARGET_SYS = "aarch64-linaro-linux"
MACHINE = "hikey960"
DISTRO = "rpb"
DISTRO_VERSION = "2.4+linaro"
TUNE_FEATURES = "aarch64"
TARGET_FPU = ""
meta-rpb = "HEAD:96d618f2597d18da1fc868a0f801854f0f2161e6"
meta-oe
meta-gnome
meta-xfce
meta-initramfs
meta-multimedia
meta-networking
meta-webserver
meta-filesystems
meta-perl
meta-python = "HEAD:352531015014d1957d6444d114f4451e241c4d23"
meta-browser-master = ":"
meta-qt5 = "HEAD:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"
meta-virtualization = "HEAD:b704c689b67639214b9568a3d62e82df27e9434f"
meta-clang = "HEAD:533f882e77714a231a1cef985fd9bb7f56e44145"
meta-96boards = "HEAD:7f473a9d0028911a04b6e797d5dc9a0c638bfac1"
meta-intel = "HEAD:9baa0974b397a8520d548a5f7b768db1acc34177"
meta-qcom = "HEAD:432e3b1d881bf91a5f5537387a68d3e2cb88bccd"
meta-st-cannes2 = "HEAD:88fadd917c3f5b7e0feba318aa2d7bbb596eb95f"
meta-ti = "HEAD:1f781998aa2d3f3526aa6e3c7a8384bcf54b800d"
meta-linaro
meta-linaro-toolchain
meta-optee = "HEAD:75dfb67bbb14a70cd47afda9726e2e1c76731885"
meta-backports = "HEAD:4b51a7a0e950ff2d4bd62e045471a44dc940ad62"
meta = "HEAD:bdf13518e79ab949c4320226a399ee4a3913ee30"

The gcc version is 7.1
I get the following error | ninja: build stopped: subcommand failed.
The complete log is attached here:
log.do_compile.log

Thanking you in advance.
Regards:Nishant Poorswani

As I work on the next upcoming Chromium milestone, once again I find myself spending most of my time fighting GCC 5 and trying to keep the build working with it. Sometimes it's a bug in the compiler itself, most of the time it's a bug in libstdc++. chromium-gcc5-workarounds.patch keeps growing, and I think things will only get worse with each new milestone.

Right now, the M66 build is broken with GCC 5 due to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77334. The bug says GCC 5.5.0 contains a fix, but I don't think anyone's willing to update GCC in Yocto's pyro branch at this point.

I can either spend more time trying to find a workaround (which will most likely also affect the build with other compilers too), or decide we only support GCC 6.4.0 and above (essentially, the default compiler versions for pyro and later branches).

I remember we originally started supporting GCC 5 to accommodate the needs of the Igalians, but it's not clear if they still need it or not.

Lately meta-browser master fails to build against poky master:

Note that proprietary-codecs option is enabled:

PACKAGECONFIG_append = " proprietary-codecs"

Log excerpt:

[7577/33157] x86_64-poky-linux-g++  -m64 -march=nehalem -mtune=generic -mfpmath=sse -msse4.2 -fstack-protector-strong  -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0/recipe-sysroot -MMD -MF obj/third_party/openh264/common/WelsThreadPool.o.d -DX86_ASM -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../../third_party/openh264/src/codec/api/svc -I../../third_party/openh264/src/codec/common/arm -I../../third_party/openh264/src/codec/common/inc -I../../third_party/openh264/src/codec/common/src -I../.. -Igen -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 -fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-missing-field-initializers -Wno-unused-parameter -Wno-format -Wno-header-hygiene -Wno-unused-function -Wno-unused-value -std=gnu++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -Wno-narrowing  -O2 -pipe -feliminate-unused-debug-types -fdebug-prefix-map=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0=/usr/src/debug/chromium-x11/68.0.3440.106-r0 -fdebug-prefix-map=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0/recipe-sysroot= -fdebug-prefix-map=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0/recipe-sysroot-native= -g1 -c ../../third_party/openh264/src/codec/common/src/WelsThreadPool.cpp -o obj/third_party/openh264/common/WelsThreadPool.o
FAILED: obj/third_party/openh264/common/WelsThreadPool.o 
x86_64-poky-linux-g++  -m64 -march=nehalem -mtune=generic -mfpmath=sse -msse4.2 -fstack-protector-strong  -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0/recipe-sysroot -MMD -MF obj/third_party/openh264/common/WelsThreadPool.o.d -DX86_ASM -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../../third_party/openh264/src/codec/api/svc -I../../third_party/openh264/src/codec/common/arm -I../../third_party/openh264/src/codec/common/inc -I../../third_party/openh264/src/codec/common/src -I../.. -Igen -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 -fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-missing-field-initializers -Wno-unused-parameter -Wno-format -Wno-header-hygiene -Wno-unused-function -Wno-unused-value -std=gnu++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -Wno-narrowing  -O2 -pipe -feliminate-unused-debug-types -fdebug-prefix-map=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0=/usr/src/debug/chromium-x11/68.0.3440.106-r0 -fdebug-prefix-map=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0/recipe-sysroot= -fdebug-prefix-map=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0/recipe-sysroot-native= -g1 -c ../../third_party/openh264/src/codec/common/src/WelsThreadPool.cpp -o obj/third_party/openh264/common/WelsThreadPool.o
cc1plus: error: -Wformat-security ignored without -Wformat [-Werror=format-security]
cc1plus: warning: unrecognized command line option '-Wno-header-hygiene'
cc1plus: some warnings being treated as errors
[7578/33157] python ../../third_party/yasm/run_yasm.py yasm -DPIC -felf64 -m amd64 -I../../third_party/libvpx/source/config -I../../third_party/libvpx/source/config/linux/x64 -I../../third_party/libvpx/source/libvpx -I. -I../.. -Igen -DCHROMIUM -o obj/third_party/libvpx/libvpx_yasm/highbd_sad4d_sse2.o ../../third_party/libvpx/source/libvpx/vpx_dsp/x86/highbd_sad4d_sse2.asm
[7579/33157] x86_64-poky-linux-gcc  -m64 -march=nehalem -mtune=generic -mfpmath=sse -msse4.2 -fstack-protector-strong  -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0/recipe-sysroot -MMD -MF obj/third_party/libvpx/libvpx_intrinsics_sse2/fwd_txfm_sse2.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -I../../third_party/libvpx/source/config -I../../third_party/libvpx/source/config/linux/x64 -I../../third_party/libvpx/source/libvpx -msse2 -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 -fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-function -Wno-sign-compare -std=gnu11  -O2 -pipe -feliminate-unused-debug-types -fdebug-prefix-map=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0=/usr/src/debug/chromium-x11/68.0.3440.106-r0 -fdebug-prefix-map=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0/recipe-sysroot= -fdebug-prefix-map=/home/gitlab-runner/yocto/mediacoder-yocto/build/tmp/work/corei7-64-poky-linux/chromium-x11/68.0.3440.106-r0/recipe-sysroot-native= -g1 -c ../../third_party/libvpx/source/libvpx/vpx_dsp/x86/fwd_txfm_sse2.c -o obj/third_party/libvpx/libvpx_intrinsics_sse2/fwd_txfm_sse2.o
ninja: build stopped: subcommand failed.

Full log:
log.do_compile.9181.log

Have tested chromium-x11 with quite recent master layers. It was build with

PACKAGECONFIG = "use-egl impl-side-painting proprietary-codecs"

for Raspi3.

On a fresh image chromium starts but as soon as I open e.g https://github.com it crashes. All further starts crash immediately. If I delete $HOME/.config/chromium I can start chromium again but moving to https://github.com crashes.

So I started chromium by console and get:

[2263:2263:1221/015335.950665:ERROR:gl_implementation.cc(241)] Failed to load /usr/lib/chromium/libGLESv2.so: /usr/lib/chromium/libGLESv2.so: cannot open shared object file: No such file or directory
[2263:2263:1221/015335.957888:ERROR:gpu_child_thread.cc(254)] Exiting GPU process due to errors during initialization
[2213:2247:1221/015335.971247:ERROR:browser_gpu_channel_host_factory.cc(108)] Failed to launch GPU process.
Bus error (core dumped)

I did some investigations:

• On Target: Creating a link /usr/lib/chromium/libGLESv2.so to /usr/lib//libGLESv2.so.2 did not change anything
• In OE-Workdir: Have no idea if this is something of importance but I found many entries like 'solibs = ./libEGL.so ./libGLESv2.so' in the created ninja files. The error message path is libexec / /usr/lib/chromium so this might cause chromium look there.

i got the process tree after launch the chromium process and open a website,
i found there is only two process on the hierarchy of chromium, that is the browser(3211) and render (3265), as you see below.

that is not same like chromium on PC environments, there would be a extra gpu process in the same scenario, so, what happens to chromium? is this mean the gpu acceleration did not open?
thanks for your help.

|-ash(1249)---chromium-bin(3204)-+-cat(3208)
| |-cat(3209)
| |-chromium-bin(3211)---chromium-bin(3265)-+-{Chrome_ChildIOT}(3271)
| | |-{CompositorTileW}(3278)
| | |-{CompositorTileW}(3279)
| | |-{CompositorTileW}(3280)
| | |-{Compositor}(3277)
| | |-{File}(3274)
| | |-{GpuMemoryThread}(3272)
| | |-{ScriptStreamerT}(3285)
| | |-{TaskSchedulerRe}(3267)
| | |-{TaskSchedulerRe}(3268)
| | |-{TaskSchedulerRe}(3269)
| | |-{TaskSchedulerRe}(3270)
| | |-{TaskSchedulerRe}(3282)
| | |-{TaskSchedulerRe}(3291)
| | |-{TaskSchedulerRe}(3292)
| | -{TaskSchedulerSe}(3266) | |-{AudioThread}(3252) | |-{BrowserWatchdog}(3253) | |-{Chrome_HistoryT}(3257) | |-{Chrome_IOThread}(3234) | |-{CompositorThrea}(3251) | |-{CompositorTileW}(3241) | |-{CrShutdownDetec}(3215) | |-{D-Bus thread}(3213) | |-{GpuIOThread}(3250) | |-{GpuMemoryThread}(3240) | |-{GpuThread}(3246) | |-{GpuThread}(3247) | |-{GpuThread}(3248) | |-{GpuThread}(3249) | |-{NetworkChangeNo}(3212) | |-{Startup watchdo}(3262) | |-{TaskSchedulerBa}(3221) | |-{TaskSchedulerBa}(3222) | |-{TaskSchedulerBa}(3223) | |-{TaskSchedulerBa}(3224) | |-{TaskSchedulerFo}(3225) | |-{TaskSchedulerFo}(3226) | |-{TaskSchedulerFo}(3227) | |-{TaskSchedulerFo}(3228) | |-{TaskSchedulerFo}(3259) | |-{TaskSchedulerFo}(3260) | |-{TaskSchedulerFo}(3261) | |-{TaskSchedulerFo}(3273) | |-{TaskSchedulerSe}(3220) | |-{TaskSchedulerSi}(3229) | |-{TaskSchedulerSi}(3230) | |-{TaskSchedulerSi}(3231) | |-{TaskSchedulerSi}(3232) | |-{TaskSchedulerSi}(3233) | |-{TaskSchedulerSi}(3237) | |-{TaskSchedulerSi}(3256) | |-{inotify_reader}(3219) | |-{mus}(3245) | |-{renderer_crash_}(3264) | -{sandbox_ipc_thr}(3210)

I am using branch ozone/wayland/67.0.33.., and recipe chromium-x11.bb

How can I invoke chromium without providing the "--no-sandbox" argument?

hi folks:
i use the latest chromium ozone wayland port 71 in your igilia repo .
when i launch it with command"
chromium --no-sandbox --kiosk
and found that the address bar and tools menu still hung it and did not work in full screen mode.

that is different from the previous version of 70, so, is this expected?

Additional context in this oe-devel thread.

We're currently still packaging Chromium M54 and Chromium M53 + ozone-wayland, both of which are ancient releases by Chromium's standards.

I've done the work to move the existing recipe to M62 (the current stable milestone upstream) based on my own recipe, we now need to break up the ~60 commits in my branch into logical chunks and start merging them.

Depending on how long it takes to get everything merged, we might need to move to M63 directly.

This is a meta issue to track everything we need to do in terms of splitting up the existing commits in my chromium62 branch:

• Drop the ozone-wayland recipe. oz-wl has been unmaintained upstream for years and there is no point in trying to get it to work with M62 or later. Doing so allows us to greatly simplify the rest of the recipe.
• Actual recipe bug fixes that also apply to M54.
• Remove unnecessary patches, as well as patches that can be replaced by gyp options.
• Recipe simplification: drop a few checks for things we build unconditionally, stop setting a few variables here and there, adjust installation directory layout.
• Adjust recipe dependencies: add implicit ones, remove unnecessary ones.
• Move to GN, still on M54. Also requires some additional recipe simplification.
• Move to M62 (should be easy once everything else is done).

the chromium ozone port always show panic message of the kernel , but it seems not affect the normal use, it is very easy to duplicate during press the "exit" button of the chromium .
another scenario of showing this message is openning the second session of chromium on terminal.
so, could i get some hints on how to dealt with this issue? thanks for your support!

[ 158.384442] chromium-bin[2130]: unhandled level 1 translation fault (11) at 0x00000074, esr 0x92000045
[ 158.394836] pgd = ffffffc00f541000
[ 158.398656] [00000074] *pgd=0000000000000000, *pud=0000000000000000
[ 158.405670]
[ 158.407330] CPU: 1 PID: 2130 Comm: chromium-bin Tainted: G O 4.4.89 #212
[ 158.416053] Hardware name: sun50iw1 (DT)
[ 158.420429] task: ffffffc0232a7300 ti: ffffffc02a250000 task.ti: ffffffc02a250000
[ 158.428765] PC is at 0x7f8c0319d4
[ 158.432477] LR is at 0x7f8c02dee8
[ 158.436185] pc : [<0000007f8c0319d4>] lr : [<0000007f8c02dee8>] pstate: 80000000
[ 158.444423] sp : 0000007fc57aa800
[ 158.448123] x29: 0000007fc57aa800 x28: 0000007fc57aa968
[ 158.454054] x27: 0000007f8c2324e0 x26: 0000000000000000
[ 158.459979] x25: 0000007f8c1c63f8 x24: 0000000000000000
[ 158.465926] x23: 0000007f8c1c6400 x22: 0000007f8c1cd000
[ 158.471854] x21: 0000007f8ca9f000 x20: 0000007f280064f8
[ 158.477797] x19: 0000007f8c044558 x18: 000000000000073c
[ 158.483725] x17: 0000007f8c031980 x16: 0000007f8c044040
[ 158.489676] x15: 0000007f8bad2d00 x14: 0000007f8badfd98
[ 158.495607] x13: 0000000000000000 x12: 0000000000000000
[ 158.501549] x11: 0000000000000000 x10: 0101010101010101
[ 158.507522] x9 : 0000000000000039 x8 : 0000000000000000
[ 158.513484] x7 : 0000007f2c0097d0 x6 : 0000000000000001
[ 158.519466] x5 : 0000007f8b8aeee0 x4 : 00000000feffffff
[ 158.525469] x3 : 0000007f8c044558 x2 : 000000000000000e
[ 158.531393] x1 : 0000000000000004 x0 : 0000000000000000
[ 158.537335]

Hi everyone,

This is not properly speaking an issue on the meta-browser but still I think here is a suitable place to get an answer from people who master it. I am (simply) trying to build a YOCTO image for my NXP Sabre i.MX6QP SD board, that includes Chromium. Here is what I do (from scratch and based on NXP Yocto User's Guide):

mkdir fsl-release-bsp_imx-4.1.15-2.1.0_ga/
cd fsl-release-bsp_imx-4.1.15-2.1.0_ga/
repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth -m imx-4.1.15-2.1.0.xml
repo sync
DISTRO=fsl-imx-x11 MACHINE=imx6qpsabresd source fsl-setup-release.sh -b build-x11
# add the following two lines in conf/local.conf
# CORE_IMAGE_EXTRA_INSTALL += " chromium libexif"
# LICENSE_FLAGS_WHITELIST = "commercial"
bitbake fsl-image-gui

This fails with the following messages:

ERROR: Nothing RPROVIDES 'chromium' (but /data/i.MX6_refs/fsl-release-bsp_imx-4.1.15-2.1.0_ga/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/images/fsl-image-gui.bb RDEPENDS on or otherwise requires it)
ERROR: chromium was skipped: Recipe is blacklisted: BROKEN: fails to build with gcc-6
NOTE: Runtime target 'chromium' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['chromium']
ERROR: Required build target 'fsl-image-gui' has no buildable providers.
Missing or unbuildable dependency chain was: ['fsl-image-gui', 'chromium']

However, /data/i.MX6_refs/fsl-release-bsp_imx-4.1.15-2.1.0_ga/sources/meta-browser exists with content of the repo. This is a kind of dead-end to me as asking support from my reseller or NXP, the answer was "we do no support meta-browser layer". Additionally, I could not find any useful help on the web (most of the time similar errors seem to be related to the commercial license I already put on whitelist).

Note that without modifying the conf/local.conf file, I produce a working image... but without Chromium. So I guess my procedure is fine, only the way I add the meta-browser layer and chromium feature is wrong.

Also, when basing my YOCTO on a previous release, producing the image works fine (repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-3.14.52-1.1.0_ga).

Can you provide any help? What am I missing in the 6 above command lines?

Thanks,

now i am porting the meta-browser on my our own platform, which only supports musl libc toolchain for reduce code size. i meet so many compile errors, basically related to the difference of glibc and musl libc,
for example, directly call "__libc_malloc" symble on chromium code and some library interface can`t be supported by musl.
so, i lost my confidence for porting rightly to the platform with muscle, has someone ever been done this?

Hi,
using the latest master (1cd38d7) fails the build of chromium-x11_67.0.3396.87 for armhf (i.MX6).

Following error occurs repeatedly (please find more details in the attached log):

error: cannot convert 'const mojo::ScopedInterfaceEndpointHandle' to 'bool' in return

I'm using following branches and configuration:

Build Configuration:
BB_VERSION           = "1.39.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-myos-linux-gnueabi"
MACHINE              = "sdimx6"
DISTRO               = "myos"
DISTRO_VERSION       = "0.0.1"
TUNE_FEATURES        = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU           = "hard"
meta
meta-poky
meta-yocto-bsp       = "master:c7c64baa411fd96886918c235b851ae3e5a6a61f"
meta-oe
meta-multimedia      = "master:4517d1c695efd0b175f4e7242e1a7bb4361527d9"
meta-java            = "master-next:c8f7e412aaee4e41ec8ff980f463536c757538d0"
meta-freescale       = "master:aa3c33cdcd9c336ec39765d5a73dc62f87393f2c"
meta-browser         = "master:1cd38d701a49eade80a04140f70d3383117b9745"

The complete do_compile log is here: log.do_compile.log

Any help is much appreciated!

regards;Richard.L

Log data follows:    
| DEBUG: Executing shell function do_configure    
| ERROR at //ui/events/BUILD.gn:80:12: Assignment had no effect.  
|   friend = [ ":*" ]  
|            ^------  
| You set the variable "friend" here and it was unused before it went  
| out of scope.  
| See //BUILD.gn:211:7: which caused the file to be included.  
|       "//ui/events:events_unittests",  
|       ^-----------------------------  
| WARNING: exit code 1 from a shell command.  
| ERROR: Function failed: do_configure 

I was followed https://github.com/Igalia/meta-browser/wiki.
When I execute bitbake chromium-ozone-wayland, above error was occured.
How can I solved this error?

i have added meta-browser to my imx6 based BSP and I am using master branch firefox 52.9 i am getting below issue .

4.060937] [] (dbs_work_handler) from [] (process_one_work+0x1ec/0x414)
[ 4.069395] r9:00000000 r8:00000000 r7:ef7bb800 r6:ef7b8900 r5:ec5f5a80 r4:ec681438
[ 4.077161] [] (process_one_work) from [] (worker_thread+0x3c/0x600)
[ 4.085271] r10:c0e02d00 r9:ffffe000 r8:ef7b8918 r7:00000008 r6:ec5f5a98 r5:ef7b8900
[ 4.093111] r4:ec5f5a80
[ 4.095666] [] (worker_thread) from [] (kthread+0x14c/0x164)
[ 4.103082] r10:ec071e98 r9:c013cb68 r8:ec5f5a80 r7:ec634000 r6:ec614780 r5:ec09c940
[ 4.110922] r4:00000000
[ 4.113485] [] (kthread) from [] (ret_from_fork+0x14/0x2c)
[ 4.120727] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c0141c90
[ 4.128566] r4:ec614780
[ 4.131130] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-

NOTE: If i remove firefox then core-image-sato is working fine. only when I add firefox then error is occur. is there any special config require.

why the meta-browser does not have the fido branch, can I add meta-browser in FIDO branch and compile. is it work?

i meet a compile issue about "libwayland-egl.so" dependency with the default bbfile of this repo.
alghough it can be skipped by add "INSANE_SKIP_${PN}+= "file_rdeps", but i dont want to do that,
why arise this error with the default chromium-ozone bbfile? how to dealt with this problem?

thanks for your support.

Initialising tasks: 100% |###########################################################################################################################################################################| Time: 0:00:13
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: chromium-ozone-wayland-64.0.3274.0.r517731.igalia.1-r0 do_package_qa: QA Issue: /usr/lib/chromium/chromium-bin contained in package chromium-ozone-wayland requires libwayland-egl.so()(64bit), but no providers found in RDEPENDS_chromium-ozone-wayland? [file-rdeps]
ERROR: chromium-ozone-wayland-64.0.3274.0.r517731.igalia.1-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: chromium-ozone-wayland-64.0.3274.0.r517731.igalia.1-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /home/zilong/WorkSpace/disk1/glibc/build/tmp/work/aarch64-poky-linux/chromium-ozone-wayland/64.0.3274.0.r517731.igalia.1-r0/temp/log.do_package_qa.3728
ERROR: Task (/home/zilong/WorkSpace/disk1/glibc/sources/meta-tina/recipes-web/recipes-browser/chromium/chromium-ozone-wayland_64.0.3274.0.r517731.igalia.1.bb:do_package_qa) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4607 tasks of which 4584 didn't need to be rerun and 1 failed.

Hi,

I'm trying to build content_shell, but I get the below error:

/home/joone/otc/yocto/poky/build/tmp/work/corei7-64-poky-linux/chromium-x11/67.0.3396.87-r0/chromium-67.0.3396.87/out/Release
| + do_compile
| + ninja -v -j 40 chrome chrome_sandbox chromedriver content_shell
|
| + cd /home/joone/otc/yocto/poky/build/tmp/work/corei7-64-poky-linux/chromium-x11/67.0.3396.87-r0/chromium-67.0.3396.87/out/Release
| + do_compile
| + ninja -v -j 40 chrome chrome_sandbox chromedriver content_shell
| ninja: error: '../../third_party/test_fonts/test_fonts/Arimo-Bold.ttf', needed by 'test_fonts/Arimo-Bold.ttf', missing and no known rule to make it
|
| ninja: error: '../../third_party/test_fonts/test_fonts/Arimo-Bold.ttf', needed by 'test_fonts/Arimo-Bold.ttf', missing and no known rule to make it
| + bb_exit_handler
| + ret=1

How can we fix this problem?

Can I compile this chrome and mozilla without x11 support if yes please say how to do
Thanks!.

hi foks:
i am using ozone-wayland port in my project, for some reasons, i need running the chromium in full screen "kiosk mode”, i run the command like that:
"chromium --no-sandbox --kiosk"
but nothing happens on the screen , it seems the lauch process has been stucked for some reason.
so, did any precondition needed for the chrome running in "kiosk" mode? please give me some hints for this, thank you!

i try to run the chromium browser more than one inistances, but got the error output from the second one, the error ouput as follows.
so, did this port support more than one instance running simultantously like chromium on the desktop ?
thanks for your support.!
root@tulip-mozart:/# chromium --no-sandbox
[1554:1554:0101/051007.512147:ERROR:browser_process_platform_part_ozone.cc(20)] Not implemented reached in virtual void BrowserProcessPlatformPart::RegisterInProcessServices(content::ContentBrowserClient::StaticServiceMap*)
[1554:1584:0101/051007.642023:ERROR:xkb_keyboard_layout_engine.cc(694)] Not implemented reached in virtual bool ui::XkbKeyboardLayoutEngine::SetCurrentLayoutByName(const string&)
[1554:1585:0101/051007.647838:ERROR:gl_surface_egl.cc(314)] eglChooseConfig failed with error EGL_BAD_ATTRIBUTE
Created new window in existing browser session.
Segmentation fault
root@tulip-mozart:/# chromium --no-sandbox
[1612:1612:0101/051026.699049:ERROR:browser_process_platform_part_ozone.cc(20)] Not implemented reached in virtual void BrowserProcessPlatformPart::RegisterInProcessServices(content::ContentBrowserClient::StaticServiceMap*)
[1612:1642:0101/051026.827107:ERROR:xkb_keyboard_layout_engine.cc(694)] Not implemented reached in virtual bool ui::XkbKeyboardLayoutEngine::SetCurrentLayoutByName(const string&)
[1612:1643:0101/051026.835510:ERROR:gl_surface_egl.cc(314)] eglChooseConfig failed with error EGL_BAD_ATTRIBUTE
Created new window in existing browser session.
Segmentation fault

i meed crash issue after launch browser, i am not sure if the launch command is right,
what am i done is on serial terminal, just launch the browser with chromium command like that:
#chromium
is that right? any parameter need to added?

hi body:
did he x11 and wayland port supports the webrtc feature？

i am porting the chromium-ozone-wayland to my target platform, but it immediately crashed when launch "chromium" command, so, has someone meet this before?
thanks for your help.
root@tulip-mozart:/# chromium
[89124.065882] chromium-bin[1542]: unhandled level 3 translation fault (11) at 0x7fd4339fd0, esr 0x92000047
[89124.076458] pgd = ffffffc029b2d000
[89124.080287] [7fd4339fd0] *pgd=0000000063feb003, *pud=0000000063feb003, *pmd=000000006a199003, *pte=0000000000000000
[89124.091897]
[89124.093551] CPU: 0 PID: 1542 Comm: chromium-bin Tainted: G O 4.4.89 #27
[89124.102169] Hardware name: sun50iw1 (DT)
[89124.106521] task: ffffffc029424980 ti: ffffffc029c9c000 task.ti: ffffffc029c9c000
[89124.114849] PC is at 0x5593569a10
[89124.118523] LR is at 0x5593569a68
[89124.122218] pc : [<0000005593569a10>] lr : [<0000005593569a68>] pstate: 80000000
[89124.130436] sp : 0000007fd433a000
[89124.134109] x29: 0000007fd433a000 x28: 0000007f9d2c7000
[89124.140024] x27: 0000007f9c7a8320 x26: 0000007f9d2c53d0
[89124.145923] x25: 0000007f9d2c7000 x24: 0000007fd4b38b30
[89124.151841] x23: 0000000000000001 x22: 0000000000011c00
[89124.157739] x21: 000000559a44603c x20: 0000005599f51f30
[89124.163660] x19: 0000007f9c7b3d10 x18: 0000000000000800
[89124.169558] x17: 0000005593569a10 x16: 0000007f9c7b3a40
[89124.175474] x15: 0000000000000000 x14: 0000007f9d217d00
[89124.181396] x13: 0000005590c45ac8 x12: 0000000000000018
[89124.187295] x11: 0000000000000010 x10: 0000007f9d2c7f30
[89124.193218] x9 : 0000000000000010 x8 : 0000005599eea688
[89124.199121] x7 : 00000000ffffffff x6 : ffffffffffffffff
[89124.205037] x5 : 00000000000007f8 x4 : 0000007f9d276be8
[89124.210959] x3 : 0000005593569e08 x2 : 0000000000000000
[89124.216859] x1 : 0000000000011c00 x0 : 0000000000011c00
[89124.222777]
Segmentation fault

[ 62.994655] sunxi-bt bt: check bluetooth io_regulator voltage: 1800000

[1952:1973:0101/000223.543868:ERROR:bus.cc(395)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[1952:1952:0101/000223.797757:ERROR:browser_process_platform_part_ozone.cc(20)] Not implemented reached in virtual void BrowserProcessPlatformPart::RegisterInProcessServices(content::Content)
[1952:2006:0101/000224.044825:ERROR:xkb_keyboard_layout_engine.cc(694)] Not implemented reached in virtual bool ui::XkbKeyboardLayoutEngine::SetCurrentLayoutByName(const string&)
[1952:2007:0101/000224.061897:ERROR:gl_surface_egl.cc(314)] eglChooseConfig failed with error EGL_BAD_ATTRIBUTE
[1952:2028:0101/000224.438268:ERROR:bus.cc(395)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[1952:2006:0101/000224.547272:ERROR:wayland_keyboard.cc(140)] Not implemented reached in static void ui::WaylandKeyboard::RepeatInfo(void*, wl_keyboard*, int32_t, int32_t)
[1952:2007:0101/000224.764758:ERROR:gl_surface_egl.cc(314)] eglChooseConfig failed with error EGL_BAD_ATTRIBUTE
[1952:1952:0101/000224.774233:ERROR:layer_tree_host_impl.cc(2508)] Forcing zero-copy tile initialization as worker context is missing
[1952:2031:0101/000225.007757:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for www.gstatic.com failed err=-8181
[1952:2031:0101/000225.145284:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for translate.googleapis.com failed err=-8181
[2035:2061:0101/000225.376187:ERROR:layer_tree_host_impl.cc(2508)] Forcing zero-copy tile initialization as worker context is missing
[1952:2031:0101/000230.349124:ERROR:cert_verify_proc_nss.cc(922)] CERT_PKIXVerifyCert for www.google.com failed err=-8181

did the firefox port of this repo suppport wayland-backend? as i know, the offical release of firefox supports wayland already.

hi folks:
the ozone-wayland port of chromium in this repo is version 64,
but another repo in "https://github.com/Igalia/meta-browser/tree/ozone/wayland/70.0.3509.0.r579363/recipes-browser/chromium" newer one, did the newer version 70 could be used replace version 64?
i meet some problems on version 64 in my project, could i use the 70 version to take a trial?

thanks for your reply!

hi guys:
during the test i found some website cant be reached every time, for example "http://www.baidu.com"
cant be reached.

but most of the website cant be visit, such as:
http://html5test.com
http://www.ifent.com
http://www.qq.com

and so on , so, seems not the problem of the network, is there any clue for this issue?

Hi,

First of all thanks for this layer — super practical and well maintained.

In my custom layer, I have a recipes-browser/chromium/chromium-x11_%.bbappend file with the following content :

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
PACKAGECONFIG = "use-egl kiosk-mode proprietary-codecs"

... but chromium doesn't start in kiosk-mode — it seems these knobs are not taken into account.
Am I missing something ?

Thanks a lot !

Hi!

As you already know, Igalia has been working on the Chromium browser to add Wayland support utilizing the newest mus/ozone (ui service) efforts being done in the Chromium project's upstream repositories. At the moment, the upstream version of Chromium supports Wayland on ChromeOS only (so called internal window mode, when mus works with ash window system (aka mustash), which plays a role of a window manager).

The project to run Chromium/mus/Wayland on Linux (external window mode) is currently being done in the downstream branch called ozone-wayland-dev (https://github.com/Igalia/chromium/). At the moment, we met a phase when the Chromium with Wayland support is stable enough (it is mostly affected with the upstream bugs rather than the implementation we have nowadays) and as close to the stock chromium as possible.

During this project, we have been closely collaborating with Google. Thus, the project to have Chromium with Wayland on Linux is aligned with the plans Google has for the new UI service and Wayland support. We have also started to upstream our patches to the Chromium project.

We have also been updating our meta-browser fork to make the browser available for the AGL system (https://www.automotivelinux.org/). Recently, we have synced our fork and updated the recipe in such a way that it can support several recipe targets, and shared a common part of the recipe between different "subrecipes". You can check it here - https://github.com/Igalia/meta-browser/tree/recipe-with-downstream-sources. The recipe has been tested on a Renesas Rcar m3 board and compiled for the rpi3 target, but not tested yet (we have our internal recipe tested on rpi2 and rpi3, which is very similar to the one we have in GitHub now).

Our idea is to upstream the recipe we have and keep stock Chromium support and Chromium with Wayland support at the same time making it available for meta-browser users.

What do you think about the recipe we have and how do you assess the idea to upstream it?

Best regards,
Maksim Sisov
Igalia S.L.

is there any version demands for "pokey" and "oe" layer to compile the chromium-ozone-wayland pass?

Hello,

which branch of meta-browser is compatible with Yocto Pyro ?

Regards

Hi,

after recent update chromium-x11 to 67.0.3396.62 fails for me with:

FAILED: obj/components/crash/content/app/app/breakpad_linux.o 
arm-angstrom-linux-gnueabi-g++  -march=armv7ve -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 --sysroot=/home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-angstrom-linux-gnueabi/chromium-x11/67.0.3396.62-r0/recipe-sysroot -MMD -MF obj/components/crash/content/app/app/breakpad_linux.o.d -DCRASH_IMPLEMENTATION -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -DV8_USE_EXTERNAL_STARTUP_DATA -I../.. -Igen -I../../third_party/crashpad/crashpad -I../../third_party/crashpad/crashpad/compat/linux -I../../third_party/crashpad/crashpad/compat/non_win -I../../third_party/breakpad/breakpad/src -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -march=armv7ve -mfloat-abi=hard -mtune=cortex-a7 -mfpu=neon-vfpv4 -mthumb -Wall -Wno-psabi -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 -fvisibility=hidden -isystem../../../recipe-sysroot/usr/include/glib-2.0 -isystem../../../recipe-sysroot/usr/lib/glib-2.0/include -std=gnu++14 -Wno-narrowing -fno-exceptions -fno-rtti -fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types -fdebug-prefix-map=/home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-angstrom-linux-gnueabi/chromium-x11/67.0.3396.62-r0=/usr/src/debug/chromium-x11/67.0.3396.62-r0 -fdebug-prefix-map=/home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-angstrom-linux-gnueabi/chromium-x11/67.0.3396.62-r0/recipe-sysroot= -fdebug-prefix-map=/home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-angstrom-linux-gnueabi/chromium-x11/67.0.3396.62-r0/recipe-sysroot-native= -g1 -c ../../components/crash/content/app/breakpad_linux.cc -o obj/components/crash/content/app/app/breakpad_linux.o
In file included from ../../third_party/lss/linux_syscall_support.h:111:0,
                 from ../../third_party/breakpad/breakpad/src/common/memory_allocator.h:50,
                 from ../../third_party/breakpad/breakpad/src/client/linux/dump_writer_common/thread_info.h:37,
                 from ../../third_party/breakpad/breakpad/src/client/linux/minidump_writer/linux_dumper.h:51,
                 from ../../third_party/breakpad/breakpad/src/client/linux/minidump_writer/minidump_writer.h:41,
                 from ../../third_party/breakpad/breakpad/src/client/linux/handler/exception_handler.h:42,
                 from ../../components/crash/content/app/breakpad_linux.cc:48:
../../third_party/crashpad/crashpad/compat/linux/sys/ptrace.h:39:35: error: 'constexpr const __ptrace_request PTRACE_GETVFPREGS' redeclared as different kind of symbol
 static constexpr __ptrace_request PTRACE_GETVFPREGS =
                                   ^~~~~~~~~~~~~~~~~
In file included from /home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-angstrom-linux-gnueabi/chromium-x11/67.0.3396.62-r0/recipe-sysroot/usr/include/sys/ptrace.h:53:0,
                 from ../../third_party/crashpad/crashpad/compat/linux/sys/ptrace.h:18,
                 from ../../third_party/lss/linux_syscall_support.h:111,
                 from ../../third_party/breakpad/breakpad/src/common/memory_allocator.h:50,
                 from ../../third_party/breakpad/breakpad/src/client/linux/dump_writer_common/thread_info.h:37,
                 from ../../third_party/breakpad/breakpad/src/client/linux/minidump_writer/linux_dumper.h:51,
                 from ../../third_party/breakpad/breakpad/src/client/linux/minidump_writer/minidump_writer.h:41,
                 from ../../third_party/breakpad/breakpad/src/client/linux/handler/exception_handler.h:42,
                 from ../../components/crash/content/app/breakpad_linux.cc:48:
/home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-angstrom-linux-gnueabi/chromium-x11/67.0.3396.62-r0/recipe-sysroot/usr/include/sys/ptrace-32.h:126:3: note: previous declaration '__ptrace_request PTRACE_GETVFPREGS'
   PTRACE_GETVFPREGS = 27,
   ^~~~~~~~~~~~~~~~~

My environment is more or less sumo:
Build Configuration:
BB_VERSION = "1.37.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "fedora-27"
TARGET_SYS = "arm-angstrom-linux-gnueabi"
MACHINE = "raspberrypi3"
DISTRO = "angstrom"
DISTRO_VERSION = "v2018.05"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7"
TARGET_FPU = "hard"
meta-angstrom = "sumo:0d3fe793b7d486bacd80bf5dacf2a76cf61cbf19"
meta-oe
meta-filesystems
meta-gnome
meta-initramfs
meta-multimedia
meta-networking
meta-python
meta-webserver
meta-xfce = "sumo+work:598198e2dbedbc68b0187eb8b0b246741b5c19d8"
meta-browser = "master:23b216a2f3202ff7679e5d60d2d7277e8a2b1dcb"
meta-raspi-light = "master:589053f582d63d6e19bec659e31f3bf3c32b2744"
meta-gumstix-community = "master:91dc39a703fb419e9a131ea4c7c0bf1b74cf5dbc"
meta-bbone = "master:c0d7810f59a41c6df2b3f00b31d3de551936ab15"
meta-misc = "master:cdd1a803f98344a50ee5998b598022c5effc15c5"
meta-office = "master:6fe4ac377d926a747f563c8bd6931674dbe01e7c"
meta-qt5 = "rocko-5.9.4:4e7ba65ba6ad4f88683701428aba037f2091fafc"
meta-qt5-extra = "master:a341bd5bbda574152fc945e015d40ddc9805acf7"
meta-games = "work-for-sumo:34e057301589028447cfad83eafe51055379b8a8"
meta-retro = "master:e6e2d9fbdade54c866fd272b7d232cb14ca5bb81"
meta = "sumo+work:94d4078908004dce83d057f57c1fff017788f71a"

OE-Core sumo +

• 94d4078908004dce83d057f57c1fff017788f71a alsa-lib: do not build with debug output by default

Meta-Oe

• e329044a67f2215137f521912c6d7e393ce15d03 fluidsynth: update 1.1.10 -> 1.1.11
• 9b2947190f5dbd74629c907614df64965f2056e6 xfce4-screenshooter: update 1.9.1 -> 1.9.2
• 67559a7af867f755a547f5fdffbbd7bbc1611534 xfce4-whiskermenu-plugin: update 2.1.6 -> 2.1.7
• d819a588b9a4a14b7f13d3fb899e970e2a8441fa menulibre: update 2.1.5 -> 2.2.0
• 3aae63a0da25ec8e798f8939327b4f7858c0f556 xfce4-pulseaudio-plugin: update 0.4.0 -> 0.4.1
• 820d26867664b3660ba7d6de3ac19076e6af5dd1 parole: update 1.0.0 -> 1.0.1
• 4290523d137d63063fcead36a36ac0ab481ee2b8 evince: update 3.24.0 -> 3.28.1
• 598198e2dbedbc68b0187eb8b0b246741b5c19d8 evince: update 3.28.1 -> 3.28.2

Release is out, I think it's time to create a branch here.

I am trying to generate a valid WebRTC binary for ARM V7. Will running this recipe on my Yocto host generate WebRTC binaries, or will it just generate the Chromium package?

please help me. i can not run chrome.

meta-browser : morty with raspberrypi 3 patch
meta-raspberrypi : morty
poky :morty

error below
display.cc(148) WaylandDisplay failed to initialize hardware
ozxonw_platform_wayland.cc(115_ failed to initialize display hardwaree

please help me to run chrome

thanks.

When I build the chromium-x11 for M64, there is a error for building, do you have a patch to fix it?

a7hf-neon-vfpv4-rk-linux-gnueabi/chromium-x11/64.0.3282.119-r0/recipe-sysroot= -g1 -c ../../base/memory/protected_memory_posix.cc -o obj/base/base/protected_memory_posix.o
| {standard input}: Assembler messages:
| {standard input}:316: Warning: ignoring changed section attributes for protected_memory
| {standard input}:644: Error: can't resolve protected_memory' {protected_memory section} - .Ltext0' {.text section}
| {standard input}:645: Error: can't resolve protected_memory' {protected_memory section} - .Ltext0' {.text section}
| {standard input}:646: Error: can't resolve protected_memory' {protected_memory section} - .Ltext0' {.text section}
| {standard input}:647: Error: can't resolve protected_memory' {protected_memory section} - .Ltext0' {.text section}
| {standard input}:650: Error: can't resolve protected_memory' {protected_memory section} - .Ltext0' {.text section}
| {standard input}:651: Error: can't resolve protected_memory' {protected_memory section} - .Ltext0' {.text section}
| {standard input}:652: Error: can't resolve protected_memory' {protected_memory section} - .Ltext0' {.text section}
| {standard input}:653: Error: can't resolve protected_memory' {protected_memory section} - .Ltext0' {.text section}

Perhaps, we should need add the Linking with lld is required to workaround crbug.com/792777.

It makes sense to have both using the same namespace.

haha!!!
the chromium-ozone-wayland now can be run on my port. thanks for your support.

but for my device has limitation input devices, is there any way to open a websit by chromium command line?
thanks !

Hi,
Using the Morty branch , I am getting a ink failure ;
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "msc-sm2-imx6"
DISTRO = "poky"
DISTRO_VERSION = "2.2"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU = "hard"
meta-poky
meta-yocto-bsp = "morty-amarel:b07e7bc6a479e280bd9a6a04bc0f9ffd7bd0287c"
meta = "master:9f46ed1d63d4ec85d88e8f31efeb4a52ad0a13a2"
meta = "morty-amarel:b07e7bc6a479e280bd9a6a04bc0f9ffd7bd0287c"
meta-oe
meta-networking
meta-python = "morty-msc:5e789602f629f3e97e9d74bbf63018ceed746759"
meta-qt5.git = "morty-msc:7128e252f83a77e04e4b53c90864f2e11677568c"
meta-oracle-java.git = "morty:f44365f02b283c3fb362dc99e2e996d3f11e356e"
meta-msc-ldk-core-recipes.git = "master:c9bb9478efc6f8bd28a6d283bc3f98306226fcbc"
meta-msc-ldk-core.git = "master:327dfb039c5a7195c4f3b78750ecc3dd66c22f97"
meta-msc-ldk-mscio.git = "master:2eef4699a0e9f509cfc67aeae87de44f87edbc89"
meta-amarel-custom.git = "develop:d41beecaf157564ba282be9a4be14c079eaeb265"
meta-freescale.git = "morty:38bd14cddf1ce325de43f1fb29f01551b48384bb"
meta-msc-ldk-lxqt.git = "master:e3a8623a884d08a57291746f7127d243a4b86880"
meta-gnome
meta-efl = "morty-msc:5e789602f629f3e97e9d74bbf63018ceed746759"
meta-qt5-extra.git = "morty-msc:c69df3339315e99a704c8e68ea1cb99ae41859c4"
meta-browser.git = "morty:1569eeb9cc1b87632abbf35fbb05f4ac4eeb3987"

Initialising tasks: 100% |#####################################################################################################################################################################################################| Time: 0:00:18
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
Currently 1 running tasks (8613 of 8638) 99% |################################################################################################################ERROR: chromium-52.0.2743.76-r0 do_compile: Function failed: do_compile (log file is located at /home/amarel/msc-amarel/build/0101301-lxqt/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/chromium/52.0.2743.76-r0/temp/log.do_compile.12245)
ERROR: Logfile of failure stored in: /home/amarel/msc-amarel/build/0101301-lxqt/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/chromium/52.0.2743.76-r0/temp/log.do_compile.12245
Log data follows:
| DEBUG: Executing shell function do_compile
| ninja: Entering directory `/home/amarel/msc-amarel/build/0101301-lxqt/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/chromium/52.0.2743.76-r0/chromium-52.0.2743.76/out/Release'
| [1/1] LINK chrome
| FAILED: chrome
| arm-poky-linux

Ideas ?

I'm currently working on Chromium 68 (currently in the beta channel), and both ARM and ARM64 builds (I've tried MACHINE="qemuarm64" and MACHINE="raspberrypi3") currently fail with pyro's GCC 6 due to an internal compiler error when building some bits of Skia that use NEON and other optimizations:

arch64-poky-linux-gcc  --sysroot=/data/src/yocto/poky/build-pyro-qemuarm64/tmp/work/aarch64-poky-linux/chromium-x11/68.0.3440.59-r0/recipe-sysroot -MMD -MF obj/skia/skcm
s/Transform.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE
_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D_F
ORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -I../../third_party/skia/third_party/skcms -w -std=c11 -fno-strict-aliasing --param=ssp
-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -Wall -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-n
ull-pointer-checks -Wno-comments -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 -fvi
sibility=hidden -std=gnu11  -O2 -pipe -feliminate-unused-debug-types -fdebug-prefix-map=/data/src/yocto/poky/build-pyro-qemuarm64/tmp/work/aarch64-poky-linux/chromium-x11
/68.0.3440.59-r0=/usr/src/debug/chromium-x11/68.0.3440.59-r0 -fdebug-prefix-map=/data/src/yocto/poky/build-pyro-qemuarm64/tmp/work/aarch64-poky-linux/chromium-x11/68.0.34
40.59-r0/recipe-sysroot-native= -fdebug-prefix-map=/data/src/yocto/poky/build-pyro-qemuarm64/tmp/work/aarch64-poky-linux/chromium-x11/68.0.3440.59-r0/recipe-sysroot= -g1
-c ../../third_party/skia/third_party/skcms/src/Transform.c -o obj/skia/skcms/Transform.o
In file included from ../../third_party/skia/third_party/skcms/src/Transform.c:176:0:
../../third_party/skia/third_party/skcms/src/Transform_inl.h: In function 'exec_ops':
../../third_party/skia/third_party/skcms/src/Transform_inl.h:459:32: internal compiler error: in convert_move, at expr.c:299
     v = (U16)( ((v<<8)|(v>>8)) & 0xffff );
              ~~~~~~~~~~~~~~~~~~^~~~~~~~~~

The code builds fine on rocko and later (which have GCC 7). I see a few different options here:

1. Explicitly drop support for GCC 6 and pyro and stop testing it altogether.
2. Just stop building and testing pyro and GCC 6 on ARM/ARM64, but make sure an x86/x86-64 build still works.
3. Bisect GCC and try to get the internal compiler error fix into pyro's GCC recipe. That requires building multiple versions of GCC as a cross-compiler, which, let's say, is definitely not a pleasant experience.

seems we now use a older version of chromium ozone wayland port, is there any plan to update the recipe to the latest version?
  | Parent Directory |   | - |  
  | chromium-ozone-wayland-dev-64.0.3257.1.r513783.igalia.1.tar.xz | 2017-11-10 10:52 | 562M |  
  | chromium-ozone-wayland-dev-64.0.3267.0.r515863.igalia.1.tar.xz | 2017-11-16 21:07 | 544M |  
  | chromium-ozone-wayland-dev-64.0.3274.0.r517731.igalia.1.tar.xz | 2017-11-22 00:50 | 579M |  
  | chromium-ozone-wayland-dev-64.0.3278.0.r519194.igalia.1.tar.xz | 2017-11-30 12:56 | 585M |  
  | chromium-ozone-wayland-dev-65.0.3298.0.r524623.igalia.1.tar.xz | 2017-12-20 14:02 | 585M |  
  | chromium-ozone-wayland-dev-65.0.3315.0.r527534.igalia.1.tar.xz | 2018-01-12 17:00 | 634M |  
  | chromium-ozone-wayland-dev-66.0.3340.0.r534306.igalia.1.tar.xz | 2018-02-12 09:48 | 640M |  
  | chromium-ozone-wayland-dev-67.0.3361.0.r540770.igalia.1.tar.xz | 2018-03-07 13:56 | 706M |  
  | chromium-ozone-wayland-dev-67.0.3368.0.r542415.igalia.1.tar.xz | 2018-03-16 13:55 | 709M |  
  | chromium-ozone-wayland-dev-67.0.3375.0.r543955.igalia.1.tar.xz | 2018-03-19 15:54 | 709M |  
  | chromium-ozone-wayland-dev-67.0.3387.0.r547398.igalia.1.tar.xz | 2018-04-05 15:50 | 709M |  
  | chromium-ozone-wayland-dev-68.0.3404.0.r552606.igalia.1.tar.xz | 2018-05-24 12:01 | 2.3M |  
  | chromium-ozone-wayland-dev-68.0.3437.0.r560198.igalia.1.tar.xz | 2018-05-24 20:12 | 792M |  
  | chromium-ozone-wayland-dev-69.0.3448.0.r563980.igalia.1.tar.xz | 2018-06-04 18:21 | 806M |  
  | chromium-ozone-wayland-dev-69.0.3455.0.r565933.igalia.1.tar.xz | 2018-06-14 09:56 | 809M |  
  | chromium-ozone-wayland-dev-69.0.3474.0.r570340.igalia.1.tar.xz | 2018-06-26 15:45 | 815M |  
  | chromium-wayland-8eb8619a.tar.xz | 2018-03-06 12:37 | 1.8G |  

When I use this layer to install Chromium (both on X11 and Wayland in all currently available versions) on my ARMv7 (Rockchip RK3288) board and compile with the proprietary-codecs PACKAGECONFIG, I get an error while playing video (or audio) in an mp4 container. The browser simply says "Oh snap! Something went wrong", and with gdb I can trace the error back to a call to ffmpeg. However, I am having a hard time finding out what goes wrong inside ffmpeg as I am not familiar with its internals and chromium seems to compile it in a strange way.

the chromium perform the h5 video tag mediaplayer with ffmpeg mechanism,
but i did not find the releationship of chromium with the my yocoto sdk ffmpeg packages, now
i meet some problem on this, and dont know where to go, so, could you show me some hints on the chromium media process, where is the core process code of the mediaplayer?

thanks for your help.

I am using the yocto pyro branch, trying to build "chromium-ozone-wayland" for x86 target.

Do you have a meta-browser branch compatible with pyro?

I am using branch "ozone/wayland/67.0.3375.0.r543955" and chromium-x11 builds fine, but when I try to build chromium-ozone-wayland , I am getting the errors shown below:

Any ideas please how I can resolve this?

[16658/35221] g++ -MMD -MF yocto_native/obj/third_party/flatbuffers/compiler_files/idl_gen_cpp.o.d -isystem/home/cchilumbu/projects/yocto-dr0081/build-aaeon/tmp/work/corei7-64-poky-linux/chromium-ozone-wayland/67.0.3375.0.r543955.igalia.1-r0/recipe-sysroot-native/usr/include -isystem/home/cchilumbu/projects/yocto-dr0081/build-aaeon/tmp/work/corei7-64-poky-linux/chromium-ozone-wayland/67.0.3375.0.r543955.igalia.1-r0/recipe-sysroot-native/usr/include -O2 -pipe -D_GLIBCXX_USE_CXX11_ABI=0 -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../../third_party/flatbuffers/src/grpc -I../.. -Iyocto_native/gen -I../../third_party/flatbuffers/src/include -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 -fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-missing-field-initializers -Wno-unused-parameter -std=gnu++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -Wno-narrowing -c ../../third_party/flatbuffers/src/src/idl_gen_cpp.cpp -o yocto_native/obj/third_party/flatbuffers/compiler_files/idl_gen_cpp.o
| [16659/35221] g++ -MMD -MF yocto_native/obj/third_party/flatbuffers/compiler_files/idl_parser.o.d -isystem/home/cchilumbu/projects/yocto-dr0081/build-aaeon/tmp/work/corei7-64-poky-linux/chromium-ozone-wayland/67.0.3375.0.r543955.igalia.1-r0/recipe-sysroot-native/usr/include -isystem/home/cchilumbu/projects/yocto-dr0081/build-aaeon/tmp/work/corei7-64-poky-linux/chromium-ozone-wayland/67.0.3375.0.r543955.igalia.1-r0/recipe-sysroot-native/usr/include -O2 -pipe -D_GLIBCXX_USE_CXX11_ABI=0 -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../../third_party/flatbuffers/src/grpc -I../.. -Iyocto_native/gen -I../../third_party/flatbuffers/src/include -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0 -fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-missing-field-initializers -Wno-unused-parameter -std=gnu++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -Wno-narrowing -c ../../third_party/flatbuffers/src/src/idl_parser.cpp -o yocto_native/obj/third_party/flatbuffers/compiler_files/idl_parser.o
| ninja: build stopped: subcommand failed.
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/cchilumbu/projects/yocto-dr0081/build-aaeon/tmp/work/corei7-64-poky-linux/chromium-ozone-wayland/67.0.3375.0.r543955.igalia.1-r0/temp/log.do_compile.1367)
ERROR: Task (/home/cchilumbu/projects/yocto-dr0081/sources/meta-browser/recipes-browser/chromium/chromium-ozone-wayland_67.0.3375.0.r543955.igalia.1.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 6005 tasks of which 5990 didn't need to be rerun and 1 failed.

from the print below, it seems the debug information was stripped in the final binary, so, how to get the callstack info properly with gdb debug tools?

tanks for your support.
#0 0x0000007f7f91c73c in epoll_pwait () from /lib/libc.so.6
#1 0x00000055782dc37c in ?? ()
#2 0x00000055782da6a0 in ?? ()
#3 0x000000557825342c in ?? ()
#4 0x0000005578277aa0 in ?? ()
#5 0x000000557815669c in ?? ()
#6 0x0000005576cc65e8 in ?? ()
#7 0x0000005576cc84f0 in ?? ()
#8 0x0000005576cc1f90 in ?? ()
#9 0x0000005577f07534 in ?? ()
#10 0x0000005577f11988 in ?? ()
#11 0x0000005577f05f74 in ?? ()
#12 0x000000557656f6a8 in ?? ()
#13 0x0000007f7f86fa24 in __libc_start_main () from /lib/libc.so.6
#14 0x000000557656f500 in ?? ()

Hi, I'm quite new to Yocto and I was wondering if the master branch of chromium Wayland is somehow compatible with the Krogoth release.
What are the main compatibility checks I need to perform?
My current problem is that the board I'm using is a custom version of an imx6 and the hw provider doesn't want to update the compatibility of some of the drivers to a newer release of yocto.
I'm currently using chromium 48 with wayland but it has some performance issues.
Thanks