chromium is compiling but is not able to add in the image
I tried adding chromium package via the meta-browser layer. It is compiling when I run $ bitbake chromium . But when I run $bitbake core-image-minimal-pdm3. It’s not adding chromium to the image and throwing errors as shown below:
Loading cache: 100% |####################################################################################################################################################################################################| Time: 0:00:00 Loaded 3249 entries from dependency cache.
Parsing recipes: 100% |##################################################################################################################################################################################################| Time: 0:00:02 Parsing of 2368 .bb files complete (2352 cached, 16 parsed). 3260 targets, 99 skipped, 10 masked, 0 errors.
WARNING: No recipes available for:
/home/iepl/work/yocto_build/meta-xilinx/meta-xilinx-contrib/recipes-kernel/linux/linux-xlnx_2018.1.bbappend /home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-extended/images/swupdate-gui-image.bbappend /home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-support/rescuegui/rescuegui_%.bbappend /home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-support/swupdate/swupdate_%.bbappend /home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3/recipes-mono/mono/mono-native_5.4.1.6.bbappend
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'chromium' (but /home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-core/images/core-image-minimal-pdm3.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'chromium' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['chromium']
ERROR: Required build target 'core-image-minimal-pdm3' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-minimal-pdm3', 'chromium']
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
The bblayers.conf file is taken care off.
I’ve added the lineIMAGE_INSTALL_append = “ chromium” in the local.conf file along with LICENSE_FLAG_WHITELIST =
" commercial_libav commercial_x264 commercial"
Apart from that Firefox is able to compile and it’s been added to the image. Can somebody tell me what is causing this issue.
Thanks,
Best Regards
Kamal Pandey
Junior Software Engineer
[ifm_logo_sqrs]ifm engineering pvt. ltd.
Survey No. 1/10/16, 3rd floor, Above SBI, Bavdhan Branch, N.D.A. Road, Bavdhan, Pune, India - 411021 | Web: www.ifm.com<http://www.ifm.com/> | Phone: +91-20-22951910 Extn:215 | CIN: U29213PN2010FTC13676
A message that is not in the archive (sent off-list or not yet received): [email protected]
Thankyou very much for the response.
core-image-minimal-pdm3 is a custom image made from proprietary meta-pdm3 layer. This layer is used to create images and packages for custom embedded device. I ve enabled x11 in conf/local.conf file.
IMAGE_INSTALL_append = " x11 \ chromium \
and yes that device has a mali GPU support.
-----Original Message-----
From: Stefano Babic <[email protected]>
Sent: 23 August 2018 21:26
To: Pandey, Kamal <[email protected]>
Cc: Ross, Fedor <[email protected]>; Barth, Steffen <[email protected]>; Marek Vasut <[email protected]>
Subject: Re: [yocto] chromium is compiling but is not able to add in the image
Hi Kamal,
(out of list):
I just seen your post to Yocto'sML...
Quoted 3 lines · Kamal
I tried adding chromium package via the meta-browser layer. It is compiling when I run */$ bitbake chromium/*/./ But when I run */$bitbake core-image-minimal-pdm3/*.
..but I can understand that nobody has the small idea what core-image-minimal-pdm3 is !
Quoted 36 lines
It’s not adding chromium to the image and throwing errors as shown below:
Loading cache: 100%
|##################################################################### |##################################################################### |##########################################################|Time: 0:00:00
Loaded 3249 entries from dependency cache.
Parsing recipes: 100%
|##################################################################### |##################################################################### |########################################################|Time: 0:00:02
Parsing of 2368 .bb files complete (2352 cached, 16 parsed). 3260 targets, 99 skipped, 10 masked, 0 errors.
WARNING: No recipes available for:
/home/iepl/work/yocto_build/meta-xilinx/meta-xilinx-contrib/recipes-kernel/linux/linux-xlnx_2018.1.bbappend
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-extended/images/swupdate-gui-image.bbappend
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-support/rescuegui/rescuegui_%.bbappend
Quoted 8 lines
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-support/swupdate/swupdate_%.bbappend
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3/recipes-mono/mono/mono-native_5.4.1.6.bbappend
Your bblayers.conf is maybe a mess. They are solved in meta-ifm-pdm3 and meta-ifm-pdm3-bsp
Quoted 31 lines
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'chromium' (but
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-core/images/core-image-minimal-pdm3.bb
RDEPENDS on or otherwise requires it)NOTE: Runtime target 'chromium' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['chromium']
ERROR: Required build target 'core-image-minimal-pdm3' has no buildable providers.
Missing or unbuildable dependency chain was:
['core-image-minimal-pdm3', 'chromium']Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
The bblayers.conf file is taken care off.
I’ve added the line
*/IMAGE_INSTALL_append = “ chromium”/* in the local.conf file along with
*/LICENSE_FLAG_WHITELIST = /**//**//*
Quoted 7 lines
*/"
commercial_libavcommercial_x264commercial/**/"/*Apart from that Firefox is able to compile and it’s been added to the image. Can somebody tell me what is causing this issue.
Apart of that, are you trying to get in running with something provided by Marek for Mali (GPU support) ? I just warn that Chromium without GPU is very slow and pratically unusable. Even with GPU support it looks quite slow...
Are you enable x11 ? As far as I know, chromium is running just on top of x11 - I added Marek in CC that can sugest something else.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: [email protected] =====================================================================
Hi Kamal,
Quoted 2 lines · Kamal
Thankyou very much for the response.
core-image-minimal-pdm3 is a custom image made from proprietary meta-pdm3 layer.
I know, I am in this project....
Quoted 2 lines
This layer is used to create images and packages for custom embedded device. I ve enabled x11 in
conf/local.conffile.
No, you have to add it in DISTRO_FEATURES, too
Quoted 4 lines
IMAGE_INSTALL_append = " x11 \ chromium \and yes that device has a mali GPU support.
You have not understood. The SOC has a mali GPU. But work for kernel driver (Lima) and openGL is WIP. Ask Fedor/Marek for the current status and if it makes sense some test. Chromium without GPU does not work.
Best regards,
Stefano Babic
Quoted 122 lines
-----Original Message-----
From: Stefano Babic <[email protected]>
Sent: 23 August 2018 21:26
To: Pandey, Kamal <[email protected]>
Cc: Ross, Fedor <[email protected]>; Barth, Steffen <[email protected]>; Marek Vasut <[email protected]>
Subject: Re: [yocto] chromium is compiling but is not able to add in the imageHi Kamal,
(out of list):
I just seen your post to Yocto'sML...
Quoted 3 lines · Kamal
I tried adding chromium package via the meta-browser layer. It is compiling when I run */$ bitbake chromium/*/./ But when I run */$bitbake core-image-minimal-pdm3/*.
..but I can understand that nobody has the small idea what core-image-minimal-pdm3 is !
Quoted 36 lines
It’s not adding chromium to the image and throwing errors as shown below:
Loading cache: 100%
|##################################################################### |##################################################################### |##########################################################|Time: 0:00:00
Loaded 3249 entries from dependency cache.
Parsing recipes: 100%
|##################################################################### |##################################################################### |########################################################|Time: 0:00:02
Parsing of 2368 .bb files complete (2352 cached, 16 parsed). 3260 targets, 99 skipped, 10 masked, 0 errors.
WARNING: No recipes available for:
/home/iepl/work/yocto_build/meta-xilinx/meta-xilinx-contrib/recipes-kernel/linux/linux-xlnx_2018.1.bbappend
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-extended/images/swupdate-gui-image.bbappend
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-support/rescuegui/rescuegui_%.bbappendQuoted 8 lines
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-support/swupdate/swupdate_%.bbappend
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3/recipes-mono/mono/mono-native_5.4.1.6.bbappendYour bblayers.conf is maybe a mess. They are solved in meta-ifm-pdm3 and meta-ifm-pdm3-bsp
Quoted 31 lines
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'chromium' (but
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-core/images/core-image-minimal-pdm3.bb
RDEPENDS on or otherwise requires it)NOTE: Runtime target 'chromium' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['chromium']
ERROR: Required build target 'core-image-minimal-pdm3' has no buildable providers.
Missing or unbuildable dependency chain was:
['core-image-minimal-pdm3', 'chromium']Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
The bblayers.conf file is taken care off.
I’ve added the line
*/IMAGE_INSTALL_append = “ chromium”/* in the local.conf file along with
*/LICENSE_FLAG_WHITELIST = /**//**//*Quoted 7 lines
*/"
commercial_libavcommercial_x264commercial/**/"/*Apart from that Firefox is able to compile and it’s been added to the image. Can somebody tell me what is causing this issue.
Apart of that, are you trying to get in running with something provided by Marek for Mali (GPU support) ? I just warn that Chromium without GPU is very slow and pratically unusable. Even with GPU support it looks quite slow...
Are you enable x11 ? As far as I know, chromium is running just on top of x11 - I added Marek in CC that can sugest something else.
Best regards,
Stefano Babic--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: [email protected] =====================================================================
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: [email protected] =====================================================================
On Fri, 2018-08-24 at 06:24 +0000, Pandey, Kamal wrote:
[trimmed]
Quoted 7 lines
Apart of that, are you trying to get in running with something provided by Marek for Mali (GPU support) ? I just warn that Chromium without GPU is very slow and pratically unusable. Even with GPU support it looks quite slow...
Are you enable x11 ? As far as I know, chromium is running just on top of x11 - I added Marek in CC that can sugest something else.
For what it's worth - lots of effort put in the last few years to run Chromium on Wayland (also for embedded). It's running on weston in the GDP, see [1]. Looking at that might help the OP, but also other systems make use of these layers.
The community GDP distro used meta-browser layer before but is for the moment on another fork that was developed by LG Electronics I believe, called meta-lgsvl-browser. We typically follow the advice of some dedicated expert companies in this area.
Hope this helps,
- Gunnar
[1] https://github.com/GENIVI/genivi-dev-platform
Signature · 3 lines
Gunnar Andersson <[email protected]> Development Lead GENIVI Alliance
Quoted 9 lines
Best regards,
Stefano Babic--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: [email protected]
=====================================================================
Quoted 4 lines · Kamal
I tried adding chromium package via the meta-browser layer. It is compiling when I run $ bitbake chromium . But when I run $bitbake core-image-minimal-pdm3. It’s not adding chromium to the image and throwing errors as shown below:
"chromium" is currently just a shorthand for "chromium-x11". Does it work if you pass the latter to bitbake?