[OE-core] Problem in Third party Software (Navit) integration

winiston at futuraautomation.com winiston at futuraautomation.com
Thu Apr 7 07:41:02 UTC 2016


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 at winiston-VirtualBox:~/poky$ source oe-init-build-env
### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

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 at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160407/cb99fb6a/attachment-0002.html>


More information about the Openembedded-core mailing list