Welcome to tomaka/glutin, the official gitter channel for Glutin and Winit! - Github: https://github.com/rust-windowing/glutin, https://github.com/rust-windowing/winit - Crates.io: https://crates.io/crates/glutin, https://crates.io/crates/winit - Docs: https://docs.rs/glutin/0.21.0/glutin, https://docs.rs/winit/0.20.0/winit/
so what should be checked for is
-C target-feature=+crt-static, but I'm not sure if a crate can check for it
1 reply
this is because I think the
*-unknown-linux-musl targets may default to dynamically linking musl in the future
I can't recall the exact issue on github where I read this, so don't quote me on that
I guess I'll dig into that sometime
winit is using wlroots right? how do I find which commit of wlroots is being used?
wlroots is a compositor framework/library
to my knowledge
I don't know what effect statically linking
libwayland-client.so has
so idk if it's that or cage
or maybe even smithay-client-toolkit
the thing I'd try myself is to link to glibc and see if that works, but I don't know if your distro specifically avoids glibc
1 reply
hm, so
cage weston-flower, cage sway and sway work and produce a [backend/drm/drm.c:1594] drmHandleEvent failed error when exiting. cage mewronoi-gnu aborts and also shows that error, but before that pixels fails to find an adapter.$ cage -s ./mewronoi-gnu
[src/lib.rs:80] window.inner_size() = PhysicalSize {
width: 1920,
height: 1080,
}
Error: AdapterNotFound
00:00:01.505 [backend/drm/drm.c:1594] drmHandleEvent failed
close object 2: Invalid argument
close object 1: Invalid argument
close object 1: Invalid argument
close object 2: Invalid argument
`
right?
so if pixels (well, wgpu, really) can't find an adapter, then that's likely a wgpu problem
is your application something you're porting to linux, or has it run on linux before?
I'm writing this myself, based it off of a pixels example. it runs on my laptop
different architecture and different kernel configuration, they have a separate kernel package for the rpi
other than that yeah
allright
and the github bot is a bit optimistic about issue numbers
I thought you had linked to a commit of yours for a hot second there
but no, it was the bot linking to PR number 1 on winit's repository
thanks, you helped me a lot, I appreciate it
1 reply
I wish you the best of luck in fixing that error
actually, this feels familiar... nannou-org/nannou#732
but it's not the same issue, I tried it out
but it's not the same issue, I tried it out
and OpenGL support in wgpu is still a WIP last I checked
digital : statically/dynamically linkage of libwayland is completely unrelated to wlroots and drm errors fyi
These are two independent problem
you mean the
00:00:01.505 [backend/drm/drm.c:1594] drmHandleEvent failed error?
Yeah, it is related to wlroots/cage, but not to the issue of dlopening libwayland-client.so
will be afk for a bit, getting dinner stuff