On 17 May 2016 at 23:24, Richard Purdie
<richard.pur...@linuxfoundation.org> wrote:
> On Tue, 2016-05-17 at 11:00 -0300, Otavio Salvador wrote:
>> On Tue, May 17, 2016 at 5:38 AM, Burton, Ross <ross.bur...@intel.com>
>> wrote:
>> >
>> > On 17 May 2016 at 08:31, Jussi Kukkonen <jussi.kukko...@intel.com>
>> > wrote:
>> > >
>> > > There's not much to work on as far as I can tell: 1.11 should be
>> > > a
>> > > simple upgrade with trivial patch changes.
>> > > As I said, I'm totally fine with waiting a couple of weeks until
>> > > 1.11.
>> > > On the other hand I haven't seen any reasons to start packaging a
>> > > pre-release -- why this one if we normally don't do it?
>> >
>> >
>> > Agreed, if we want an upgrade now then 1.10 is good, otherwise wait
>> > for
>> > 1.11. There's no urgent need for a prerelease is there?
>>
>> So please do 1.10 now, as the XWayland rework was done basing on that
>> ... we can handle 1.11 upgrade once it happens.
>
> I fixed up the selftest failure the original patch as proposed caused
> and have merged that. Anything further can be based on that...
Thanks RP.
Explanation for anyone coming to this thread wondering why the weston
recipe does what it does:
* wayland-protocols is allarch because it's just xml files
* weston needs to add WAYLAND_PROTOCOLS_SYSROOT_DIR=${STAGING_DIR}/${MACHINE}
to EXTRA_OECONF to find the xml files as PKGCONFIG_SYSROOT_DIR would
point to the wrong
place when weston is multilib -- allarch files are in machine
sysroot, not multilib sysroot
* this leads test_sstate_sametune_samesigs test to fail, which RP
silenced by adding
EXTRA_OECONF[vardepsexclude] = "MACHINE"
Simples!
Any other wayland compositor recipe will have to do similar things.
- Jussi
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
