Hi Patrick, Leon, Vitaly & all :)

Thank you very much for your feedback. It definitely shared some light 
regarding the current options.



> -----Original Message-----
> From: Patrick Ohly [mailto:patrick.o...@intel.com]
> Sent: Monday, May 11, 2015 3:50 PM
> To: Vitaly Chernooky
> Cc: Leon Anavi; ivi@lists.tizen.org; de Queiros, Pedro
> Subject: Re: [IVI] tizen ivi for the Renesas R-Car M2 ARM platform using 
> yocto?
> 
> On Mon, 2015-05-11 at 15:55 +0300, Vitaly Chernooky wrote:
> > Hi Leon,
> >
> > On Fri, May 8, 2015 at 4:32 PM, Leon Anavi <leon.an...@konsulko.com>
> > wrote:
> >         Hi Pedro,
> >
> >         On 8.05.2015 14:59, pedro.quei...@elektrobit.com wrote:
> >                 Hi all,
> >                 I have started an attempt to build tizen ivi for the
> >                 Renesas R-Car M2 ARM platform (Koelsch board), one of
> >                 the goals would be to attempt graphics hw acceleration
> >                 with the proprietary drivers.
> >                 There are some instructions available in the wiki
> >                 regarding using gbs. Nevertheless I wonder whether
> >                 someone did or is in the process going the same using
> >                 yocto?
> >
> >         Building Tizen:Common or any of the Tizen profiles based on it
> >         (like IVI) for ARM using Yocto isn't easy task. In my opinion
> >         the Yocto recipes are not perfect and you will have numerous
> >         challenges if you try to build them for any devices with CPU
> >         different from Intel.
> >
> >
> > I have different opinion on it. According to my experience with Yocto,
> > it is much more easier to build for ARM with Yocto than with gbs ;)
> 
> The comment was about the "Tizen on Yocto" recipes, not Yocto. The recipes
> have issues that you don't see when building recipes manually written for
> Yocto.
> 
> These recipes get converted from .spec files to .bb files based on the build
> configuration for x86. All architecture specific tweaks in Tizen get lost at 
> that
> point and have to be added back manually to the generated .bb files.
> 
> The spec2yocto conversion tool also does not have enough information
> available in the .spec files about dependencies (is a tool needed or something
> to link against?) and has to use heuristics, which fail in some cases when 
> doing
> cross-compilation.
> 

 [PQ] Just to understand a bit better the plan to support both build systems. 
Are the .spec files intended to contain the "master" information and yocto 
recipes shall be considered generated code.
Thus, for the generated recipes, manual adaptations shall take into account the 
generation process (to avoid conflicts)?

Or are the generated recipes an outcome of first yocto integration step but in 
the mid/long term the plan in to adapt/rewrite them manually? Thus generation 
compatibility is not the main focus?

> --
> 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.
> 
> 

Best Regards,
Pedro Q.


----------------------------------------------------------------
Please note: This e-mail may contain confidential information
intended solely for the addressee. If you have received this
e-mail in error, please do not disclose it to anyone, notify
the sender promptly, and delete the message from your system.
Thank you.

_______________________________________________
IVI mailing list
IVI@lists.tizen.org
https://lists.tizen.org/listinfo/ivi

Reply via email to