I think some words on how the workflow from an external consumer would be beneficial? I understand we cannot be prescriptive, as each may have different internal workflows, but which might be interesting is does the model place any constraints on their workflow? Maybe there is none. What is the vision of an external product vendor for example working with this model expected to operate? For example, the last step in the diagram is the download server - so is that the egress for them? Is it expected that they replicate the picture internally? They will probably be forced to. Should the build against pre-build binary rpms, or rebuild themselves? In summary - a nice presentation, but a go-to-product perspective missing for me.
> -----Original Message----- > From: Dev [mailto:[email protected]] On Behalf Of Patrick Ohly > Sent: Friday, November 28, 2014 8:02 AM > To: Kévin THIERRY > Cc: [email protected] > Subject: Re: [Dev] Call for feedback for a Candidate Tizen-Yocto based > workflow > > On Thu, 2014-11-27 at 17:14 +0100, Kévin THIERRY wrote: > > To build for armv7l you need to modify the MACHINE value in > > conf/local.conf. Maybe another layer will be needed to provide the > > correct MACHINE value (I know that qemuarm is available by default but > > I don't know about others...). Also if an external meta is used, one > > needs to make sure that the kernel version is the same as the one in > > Tizen > > (3.14.x) so there might be some work regarding this issue. > > > > Note that Annop Babu already began to work on this issue for iMX6 > > Sabre using the layer meta-fsl-arm. > > Xavier Roche also began to work on that a while ago but didn't get the > > time to fully make it work. > > > > Anybody who wants to look at the ARM build is more than welcome :) > > And Yocto is particularly tailored towards board enabling. There's even a > dedicated document about it: > http://www.yoctoproject.org/docs/1.7/bsp-guide/bsp-guide.html > > However, there's one caveat worth mentioning regarding the current > meta-tizen: all recipes converted from Tizen .spec files are based on a > configuration for x86 and Wayland (right?). Any bcond or ifarch special cases > for other configurations are not present in the generated .bb meta data. > > That's a known limitation that won't be fixed. Long-term, these auto- > generated files need to be replaced with hand-written .bb files. > > The conversion in the other direction will have to be more complete. > > -- > Best Regards, Patrick Ohly > > The content of this message is my personal opinion only and although I am an > employee of Intel, the statements I make here in no way represent Intel's > position on the issue, nor am I authorized to speak on behalf of Intel on this > matter. > > > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev -------------------------------------------------------------- Intel Shannon Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
