Hi NXP Team
Follower the i.MX_Yocto_Peoject_User's_Guide.pdf, we're try to add chromium browser on X11 yocto 2.1 version.
In local.conf, you can perform the following operations:
• Add Chromium into your image.
CORE_IMAGE_EXTRA_INSTALL += "chromium libexif"
• Add the commercial white list into local.conf.
LICENSE_FLAGS_WHITELIST="commercial"
-----------------------------------------------------------------------------------------------------------------------------------------------------
Our customer have successfully built an image with Chromium but errors appeared during the compilation. (see below)
When using Chromium, the web browser crashed very often.
Failures during compilation:
(1)First we got this error:
ERROR: chromium was skipped: Recipe is blacklisted: BROKEN: fails to build with gcc-6
Because Chromium is on the blacklist
The solution is to add in local.conf: PNBLACKLIST[chromium] = “”
(2) Then we got a second error regarding a chromium patch:
0004-Create-empty-i18n_process_css_test.html-file-to-avoi.patch
patch: **** Only garbage was found in the patch input
the workaround is to create manually an empty html file (details is in the patch) but it is not a sustainable solution.
About the two question,do you have any advice?
Thanks
Best regards
Clayder
Hi Clayder
one can look on
i.MX6 DL, Yocto Krogoth and Chromium 48.0.2548 problems ...
Porting Chrome on i.mx6 with hw accelaration?
as stated in i.MX_Yocto_Peoject_User's_Guide.pdf :
"Note that NXP does not support or test the patches from the community."
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi Igor,
I have checked your offering 2 links of the possible solution of Chromium integration, but unfortunately the former communication and solution was based on Ycoto V1.7 or older version, and the former method couldn't be used in Ycoto V2.1, we still had the building error messages and we could build with Chromium package success.
So could you have another suggestion for us?
Thank you for help!
B.R.,
Kevin