ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
ybogdano has quit [Ping timeout: 480 seconds]
NepNepdmsalwaysopen[m] has joined #wayland
<NepNepdmsalwaysopen[m]>
Hello! I'm working on implementing hyprland_toplevel_export_v1, using handles from zwlr_foreign_toplevel_manager_v1 to indentify toplevels in capture_toplevel_with_wlr_toplevel_handle (part of the first protocol). Since I'm new to wayland development and using zig-wlroots/zig-wayland, there's something I haven't been able to figure out yet: The request data includes a pointer to the server.zwlr.ForeignToplevelHandleV1 of
<NepNepdmsalwaysopen[m]>
the toplevel it wants to capture, that handle type is automatically generated by the zig-wayland build system, but the handles stored in the compositor I'm working on (river, though I'm forking it rather than making a PR since as far as I know the maintainer wants to wait for a standard way to do it) are stored as the zig-wlroots version, which isn't automatically generated, what I don't know is how to compare them.
navi has quit [Quit: WeeChat 3.8]
ahartmetz has quit [Quit: Konversation terminated!]
Brainium has quit [Quit: Konversation terminated!]
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
crazybyte has quit [Ping timeout: 480 seconds]
crazybyte has joined #wayland
tzimmermann has joined #wayland
manuel1985 has joined #wayland
test has joined #wayland
test has quit [Remote host closed the connection]
sima has joined #wayland
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #wayland
manuel1985 has quit [Ping timeout: 480 seconds]
manuel1985 has joined #wayland
rv1sr has joined #wayland
bodiccea_ has joined #wayland
rasterman has joined #wayland
iomari892 has joined #wayland
<any1>
NepNepdmsalwaysopen[m]: What does hyprland_toplevel_export_v1 do?
<any1>
Nm, I found it. :)
<any1>
Looks like screencopy for toplevels.
sima has quit [Ping timeout: 480 seconds]
<kennylevinsen>
NepNepdmsalwaysopen[m]: a normal use of these would be to attach some data to the handle where it is created, which can then be referenced whenever a call is made using that object
<kennylevinsen>
for the wlroots implementation, wlr_foreign_toplevel_handle_v1 has a data pointer you can attach anything to
<kennylevinsen>
this can in turn be referenced in the hyprland_toplevel_export_manager_v1.capture_toplevel_with_wlr_toplevel_handle handler
TheKnownSecret has joined #wayland
<pq>
emersion, re: VKMS configfs; Yay! \o/
cmichael has joined #wayland
TheKnownSecret has quit [Quit: TheKnownSecret]
crazybyte has quit [Ping timeout: 480 seconds]
crazybyte has joined #wayland
fmuellner has joined #wayland
bodicceaII has joined #wayland
caveman has quit [Remote host closed the connection]
<pq>
right, that's the part that I guessed and is fine by me.
<psykose>
in what way does that decrease performance
<pq>
good question, they are library calls to begin with
<emersion>
maybe libc has it static inline in a header or something
<emersion>
or maybe libc has clever LTO stuff
Leopold_ has joined #wayland
<pq>
if it did, we couldn't override them like we do?
<emersion>
hm, that's true…
<emersion>
hm, and the LTO is not possible
<emersion>
LTO is just inside a single .so
<emersion>
so yeah, probably doesn't matter anyways
<emersion>
i guess LTO _could_ happen if you statically link libc
<pq>
I'm more worried about having two vfuncs for the same thing, one in libwayland-server and one in libwayland-client, and those somehow getting mixed up by e.g. the tests trying to modify them.
<pq>
the build of 'test_runner' links curiously many things...
<kennylevinsen>
emersion: if you statically link libc I assume you also want to statically link libwayland, and then you get all the LTO
<emersion>
pq, wouldn't these share the same wayland-os.o?
<emersion>
hm
<pq>
oh right, os-helpers are explicitly linked statically, so they can be tested, since none of them are exported
<pq>
emersion, it doesn't reduce duplication if the same .o is copied into two .so
<emersion>
yea
<pq>
but I think it should be just fine - don't export anything
<pq>
the test will be testing its own copy of the .o, not going through the .so
<wlb>
weston/main: Daniel Stone * build: Switch join_paths(foo, bar) to foo / bar https://gitlab.freedesktop.org/wayland/weston/commit/386dcd904fda compositor/meson.build data/meson.build doc/sphinx/meson.build libweston/meson.build man/meson.build meson.build