[yocto] Mentor's Application Development Environment (ADE)

[Zhang, Jessica]

Hi Chris,



Base on your description, we have a similar use case that is supported by adt-installer for app developers using Eclipse, which based on ipk repo but mainly for setup the host cross tools. It also takes care of setting up sysroot but through extracting the target image file instead of using package repo. I think your proposal compliment that use case by providing a way to setup sysroot using P2 repo.  And we can look into leveraging your work of coverting ipk into P2 which allows us through Eclipse to install the cross tools on the host.



We’re starting to look into our 1.3 features and we’ll have a discussion about it at collab summit which I’m planning to attend. This is definitely something interesting and if possible, I’d like to flesh out more on it with you during collab.



Thanks,

Jessica



From: yocto-bounces at yoctoproject.org [mailto:yocto-bounces at yoctoproject.org] On Behalf Of Christopher Larson
Sent: Thursday, March 08, 2012 1:21 PM
To: yocto
Subject: [yocto] Mentor's Application Development Environment (ADE)



Greetings folks,



I'm emailing to ascertain the potential interest in a piece of functionality Mentor has been including in our MEL product, and see if it'd be something either we could push up under the Yocto umbrella, or potentially reimplemented in concert with upstream folk to better meet folks needs.



This feature is a means of distribution of sysroot content (libraries, headers, potentially host scripts and binaries) from the person doing the bitbake builds to a potential application developer using eclipse. This is a different approach than that taken by the ADT, as this doesn't require a poky development environment, so is potentially more useful for application developers.



In concept it's quite simple. We construct an eclipse P2 IU (installable unit) and binary artifact for every binary package we emit, and build a P2 repository with those. This repository can be added to eclipse, and you can pick and choose any of the packages we emitted, including -dev, -dbg content and it installs it into a sysroot relative to the eclipse install directory, where you could then point your application project. It's really not unlike adding a new package management format, as that's what P2 really is, a package management / content distribution system. I think it provides a fair bit of value, but I'd like to get the opinions of others on this.



The current implementation has a python script which converts an ipk package repository into a p2 repository. I intend to move toward a package_p2.bbclass type approach, emitting xml snippets for each along with the artifact as we go, and then have the feed construction reassemble the component metadata into the appropriate artifact and IU xml files, which would more closely mirror the way our other package management formats behave.



Thoughts?

--

Christopher Larson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20120308/714b54cf/attachment.html>