Hi Mikko,
On 2014-10-23 12:31 PM, Damian Hobson-Garcia wrote:
> 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
>>
It seems that the emulator build uses Prefer: statement in the OBS
configuration to select the mesa versions of the OpenGL packages for
linking. I think that something similar is necessary for the ARM
configurations as well. Do you think that it would be possible to have
the mesa libraries listed as Prefer for the non emulator builds as well?
i.e. the current configuration is:
%if "%_repository" == "emulator"
Prefer: mesa-libGLESv2
Prefer: libwayland-egl
Prefer: libgbm
Prefer: mesa-libGL
Prefer: mesa-libEGL
Prefer: emulator-yagl
...
%endif
I am proposing:
Prefer: mesa-libGLESv2
Prefer: libwayland-egl
Prefer: libgbm
Prefer: mesa-libEGL
%if "%_repository" == "emulator"
Prefer: mesa-libGL
Prefer: emulator-yagl
...
%endif
It looks like the settings files in scm/meta/build-config are generated
from the OBS settings, so I'm not sure if this suggestion should be
submitted through gerrit to the scm/meta/build-config project or
somewhere else.
Also, to add to the previous rules that I listed for having multiple
versions(i.e. for different ARM platforms or configuration) of the same
library in the same repo,
> 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 (master) version
> 2) Every image target (ks file but not board.conf) defines the version
> that it wants to use.
3) The master version is preferred for building by using a
"Prefer:" statement in the build.conf
Comments from anyone interested in this regarding the above "rules" or
the suggestion to change the Prefer: statements are very welcome and
would be greatly appreciated.
Thanks,
Damian
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi
