[Wayland-bugs] [Bug 91799] Usage of timerfd_create and signalfd prevent porting to non-linux platforms

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=91799

Jonas Ådahl <jadahl at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jadahl at gmail.com

--- Comment #3 from Jonas Ådahl <jadahl at gmail.com> ---
(In reply to Pekka Paalanen from comment #2)
> I am scared to even think of what spawning a thread in libwayland-server
> would cause.
> 
> An alternate proposal to this problem would be to deprecate the whole server
> event loop implementation in Wayland. It obviously has never worked on BSDs,
> so BSDs could start by compiling a version of libwayland-server which does
> not have that API (or plug it with stubs).
> 
> But this is major design change. We would need to plan how to gracefully
> deprecate the event loop API everywhere, and port all users to third party
> event loop libraries. Therefore it requires a significant buy-in from the
> community.
> 
> I recall Jasper saying that Gnome's compositor does not use the event loop
> stuff of libwayland-server, because they already have their own. I wonder
> what others do.

In mutter we do use the event loop. We just add the fd to our event loop and
dispatch on input on that fd, more or less.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20150831/3481194c/attachment.html>