ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
ciara has quit [Read error: Connection reset by peer]
kien has joined #wayland
kien has quit [Quit: Leaving]
ciara has joined #wayland
Company has quit [Quit: Leaving]
ciara has quit [Read error: Connection reset by peer]
ciara has joined #wayland
junaid has joined #wayland
ciara has quit [Ping timeout: 480 seconds]
lsd|2 has joined #wayland
lsd|2 has quit []
lsd|2 has joined #wayland
lsd|2 has quit []
junaid has quit [Ping timeout: 480 seconds]
ciara has joined #wayland
ciara has quit [Read error: Connection reset by peer]
newbthenewbd has joined #wayland
junaid has joined #wayland
mvlad has joined #wayland
tent405 has quit [Quit: tent405]
<wlb>
weston Merge request !1331 opened by Marius Vlad (mvlad) backend-drm/meson.build: Require at least mesa 21.1.1 https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1331 [Backport to weston 10], [Backport to weston 11], [Backport to weston 12], [DRM/KMS backend]
ciara has joined #wayland
i509vcb has quit [Quit: Connection closed for inactivity]
iomari891 has joined #wayland
leon-anavi has joined #wayland
crombie has joined #wayland
sima has joined #wayland
crombie_ has joined #wayland
crombie has quit [Ping timeout: 480 seconds]
carlos_ has joined #wayland
junaid has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
caveman has quit [Remote host closed the connection]
<wlb>
weston/main: Philipp Zabel * libweston: Set the presentation clock in the compositor https://gitlab.freedesktop.org/wayland/weston/commit/1d59530e4b72 compositor/main.c include/libweston/libweston.h libweston/backend-drm/kms.c libweston/backend-headless/headless.c libweston/backend-pipewire/pipewire.c libweston/backend-rdp/rdp.c libweston/backend-vnc/vnc.c libweston/backend-wayland/wayland.c libweston/ba
<senatorM>
thasounds to millions of facts if encoded by minification in a clock cycle
<senatorM>
you will notice that those people say what i say, and overall there are flaws in calculating data allocations, memory wasting , so that needs new design
iomari891 has quit [Read error: Connection reset by peer]
iomari891 has joined #wayland
senatorM was banned on #wayland by ChanServ [*!~kelmid@*]
senatorM was kicked from #wayland by ChanServ [You are not permitted on this channel]
iomari892 has joined #wayland
iomari891 has quit [Read error: Connection reset by peer]
godvino has joined #wayland
iomari892 has quit [Ping timeout: 480 seconds]
lsd|2 has joined #wayland
lsd|2 has quit []
lsd|2 has joined #wayland
lsd|2 has quit []
lsd|2 has joined #wayland
lsd|2 has quit []
lsd|2 has joined #wayland
cmichael has joined #wayland
junaid has joined #wayland
junaid has quit []
junaid has joined #wayland
nerdopolis has joined #wayland
junaid has quit [Remote host closed the connection]
crombie_ has quit [Ping timeout: 480 seconds]
kts has joined #wayland
nerdopolis has quit [Remote host closed the connection]
nerdopolis has joined #wayland
MajorBiscuit has joined #wayland
<Zeroine>
There's 2 different sets of functions, variables, struct, etc. for the wayland client and wayland server library and header files, right? Like for example, after installing the wayland package I got one wayland-client shared library which I think contains the implementation of both the functions declared by the header file for low-level wire protocol and the high-level one which is
<Zeroine>
used for creating compositors or wayland clients. Is this correct so far?
<Zeroine>
I'm not sure which of the header files is exactly the low-level one and which is the high-level one. Wikipedia says the high-level one is generated by the XML. For me this is wayland-client-protocol.h which is identical to what `wayland-scanner client-header /usr/share/wayland/wayland.xml` returns but the wayland-client.h file which just includes both core and and protocol headers
<Zeroine>
says including only the core is encouraged (I think this implies it's the higher level API that's encouraged to be used)
<Zeroine>
So both of those statements conflict.
crombie_ has joined #wayland
crombie__ has joined #wayland
<Zeroine>
I noticed the functions that return wl_proxy (which according to the documentation aren't supposed to be used directly) are declared in the core header but they're only being used in the protocol header
crombie_ has quit [Ping timeout: 480 seconds]
<Zeroine>
actually nevermind
godvino has quit [Quit: WeeChat 3.6]
kts has quit [Quit: Leaving]
Company has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
<Zeroine>
don't know why the protocol header contains the definitions of functions though, I thought it would just be the declarations and the implementation is in pre-compiled in libwayland-client or libwayland-server
<kennylevinsen>
Zeroine: those functions are specific to the generated protocol. libwayland does just has the wire protocol logic, it has no knowledge of the protocols you run wayland-scanner on.
glennk has quit [Read error: Connection reset by peer]
glennk has joined #wayland
<MrCooper>
JPEW: it's because some of the "Base container" stage jobs really failed to complete their work, but incorrectly returned success; this could be fixed by updating to a newer ci-templates snapshot, meanwhile you can try manually retrying the base container jobs and then the failed build/test jobs