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

Burton, Ross ross.burton at intel.com
Thu Apr 7 10:32:00 UTC 2016


On 7 April 2016 at 10:57, <winiston at futuraautomation.com> wrote:

> 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.
>

core-image-base doesn't come with a GUI, so I'm not sure what you expect.
If you want navit to start up on boot then that's part of the integration
that you'll have to do.


>
>
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?
>

The packages are the ones listed in the PACKAGES variable in the recipe.
You install them by listing more of them in your INSTALL_IMAGE_append
assignment.


> 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?
>

No idea, I've never used or even look at navit before. You'll have to look
at the contents of the packages to understand what is being put in what
package (or just install all of them).

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160407/bbc336ef/attachment-0002.html>


More information about the Openembedded-core mailing list