[PATCH wayland v2 0/8] Import wayland-egl frontend library

Emil Velikov emil.l.velikov at gmail.com
Tue Dec 12 16:03:29 UTC 2017

Hi Daniel,

On 13 November 2017 at 14:06, Daniel Stone <daniel at fooishbar.org> wrote:
> Hi Emil,
> On 8 November 2017 at 14:06, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>> On 10 October 2017 at 14:43, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>>> In summary - we want the user facing library to live in Wayland with
>>> vendors providing a backend/plugin.  Otherwise we'll get file conflicts
>>> as library can come from different vendors.
>>> Changes since v2 include:
>>>  - pushed multiple cleanups to Mesa and rebased the series on top
>>>  - cut down the fluff in the 1/9 commit message.
>>>  - use 17.4.0 version to avoid breakage of existing apps
>>>  - pass the DSO name (used in the symbol test) via the build system
>>>  - use local WL_EXPORT macro
>>> I've kept the import and build integration, since:
>>>  - the former is mechanical, while the latter involves some brain cells
>>>  - couple of changes were needed before building the imported code.
>>> Any formal Acked-by, Reviewed-by or other will be appreciated. Comments
>>> and suggestions are also welcome.
>> Humble ping?
>> Miguel already reviewed the [IMHO] important parts.
>> How can I help move the series forward?
> I haven't had / don't have time to review the last spin,
> unfortunately. But I'm happy for it to be merged if someone else can.
> There's definitely no danger of this missing the next release, mind!
Any suggestions who (and how) can I bribe to look at the series?
I've intentionally kept things dead trivial so that anyone can take a
look - yet no luck :-(

I am not asking that _you_ have to look through it, but I'm running
out of ideas.


More information about the wayland-devel mailing list