Hi Mikko, On 2014-10-20 2:34 PM, Ylinen, Mikko wrote: > On Mon, Oct 20, 2014 at 6:03 AM, Damian Hobson-Garcia <[email protected]> > wrote: > > >> 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 >> >> > I understand what you mean. However, there's no answer to your question yet. > Let's discuss it here.
Sounds great. I've updated the subject field to reflect the discussion topic a little better. > > >> 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. >> > > We have an independent build target in OBS for emulator and we get > a repository for it: > http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ > > However, having a separate target for each arm device is not scalable. > This particular challenge we need to solve within 'arm' target. I think that a similar issue may come up in certain packages, for example the OpenGL support, where it might be useful to have multiple versions of the same package in the repository at the same time. > > Right now we are building a generic arm kernel using > > # Default arch config for tizen per arch (unless overiden after) > %define kernel_image bzImage > %define defconfig tizen_defconfig > > In parallel to this discussion, we could enable your board as the default > 'arm' kernel > with this section in the IVI kernel .spec > > %ifarch %arm > %define kernel_arch arm > %define kernel_arch_subdir arch/%{kernel_arch} > %define kernel_image zImage > %define vdso_supported 0 > %define modules_supported 0 > %endif > > (just add the defconfig %define) > There is already a nice spec file in Philippe Coval's sandbox that handles the fact that the Renesas platform uses uImage files instead of zImage, the defconfig, etc. https://review.tizen.org/gerrit/gitweb?p=profile/common/kernel-common.git;a=shortlog;h=refs/heads/sandbox/pcoval/rcar-m2 > The .spec file could also have multiple defconfigs for arm and then each > profile > can select the default one using a bcond option. Does selecting one image using bcond require multiple targets? Thanks, Damian _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
