<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Usage of timerfd_create and signalfd prevent porting to non-linux platforms"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91799#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Usage of timerfd_create and signalfd prevent porting to non-linux platforms"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91799">bug 91799</a>
from <span class="vcard"><a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> <span class="fn">Pekka Paalanen</span></a>
</span></b>
<pre>I take my idea back. I had a chat with Jonas in IRC, and realized that pulling
essentially all event loop features out of libwayland-server would be more work
than I imagined. The single fd you can currently get from the wl_display's
wl_event_loop considers not only all server sockets but all clients too, at
minimum. We'd need much of new API to deal with all that, and furthermore
deprecating anything from a public ABI in a stable library is going to be
painful.
Now I believe that contributions to implement the features in libwayland that
do not work currently on non-Linux are welcome. I wasn't too sure before.
This way all the burden of implementing and maintaining alternate code paths is
on the people working on non-Linux OS's.
And just now I realized you're probably not talking about BSD but Haiku. :-)
I would prefer if we could do the OS-specific things mostly as which .c files
to build in, rather than an #ifdef hell.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>