[yocto] creating images which include actively developed applications

[Khem Raj]

> On May 5, 2015, at 6:35 PM, michael_e_brown at dell.com wrote:
> 
> Dell - Internal Use - Confidential
> 
> We use the google android “repo” tool plus ‘externalsrc’ to great effect. 3 generations now, across now 6-ish different products and dozens of releases at this point. It checks out poky, our layer, our source mirror, and our internal sources all at once.

well, I have similar setup with repo hooks to generate an auto.conf with needed info about externalsrc components from repo groups and it works well however it really depends upon how much software you build on top if its a thick middleware + apps then
we loose the sstate reuse and if you have components which are needing to be dependency for something like qtwebkit then
its going to be even further degraded build performance for developers. Most of the times the dependencies are not changing APIs and interfaces but rebuild still happens since the component has changed we have no way to determine if the components APIs changed or not. It would be nice if build system could have such a tool to register certain APIs which could be added to rebuild decision checksum to make it more fine grained.

> --
> Michael
> 
> -----Original Message-----
> From: yocto-bounces at yoctoproject.org [mailto:yocto-bounces at yoctoproject.org] On Behalf Of Paul Eggleton
> Sent: Tuesday, May 05, 2015 3:32 AM
> To: Trevor Woerner
> Cc: yocto at yoctoproject.org
> Subject: Re: [yocto] creating images which include actively developed applications
> 
> On Friday 01 May 2015 16:25:38 Trevor Woerner wrote:
> > On 04/22/15 13:58, Paul Eggleton wrote:
> > > On Wednesday 22 April 2015 15:32:06 Brian Karcz wrote:
> > >> Is there a way to create a recipe to build actively developed code
> > >> located in an external source directory? Basically skip the fetch
> > >> and unpack steps and always execute the compile and populate steps
> > >> each time and image is built?
> > >
> > > Indeed there is:
> > >
> > > http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#
> > > buildi
> > > ng-software-from-an-external-source
> >
> > Paul, I'm surprised you suggested externalsrc instead of just
> > mentioning devtool right from the start (doubly-surprised since you're
> > the person who wrote devtool!). Using devtool the "administration" (of
> > creating a recipe, etc) is done for you, no?
> >
> > http://twoerner.blogspot.ca/2015/01/the-yocto-project-introducing-devt
> > ool.ht
> > ml
> 
> Well, I would have, except this doesn't quite seem like the same case as devtool is designed for (which is "temporary" switching of the source for development - AIUI Brian was looking for something more permanent.)
> 
> Cheers,
> Paul
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org <mailto:yocto at yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20150505/510b818f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20150505/510b818f/attachment.pgp>