On Tue, 2015-05-12 at 07:15 +0000, pedro.quei...@elektrobit.com wrote: > > 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.
That's how it is at the moment. See also my description of the procedure that I used to handle such manual fixes when I (temporarily!) took over maintenance of "Tizen on Yocto": https://lists.tizen.org/pipermail/dev/2015-January/006017.html > 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? There was work on switching to conversion from .bb to .spec. See https://lists.tizen.org/pipermail/dev/2014-December/005685.html Having said that, I don't know what the plan is for this year. I'm not currently working on "Tizen on Yocto". -- 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. _______________________________________________ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
