[meta-freescale] problems adding python to build
David Van Beveren
vbdavid at gmail.com
Thu Dec 20 10:31:30 PST 2012
I have been exploring yocto for the Freescale ARM boards (I have an
i.MX28-evk) for about 2 weeks now. I understand all of the basics but have
not had much success customizing the images.
I am using the danny release.
I would like to build an image that contains:
python and pyopenssl
a local gnu toolchain on the target
gdb / gdbserver
NFS server and client
the Google API python client library (typically installed with
My own python program
My own C++ apps
I have had success configuring the kernel and busybox already using
bitbake. (I have turned on IPv6, NFSserver, ftp, etc)
I am able to build the standard images (e.g. core-image-minimal, -lsb, and
I have had some problems experimenting with hob. However, this seems to
just add another layer, and I am just as comfortable doing this by hand.
My approach has been to create a copy of the .bb file for the image, in the
same folder as the original, (poky/meta/recipies-core/images) then edit
Side Q: Is this the best approach? Should I be adding files to the
sources folder or should I be keeping them outside?
Here is one cut at my image file, my-image-lighttpd, between the dashes:
IMAGE_INSTALL += "python_2.7.3 lighttpd"
I get a message in response that 'nothing PROVIDES python_2.7.3' This is
confusing to me because I can see such a recipe:
NOTE that when I remove the python entry and just keep the lighttpd entry
it works fine.
The Yocto docs talk about a variety of approaches to customizing images,
from editing local.conf to creating a new layer. I am interested in the
simplest approach that does not run against the grain of what the designer
Once I am able to add the Python packages I think I will understand enough
to move on.
I believe that the fsl/yocto/poky/oe pltform is the bet embedded build
platform I have seen. I have used buildroot in the past and when I started
working on this Freescale board I dove in to ltib but quickly thought about
moving to either OE or buildroot, when I discovered Yocto and your group.
It is a very impressive open source project, and I am looking forward to
contributing where I can.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the meta-freescale