Segfault when calling glfwInit() on Wayland

[left geode]

do you get the same thing if you don't link statically?

[burnt bough]

no it works without -static

[left geode]

looks like it's linking the wrong glibc or something like that

[burnt bough]

thats something that can happen? interesting

how would I go about investigating that further?

[left geode]

why are you setting -static manually?

[burnt bough]

how am I supposed to do it then?

[left geode]

you already set BUILD_SHARED_LIBS and GLFW_BUILD_SHARED_LIBS to off

[burnt bough]

maybe I'm misunderstanding but, removing the flag would cause it to not link to libc and other standard libraries statically, thus I would also need to provide those with the application, on Linux that doesn't matter that much, but for a Windows build, that would be a little bit annoying

I want to have a single executable with everything included, no other files alongside it

is statically linking everything not the way to do that, or is it otherwise a bad idea? if so, why?

[left geode]

if you want to static link the runtime then you want -static-libgcc -static-libstdc++

but providing dlls next your you executable is usually nto an issue

[burnt bough]

its not, I just don't want to haha

[austere spire]

@burnt bough has reached level 1. GG!

[burnt bough]

so I only need these and not -static to achieve the same effect?

[left geode]

I think so

[burnt bough]

ah ok, then I'll just do that, thanks