Hi Dominig, Unfortunately I was not in Germany and so wasn't able to hear Stéphane's presentation first hand. Thank you for the slides, but I think that the topic is a little different from what I'm trying to figure out.
I don't want to create a new profile. I want to have a way within a profile (IVI in this case) to know if the build is for the Renesas platform or not. I understand that its possible to differentiate between ARM and Intel with an "ExclusiveArch:" in the spec file, but what about differentiating between different ARM platforms? (or Intel "platforms" in the case of emulation). I've also made a mention of this issue last week in this bug report: https://bugs.tizen.org/jira/browse/TC-1464 Looking at what is done for emulation, there is a separate build config, build-emulator.conf, that sets up emulator specific values. Is this the recommended way to do this? It looks like it results in a rebuild of all Tizen packages on the OBS. Thank you, Damian On 2014-10-17 4:34 PM, Dominig ar Foll (Intel OTC) wrote: > Damian, > > you obviously were not in Germany this week, otherwise you would have > followed > Stéphane presentation on Wednesday afternoon. > > As all the slides are not yet available on the Linux Con web site, this link > will give you early access to his slide desk. > "Creating a profile from Tizen:Common". > > Let us know if you have more question. > > https://drive.google.com/folderview?id=0B1s7BiE7yLZQelkwYnNlcTN6M0E&usp=sharing > > Regards > > Dominig ar Foll > Senior Software Architect > Open Source Technology Centre > Intel SSG > > Le 17/10/2014 04:32, Damian Hobson-Garcia a écrit : >> Hi Dominig, >> >> Thanks for all of your assistance so far. >> >> I have a question about how best to integrate the kernel build (and the >> platform as a whole) for the Renesas and Intel platforms. >> >> If both platforms are building the kernel from the same source package, what >> is the best way to handle the fact that they both require different >> configurations and build processes? Is it best to test for variable in the >> spec file and if so, what is the best way to set the variable value? Is >> setting it in build.conf the best option? >> >> I can do this for a local build without too much trouble, but from what I've >> seen of obs it looks like that means defining a whole new build >> configuration. Is that the only way to go? >> >> Thanks, >> Damian >> >> >> >> On 12 September 2014 17:49, Dominig ar Foll (Intel OTC) >> <dominig.arf...@fridu.net <mailto:dominig.arf...@fridu.net>> wrote: >> >> Le 11/09/2014 17:26, hisao munakata a écrit : >> >> >> Personally I have no objection to migrate to 3.14-LTSI for baseline >> code. >> Possible problem is middleware compatibility and delivery. I will >> check when >> and how we can deliver them using through click-through type easy >> manner. >> >> Anyway now I can understand your suggestion. I will consider this. >> >> >> Thanks for your comprehension. >> >> Unfortunately ARM based CPU have always some non open source drivers >> which >> are pain when it come to Kernel upgrade. >> Picking up the LTS kernel is the least painful option that we could come >> up with. >> >> The pain point for us at Intel is in the opposite direction as new IA SoC >> come with of the shelves support in latest kernel and we will need to >> back-port to 3.14. >> >> Let us know if we can help you in any way to ease your move to 3.14. >> >> Regards >> >> Dominig >> >> _______________________________________________ >> IVI mailing list >> IVI@lists.tizen.org <mailto:IVI@lists.tizen.org> >> https://lists.tizen.org/listinfo/ivi >> >> > _______________________________________________ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
