ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
tzimmermann has quit [Ping timeout: 480 seconds]
Lucretia has quit []
pnowack has quit [Quit: pnowack]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
onelegend has joined #wayland
twb has joined #wayland
<twb>
Just because I'm curious: I see wayland exists on Linux and BSDs. How much "stuff" is needed to put it on some new OS? Like say seL4 or NTOSkrnl or android?
<twb>
Is it like "we basically assume gnu/linux everywhere and if you aren't that, it's your problem?" or is it the other extreme of like "as long as you have POSIX.1 and a way to do framebuffers, you just need to port this one bit"
<pq>
twb, mind that libwayland itself is only a tip of the iceberg. Making that lib work on a new OS still gets you nowhere, you need at least one compositor and some apps (toolkits) too.
<pq>
twb, however, once you do have libwayland, your compositor could be finger-painting on rocks if you wanted to.
<twb>
I thought we were mostly talking about the compositor/wayland server process
<twb>
since the apps just talk a standard protocol to a AF_UNIX socket or something, right?
<pq>
twb, when you talk about wayland, people here usually think libwayland and protocol, not compositors.
<twb>
Righto
<pq>
there is no "the Wayland compositor", there are many different compositors with hugely differing requirements.
<pq>
compositor is another word for a Wayland server
<pq>
libwayland-server only has the IPC bits (and the event loop bits) of a server but not an actual server implementation
<pq>
well, it has few implementation bits but those are a tiny fraction of a complete server implementation
<pq>
twb, another thing about another OS is that there are some Wayland extension that have been written for Linux specifically, most importantly zwp_linux_dmabuf_v1 which is used for passing GPU-rendered images around. Software rendered images OTOH do not need that one.
xexaxo_ has quit [Ping timeout: 480 seconds]
<emersion>
twb, in terms of BSD support, there are a few wayland compositors in the FreeBSD repos
<emersion>
including some with upstream FreeBSD support, and some even written with FreeBSD as the primary target
bodiccea has quit [Remote host closed the connection]
bodiccea has joined #wayland
bodiccea has quit [Remote host closed the connection]
bodiccea has joined #wayland
<whot>
jadahl: oh. I disabled docs by default, the meson invocation needs a -Ddocumentation=true or something. Can do this tomorrow if you don't beat met to it
rapha has joined #wayland
xexaxo_ has joined #wayland
<rapha>
hi all, i'm getting very annoyed with where windows open on X. with wayland, is there a way that a window will either open on the same screen as the parent window (i.e. in the case of a dialog) or on the screen that has the mouse cursor, but never on any screen fulfilling not one of these two conditions?
<SardemFF7>
it’s up to the compositor, mainly the same an X11 (up to the WM, but any other program can interfere)
hardening has quit [Read error: Connection reset by peer]
hardening has joined #wayland
<SardemFF7>
OTOH, other apps cannot interfere, and metadata may be more useful to the compositor to do meaningful placement
<pq>
SardemFF7, oh hey, haven't seen you in a long while. :-)
slattann has quit []
slattann has joined #wayland
<SardemFF7>
hi pq :-)
<SardemFF7>
I’ve been lurking around, trying to keep up-to-date
slattann has quit [Read error: Connection reset by peer]
<daniels>
I have no objection to a Wayland release; I wanted to delay Weston because it seemed like dmabuf-hints was a matter of days away, but then that ended up somewhat derailed
<daniels>
I've let that sit for a couple of weeks but will come back to it and see if there's any prospect of resolution within bounded time
hendursaga has quit [Quit: hendursaga]
hendursaga has joined #wayland
<emersion>
part of that is on me, need to update the protocol
<emersion>
but protocol work is very headache-happy
zumbi has quit [Ping timeout: 480 seconds]
<daniels>
:)
TimWolla has quit [Quit: Bye]
TimWolla has joined #wayland
<pq>
daniels, when you replaced EGL_DEFAULT_DISPLAY with NULL, what prompted you to do that?
jgrulich_ has quit [Ping timeout: 480 seconds]
<daniels>
pq: disappointment, frustration, rage - pick any and/or all of them
<daniels>
I think the specific catalyst was clang on ARMv7
<pq>
daniels, should I guess that it triggered some compiler warning-as-error somewhere?
<daniels>
^ yeah
<pq>
oh, ok
<daniels>
EGLNativeDisplayType and thus EGL_DEFAULT_DISPLAY are only defined by magic heuristics
<pq>
would have been nice to mention that in the commit message
<daniels>
and IIRC on clang/armv7 it was landing on an int or long type for ... well I don't know why
<daniels>
whereas we internally type it as void* since we don't have any non-pointer display types
<rapha>
SardemFF7: ah, so window placement isn't wayland's job, but it makes it easier to the program that used to be the window manager under X11 to do it properly?
xexaxo_ has quit [Ping timeout: 480 seconds]
d_ed has quit [Remote host closed the connection]
nik has joined #wayland
boistordu_ex has joined #wayland
Erandir has joined #wayland
leon-p has joined #wayland
xexaxo_ has joined #wayland
zebrag has joined #wayland
fmuellner has joined #wayland
Narrat has joined #wayland
pnowack has quit [Ping timeout: 480 seconds]
fmuellner has quit [Remote host closed the connection]