HićMikko, On 2014-10-21 2:24 PM, Ylinen, Mikko wrote: > On Mon, Oct 20, 2014 at 11:34 AM, Damian Hobson-Garcia <[email protected]> > wrote: > >> >>> 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. >> > > OpenGL can be managed, e.g., with a common devel/headers package > and Provides/Conflicts. The boards specific libs RPM will be selected in > the image .ks file. > > See: > https://review.tizen.org/git/?p=platform/upstream/opengl-es-virtual-drv.git;a=tree;h=refs/heads/tizen;hb=refs/heads/tizen > Yes I see what you mean. After playing around with the tools a little it seems like multiple versions can happily co-exist provided that: 1) The pkgconfig file (or maybe the whole -devel package) is provided by only one version 2) Every image target (ks file but not board.conf) defines the version that it wants to use.
If this is correct, it seems possible that the emulator build might be able to exist in the same repo as the non-emulator version. Unless of course there is some other reason to separate them. And then maybe the same thing can work for the ARM builds as well. >> 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 >> > >> > > Yes, we could have this configuration in the IVI kernel .spec. > > >>> 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? >> >> > Yes Just to clarify, having multiple targets (board.confs) implies multiple repos, correct? That would seem to impact the scalability. Instead of multiple targets, is it possible to have multiple packages, one for each kernel variant, and have them all sit in the same repo, with the ks file doing the selection? Thanks, Damian > > -- Mikko > _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
