Correction: we might be able to reuse part of the bbappend. Make a copy
of the bbappend for Chromium 52. Then, in the copy, remove or comment
out the lines which start with CHROMIUM_IMX_VPU_PATCHES_ . Also remove
the CHROMIUM_IMX_WAYLAND_PATCHES line (we do not have working Wayland
support in >M48 at the moment because ozone-wayland does not have a
matching branch; ozone-wayland has been partially merged into Chromium,
but nobody has tried using this feature yet). Then you have Chromium
without VPU integration (this is what I was referring to earlier
regarding the APIs) but with EGL flags etc. enabled.
On 2016-08-19 17:31, Carlos Rafael Giani wrote:
Such updates are never trivial because the Chrome devs constantly
change subtle things about the APIs. This will require an update of
chromium-imx to be fully functional. I will not be able to do this
until mid September. So, either you stick to M48, or you remove the
bbappend. No other options are there at the moment, unfortunately :(
On 2016-08-19 17:07, Gary Thomas wrote:
On 2016-08-19 16:43, Otavio Salvador wrote:
Hello Gary,
On Fri, Aug 19, 2016 at 7:43 AM, Gary Thomas <[email protected]> wrote:
After updating to
meta-fsl-arm: 53cfeee85f712937cd33c63b18a4be49e0b08e19
meta-browser: d4deef18f8662bdd918a2d0456078dd4976d9ce9
ERROR: No recipes available for:
/local/poky-cutting-edge/meta-fsl-arm/browser-layer/recipes-browser/chromium/chromium_48.0.2548.0.bbappend
Indeed; for Krogoth I created a branch for meta-browser before the
upgrade so it is possible to keep using it. For master, someone who is
actively using Chromium should provide a patch :-) (Yes Gary I am
looking at you... :-))
I might, Except I don't know the implications of the patches/changes
w.r.t.
the new version :-(
--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
