Re: [OE-core] Problem in Third party Software (Navit) integration
Dear Ross, Your question: You're not really giving much away by just saying "not running", Answer : kernel is generated using “bitbake core-image-base” command. I extracted my kernel image to SD card and used it in my am437x-eVm board, It boots and end up with command prompt. But No GUI related to “Navit” . I wanted to get the “Navit” GUI. So I assume that it is not running. Your question: you may need to install more than just the navit package. Answer : I don’t have idea, what are the package I need to install and how to install? I have added IMAGE_INSTALL_append = " navit" in /build/conf/local.conf Do you have any procedure to install additional packages? Your question:Have a look at the recipe and you'll see that it generates lots of packages, Answer : when I run “bitbake core-image-base” , No packages are generated it seems. But when I run “bitbake qt4e-demo-image” , Lot of packages are generated related to “navit” in /home/winiston/poky/build/tmp/sysroots/am437x-evm/pkgdata/runtime. What are the packages I need to add ? How do I add those packages in the image? Thanks in advance... Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 From: Burton, Ross Sent: Thursday, April 07, 2016 2:28 PM To: winis...@futuraautomation.com Cc: OpenEmbedded core ; yocto texas ; Yocto layer Subject: Re: [OE-core] Problem in Third party Software (Navit) integration On 7 April 2016 at 08:41, wrote: Kernel is successfully generated. But “Navit” is not running in my kernel. How do I integrate/add “Navit” to my kernel ? should I make any other configuration and package? You're not really giving much away by just saying "not running", but you may need to install more than just the navit package. Have a look at the recipe and you'll see that it generates lots of packages, you may need to install some more or even all of those. Ross-- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] Problem in Third party Software (Navit) integration
Dear, I cannot add “Navit” to my kernel (“core-image-base” or “qt4e-demo-image” ). Kernel is successfully generated. But “Navit” is not running in my kernel. How do I integrate “navit” to my kernel . Please provide the way to add “navit”. Note: “Navit” is navigation software. I am using yocto build system (Poky) for building “core-image-base” kernel for “am437x-evm”. Since I want to integrate “Navit” to my kernel, I have added “meta-oe” layer . “meta-oe”(jethro branch) has been downloaded from open embedded project and integrated to poky. meta-oe has “recipes-navigation”. After that I made the following changes in “/build/conf/local.conf “ to integrate “Navit” to my kernel. 1. IMAGE_INSTALL_append = " navit" (For append Navit to my kernel ). 2. DISTRO_FEATURES_BACKFILL_CONSIDERED = " bluez5" (navit is using bluez4. For avoid conflict to blue54 and bluez5, this line is added ). 3. BBFILES+= "${HOME}/winiston/poky/meta-oe/recipes-navigation/*/*.bb" 4. MACHINE ??= "am437x-evm" (“am437x-evm” machine is selected). bblayers.conf (/build/conf/bblayers.conf ) files as given below. # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf # changes incompatibly LCONF_VERSION = "6" BBPATH = "${TOPDIR}" BBFILES ?= "" BBLAYERS ?= " \ /home/winiston/poky/meta \ /home/winiston/poky/meta-yocto \ /home/winiston/poky/meta-yocto-bsp \ /home/winiston/poky/meta-ti \ /home/winiston/poky/meta-oe \ " BBLAYERS_NON_REMOVABLE ?= " \ /home/winiston/poky/meta \ /home/winiston/poky/meta-yocto \ " #wini BBFILES += "${HOME}/winiston/poky/meta/recipes-qt/*/*.bb" #added by hob BBFILES += "${TOPDIR}/recipes/images/custom/*.bb" #added by hob BBFILES += "${TOPDIR}/recipes/images/*.bb" Please see my below command and terminal window output. winiston@winiston-VirtualBox:~/poky$ source oe-init-build-env ### Shell environment set up for builds. ### You can now run 'bitbake ' Common targets are: core-image-minimal core-image-sato meta-toolchain adt-installer meta-ide-support You can also run generated qemu images with a command like 'runqemu qemux86' winiston@winiston-VirtualBox:~/poky/build$ bitbake core-image-base Loading cache: 100% |##| ETA: 00:00:00 Loaded 2223 entries from dependency cache. NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo) NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg NOTE: multiple providers are available for jpeg-native (jpeg-native, libjpeg-turbo-native) NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg-native Build Configuration: BB_VERSION= "1.28.0" BUILD_SYS = "i686-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS= "arm-poky-linux-gnueabi" MACHINE = "am437x-evm" DISTRO= "poky" DISTRO_VERSION= "2.0.1" TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9" TARGET_FPU= "vfp-neon" meta meta-yocto meta-yocto-bsp= "jethro:12fae239641cc7a72c509a1a0841ab8bb06ce7f0" meta-ti = "master:963c35fc490a733a533c0c30471f9974eed451d6" meta-oe = "jethro:12fae239641cc7a72c509a1a0841ab8bb06ce7f0" NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Tasks Summary: Attempted 3805 tasks of which 3799 didn't need to be rerun and all succeeded. Kernel is successfully generated. But “Navit” is not running in my kernel. How do I integrate/add “Navit” to my kernel ? should I make any other configuration and package? Thanks in advance... Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [linux-yocto] How to integrate third party application software to yocto image
Dear Ross, Thanks for your valuable time...As you said, I added “meta-oe” layer in “bblayers.conf” . Now that Error got disappeared. Now it spits out the following error.. winiston@winiston-VirtualBox:~/poky/build$ bitbake qt4e-demo-image Loading cache: 100% |##| ETA: 00:00:00 Loaded 2176 entries from dependency cache. ERROR: ParseError at /home/winiston/poky/meta-oe/recipes-connectivity/networkmanager/networkmanager_1.0.10.bb:12: Could not inherit file classes/bash-completion.bbclass Summary: There was 1 ERROR message shown, returning a non-zero exit code. winiston@winiston-VirtualBox:~/poky/build$ Then for the time being, I have removed “networkmanager_1.0.10.bb “ . After that it started building more than 3350 package out of 3659. Now it spits out the following error. Please see below log files. winiston@winiston-VirtualBox:~/poky/build$ bitbake qt4e-demo-image Loading cache: 100% |##| ETA: 00:00:00 Loaded 2218 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION= "1.28.0" BUILD_SYS = "i686-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS= "arm-poky-linux-gnueabi" MACHINE = "am437x-evm" DISTRO= "poky" DISTRO_VERSION= "2.0.1" TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9" TARGET_FPU= "vfp-neon" meta meta-yocto meta-yocto-bsp= "jethro:12fae239641cc7a72c509a1a0841ab8bb06ce7f0" meta-ti = "master:963c35fc490a733a533c0c30471f9974eed451d6" meta-oe = "jethro:12fae239641cc7a72c509a1a0841ab8bb06ce7f0" NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: oe_runmake failed ERROR: Function failed: do_compile (log file is located at /home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/temp/log.do_compile.3665) ERROR: Logfile of failure stored in: /home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/temp/log.do_compile.3665 Log data follows: | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] | DEBUG: Executing shell function do_compile | NOTE: make -j 1 | make all-recursive | make[1]: Entering directory `/home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/build' | Making all in intl | make[2]: Entering directory `/home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/build/intl' | make[2]: Nothing to be done for `all'. | make[2]: Leaving directory `/home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/build/intl' | Making all in po | make[2]: Entering directory `/home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/build/po' | make[2]: Nothing to be done for `all'. | make[2]: Leaving directory `/home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/build/po' | Making all in man | make[2]: Entering directory `/home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/build/man' | make[2]: Nothing to be done for `all'. | make[2]: Leaving directory `/home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/build/man' | Making all in navit | make[2]: Entering directory `/home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/build/navit' | echo "#include \"config.h\"" >version.h.tmp | echo "#define SVN_VERSION \"$(LANG=C svnversion /home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/navit 2>/dev/null)\"" >>version.h.tmp | echo "#define NAVIT_VARIANT \"\"" >>version.h.tmp | if ! diff version.h.tmp version.h >/dev/null 2>/dev/null; \ | then \ | mv -f version.h.tmp version.h; \ | fi | make all-recursive | make[3]: Entering directory `/home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/build/navit' | Making all in fib-1.1 | make[4]: Entering directory `/home/winiston/poky/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/navit/1_0.2.0+svnr5310-r11.3/build/navit/fib-1.1' | make[4]: Nothing to be done for `all'. | make[4]: Leaving directory `/home/winiston/poky/bui
Re: [OE-core] [linux-yocto] How to integrate third party application software to yocto image
Dear Ross, Backlist problem got solved by adding the lines which you mentioned in the previous mail. Now it gives the following error while building the image. winiston@winiston-VirtualBox:~/poky/build$ bitbake qt4e-demo-image Parsing recipes: 100% || Time: 00:02:24 Parsing of 1125 .bb files complete (0 cached, 1125 parsed). 1569 targets, 139 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'gd' (but /home/winiston/poky/meta/recipes-qt/navit/navit_svn.bb DEPENDS on or otherwise requires it). Close matches: gdb NOTE: Runtime target 'navit' is unbuildable, removing... Missing or unbuildable dependency chain was: ['navit', 'gd'] ERROR: Required build target 'qt4e-demo-image' has no buildable providers. Missing or unbuildable dependency chain was: ['qt4e-demo-image', 'navit', 'gd'] Summary: There were 2 ERROR messages shown, returning a non-zero exit code. winiston@winiston-VirtualBox:~/poky/build$ I would be very thankful if you tell me the procedure to add “Navit” in the yocto build. My aim is to integrate “navit” in my image. Thanking you... Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 From: Burton, Ross Sent: Thursday, March 03, 2016 7:07 PM To: winis...@futuraautomation.com Cc: Anders Darander ; OE-core ; yocto texas ; Yocto layer Subject: Re: [linux-yocto] [OE-core] How to integrate third party application software to yocto image On 2 March 2016 at 08:52, wrote: ERROR: navit was skipped: Recipe is blacklisted: bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES Your distro is using bluez5 but navit is using the old/deprecated/unmaintained bluez4. Ideally you create a new distro and change this, but for testing this in your local.conf should be sufficient: DISTRO_FEATURES_BACKFILL_CONSIDERED = "bluez5" This will stop your distro from wanting to use bluez5 and will fall back to bluez4, at which point navit will build. Ross-- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] How to add recipes-navigation in core-image-base
Hi, I wanted to use “recipes-navigation” in my yocto build (Poky ) . How do I add” recipes-navigation “ to my image? I have downloaded “ recipes-navigation “ from “open embedded project”. Is it compatible with yocto build (poky ) ? Note: Ultimately I wanted to integrate “Navit” to my image. “recipes-navigation “ has “navit”. How do I achieve this “Navit” integration in my image? Target Image: image-core-base Target machine : AM437x-evm Host Machine : Ubuntu 14.04 I am looking forward to your valuable reply. If you need any more details, Let me know please. Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] How to integrate third party application software to yocto image
Hi, I am new to this community.What does mean top post? Please see my bblayers.conf file content. # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf # changes incompatibly LCONF_VERSION = "6" BBPATH = "${TOPDIR}" BBFILES ?= "" BBLAYERS ?= " \ /home/winiston/poky/meta \ /home/winiston/poky/meta-yocto \ /home/winiston/poky/meta-yocto-bsp \ /home/winiston/poky/meta-ti \ /home/winiston/poky/meta-oe \ /home/winiston/poky/meta-multimedia \ /home/winiston/poky/meta-qt5 \ " BBLAYERS_NON_REMOVABLE ?= " \ /home/winiston/poky/meta \ /home/winiston/poky/meta-yocto \ " #added by hob BBFILES += "${TOPDIR}/recipes/images/custom/*.bb" #added by hob BBFILES += "${TOPDIR}/recipes/images/*.bb" I have copied meta-oe , meta-multimedia and meta-qt5 from meta-openembedded to /home/winiston/poky. It spits out the same error. Log output as given below. winiston@winiston-VirtualBox:~/poky/build$ bitbake core-image-base Parsing recipes: 100% || Time: 19:17:59 Parsing of 1760 .bb files complete (0 cached, 1760 parsed). 2285 targets, 196 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies ERROR: Nothing RPROVIDES 'navit' (but /home/winiston/poky/meta/recipes-core/images/core-image-base.bb RDEPENDS on or otherwise requires it) ERROR: navit was skipped: Recipe is blacklisted: bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES NOTE: Runtime target 'navit' is unbuildable, removing... Missing or unbuildable dependency chain was: ['navit'] ERROR: Required build target 'core-image-base' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-base', 'navit'] Summary: There were 2 ERROR messages shown, returning a non-zero exit code. winiston@winiston-VirtualBox:~/poky/build$ 1. What could be the problem? Since I could not proceed my project, Kindly help me to solve this issue. Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 -Original Message- From: Anders Darander Sent: Friday, February 26, 2016 3:03 PM To: openembedded-core@lists.openembedded.org ; yocto texas ; Yocto layer Subject: Re: [OE-core] How to integrate third party application software to yocto image Hi, Please, don't top post. * winis...@futuraautomation.com [160226 06:41]: I copied "recipes-navigation" folder from meta-oe (Open embedded build tree) to "/poky/meta " I have appended in “conf/local.conf” as given below IMAGE_INSTALL_append = " navit" While creating the image, it spits out the following error, winiston@winiston-VirtualBox:~/poky/build$ bitbake qt4e-demo-image Loading cache: 100% |##| ETA: 00:00:00 Loaded 1510 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing RPROVIDES 'navit' (but /home/winiston/poky/meta/recipes-qt/images/qt4e-demo-image.bb RDEPENDS on or otherwise requires it) ERROR: navit was skipped: Recipe is blacklisted: bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES This is the error. You have bluez5 in your DITRO_FEATURES, and I assume that navit requires bluez4? Anywya, it's blacklisted. NOTE: Runtime target 'navit' is unbuildable, removing... Missing or unbuildable dependency chain was: ['navit'] ERROR: Required build target 'qt4e-demo-image' has no buildable providers. Missing or unbuildable dependency chain was: ['qt4e-demo-image', 'navit'] Summary: There were 2 ERROR messages shown, returning a non-zero exit code. winiston@winiston-VirtualBox:~/poky/build$ Should I make any other setting to add the “navit” recipe to my image? Is this the correct method of copying "recipes-navigation" folder to "/poky/meta " ? Well, it works. If you don't mind the rest of meta-oe, I'd rather add that layer to conf/bblayers.conf. That would make it easier to get updates to e.g. navit. Cheers, Anders -- Anders Darander, Senior System Architect ChargeStorm AB / eStorm AB -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] How to integrate third party application software to yocto image
Hi Ross, I copied "recipes-navigation" folder from meta-oe (Open embedded build tree) to "/poky/meta " I have appended in “conf/local.conf” as given below IMAGE_INSTALL_append = " navit" While creating the image, it spits out the following error, winiston@winiston-VirtualBox:~/poky/build$ bitbake qt4e-demo-image Loading cache: 100% |##| ETA: 00:00:00 Loaded 1510 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing RPROVIDES 'navit' (but /home/winiston/poky/meta/recipes-qt/images/qt4e-demo-image.bb RDEPENDS on or otherwise requires it) ERROR: navit was skipped: Recipe is blacklisted: bluez5 conflicts with bluez4 and bluez5 is selected in DISTRO_FEATURES NOTE: Runtime target 'navit' is unbuildable, removing... Missing or unbuildable dependency chain was: ['navit'] ERROR: Required build target 'qt4e-demo-image' has no buildable providers. Missing or unbuildable dependency chain was: ['qt4e-demo-image', 'navit'] Summary: There were 2 ERROR messages shown, returning a non-zero exit code. winiston@winiston-VirtualBox:~/poky/build$ Should I make any other setting to add the “navit” recipe to my image? Is this the correct method of copying "recipes-navigation" folder to "/poky/meta " ? Kindly help me to resolve this error. Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 From: Burton, Ross Sent: Thursday, February 25, 2016 6:22 PM To: winis...@futuraautomation.com Cc: Maxin B. John ; yocto texas ; Yocto layer ; OpenEmbedded core Subject: Re: [OE-core] How to integrate third party application software to yocto image On 25 February 2016 at 12:51, wrote: IMAGE_INSTALL_append = " navit_svn" The recipe is called navit, _svn is the version. Just append " navit". Ross-- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] How to integrate third party application software to yocto image
Hi Maxin, I copied "recipes-navigation" folder from meta-oe (Open embedded build tree) to "/poky/meta " . Then I have added the below line in "/conf/local.conf" as given below. IMAGE_INSTALL_append = " navit_svn" Then I used bitbake to build the image. It spits out the following errors, winiston@winiston-VirtualBox:~/poky/build$ bitbake qt4e-demo-image Parsing recipes: 100% || Time: 00:01:35 Parsing of 1073 .bb files complete (0 cached, 1073 parsed). 1509 targets, 143 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies ERROR: Nothing RPROVIDES 'navit_svn' (but /home/winiston/poky/meta/recipes-qt/images/qt4e-demo-image.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'navit_svn' is unbuildable, removing... Missing or unbuildable dependency chain was: ['navit_svn'] ERROR: Required build target 'qt4e-demo-image' has no buildable providers. Missing or unbuildable dependency chain was: ['qt4e-demo-image', 'navit_svn'] Summary: There were 2 ERROR messages shown, returning a non-zero exit code. winiston@winiston-VirtualBox:~/poky/build$ What could be the problem? Where I have done the mistake ? Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 -Original Message- From: Maxin B. John Sent: Wednesday, February 24, 2016 7:41 PM To: winis...@futuraautomation.com Cc: OpenEmbedded core ; Yocto layer ; yocto texas Subject: Re: [OE-core] How to integrate third party application software to yocto image Hi Winiston, On Wed, Feb 24, 2016 at 06:20:14PM +0530, winis...@futuraautomation.com wrote: -- Hi, I can build yocto image for arm based product like AM437x-evm using yocto project. I want to add third party software(Navit) to my image. How can I add the third party software to my image ?. Can you provide me the steps to integrate third party software with yocto image ? Please read this documentation: http://www.yoctoproject.org/docs/1.4.2/dev-manual/dev-manual.html#usingpoky-extend-addpkg Note: Navit is a navigation software and it supports arm based product like AM437x. In the case of Navit, recipe is already available in meta-oe layer: http://cgit.openembedded.org/cgit.cgi/meta-openembedded/tree/meta-oe/recipes-navigation/navit/navit_svn.bb?h=master Host system: Ubuntu 14.04 Target system : AM437x-evm Regards, Winiston.P Futura Automation Pvt Ltd. Best Regards, Maxin -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] How to integrate third party application software to yocto image
Hi, I can build yocto image for arm based product like AM437x-evm using yocto project. I want to add third party software(Navit) to my image. How can I add the third party software to my image ?. Can you provide me the steps to integrate third party software with yocto image ? Note: Navit is a navigation software and it supports arm based product like AM437x. Host system: Ubuntu 14.04 Target system : AM437x-evm Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Error building core-image-sato
Dear, Yes, I added meta-ti layer in the bblayers.conf which is reside in /home/winiston/meta-ti and I used hob to create the image. My bblayers.conf contents as given below. # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf # changes incompatibly LCONF_VERSION = "6" BBPATH = "${TOPDIR}" BBFILES ?= "" #BBLAYERS ?= " \ # /home/winiston/poky/meta \ # /home/winiston/poky/meta-yocto \ # /home/winiston/meta-ti \ # " BBLAYERS_NON_REMOVABLE ?= " \ /home/winiston/poky/meta \ /home/winiston/poky/meta-yocto \ " #added by hob BBFILES += "${TOPDIR}/recipes/images/custom/*.bb" #added by hob BBFILES += "${TOPDIR}/recipes/images/*.bb" #added by hob BBLAYERS = "/home/winiston/poky/meta /home/winiston/poky/meta-yocto /home/winiston/meta-ti" What could be the problem? Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 -Original Message- From: Khem Raj Sent: Monday, February 22, 2016 7:38 AM To: winis...@futuraautomation.com Cc: OpenEmbedded core Subject: Re: [OE-core] Error building core-image-sato On Wed, Feb 17, 2016 at 9:02 PM, wrote: Dear, I tried to build core-image-sato. It spits out the following error. winiston@winiston-VirtualBox:~/poky/build$ bitbake core-image-sato Parsing recipes: 100% |###| ETA: 00:00:00 Parsing of 1060 .bb files complete (0 cached, 1060 parsed). 1496 targets, 138 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies ERROR: Nothing RPROVIDES 'xf86-input-tslib' (but /home/winiston/poky/meta/recipes-graphics/packagegroups/packagegroup-core-x11-xserver.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'xf86-input-tslib' is unbuildable, removing... Missing or unbuildable dependency chain was: ['xf86-input-tslib'] NOTE: Runtime target 'packagegroup-core-x11-xserver' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-core-x11-xserver', 'xf86-input-tslib'] NOTE: Runtime target 'packagegroup-core-x11-base' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-core-x11-base', 'packagegroup-core-x11-xserver', 'xf86-input-tslib'] ERROR: Required build target 'core-image-sato' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-sato', 'packagegroup-core-x11-base', 'packagegroup-core-x11-xserver', 'xf86-input-tslib'] Summary: There were 2 ERROR messages shown, returning a non-zero exit code. winiston@winiston-VirtualBox:~/poky/build$ How do I resolve this error? whats the content of your bblayers.conf, do you have some modifications to default configuration ? Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] Error building core-image-sato
Dear, I tried to build core-image-sato. It spits out the following error. winiston@winiston-VirtualBox:~/poky/build$ bitbake core-image-sato Parsing recipes: 100% |###| ETA: 00:00:00 Parsing of 1060 .bb files complete (0 cached, 1060 parsed). 1496 targets, 138 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies ERROR: Nothing RPROVIDES 'xf86-input-tslib' (but /home/winiston/poky/meta/recipes-graphics/packagegroups/packagegroup-core-x11-xserver.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'xf86-input-tslib' is unbuildable, removing... Missing or unbuildable dependency chain was: ['xf86-input-tslib'] NOTE: Runtime target 'packagegroup-core-x11-xserver' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-core-x11-xserver', 'xf86-input-tslib'] NOTE: Runtime target 'packagegroup-core-x11-base' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-core-x11-base', 'packagegroup-core-x11-xserver', 'xf86-input-tslib'] ERROR: Required build target 'core-image-sato' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-sato', 'packagegroup-core-x11-base', 'packagegroup-core-x11-xserver', 'xf86-input-tslib'] Summary: There were 2 ERROR messages shown, returning a non-zero exit code. winiston@winiston-VirtualBox:~/poky/build$ How do I resolve this error? Regards, Winiston.P Futura Automation Pvt Ltd. Ph :91-80-28375290 / 28375295 Fax :91-80-28375291 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core