[poky] building images

[Zhang, Jessica]

Michael,



See my comments below...



Thanks,

Jessica



From: C Michael Sundius [mailto:msundius at sundius.com]
Sent: Wednesday, April 27, 2011 11:41 AM
To: openembedded-devel at lists.openembedded.org; poky at yoctoproject.org; josh at linux.intel.com; Zhang, Jessica
Subject: building images



I'm wondering if when bitbake builds an image, that is to say if all the necessary package recipes have already been completely built, if just when creating the image, does bitbake make use of the staging/sysroot directory at all? or does it only install packages and run some scripts for pre and post processing of the image?....



could we get away with simply simply providing the packages or a package feed for this step?



as I write this, I guess we'd be missing the native tools in the sysroot/i686-linux/* directory. lets just say we have told bitbake that it should use the native tools from the build host for *everything*.



I'm asking this because I want a way for our customers to use an SDK (that we provide from OE) to build an app,



Yocto project has a command line script called adt-installer probably you can take a look, what it does is setup your host cross development environment.  It downloads the cross-toolchain for the target and download the corresponding image rootfs and extract it out on the development host as sysroot that contains the target headers and libraries.  The remote package access is based on wget and it's using opkg to manipulate ipk packages since it's lightweighted.  The adt-installer is running against a installation config file basically tells it where (the ipk package repo) to download things and where (on the development host) to setup things, the toolchain, the sysroot etc.  So for the developer perspective, there's no dependency on OE.  What you need to do is to build out all the needed ipk packages using OE/Yocto and setup the ipk package repo.



and then create an image that is equivalent to one that would have been created from within the OE environment (will all the package recipes).





My problem is that some of our customers will not adopt OE for developing applications. (I think they should, but we just can't guarantee that they will, nor do I think we should force them).



If we provide:



1) an SDK that includes:

- all of our interfaces,

- all of our utilities and branding info

- the tool chain,

- some or all the other native utilities (or maybe just take chances that the build host is not Fedora Core 3!)

2) the packages or a link to a package feed with all of our packages necessary for the release



what would the minimal config and class info we'd need to create an image with bitbake?



would this be useful or would it be just as much work to get my customers to build their app with an OE recipe?



anyone have any thoughts on as much?



Does anyone else have the problem that they need to create an image from the result of an SDK? What do you do to solve the problem?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/poky/attachments/20110429/20808b7a/attachment.html>