M.Sz.
CC @kenn1dy @SleepyPrince
ok, so let me apply that diff to master and close this and #764
- ref: https://github.com/glfw/glfw/issues/1147
I think ebiten uses glfw on linux. I have glfw v3.3 header in /usr/include/GLFW (idk what header ebiten uses)
first v3.3 was released in 2019 and the above issue was fixed in 2017, so I think this is a iplementation bug somewhere here (?)
> Ebitengine dropped Wayland support from GLFW. So what deos it use for linux-wayland now? maybe I can share some more info?
interessting, on examples/fullscreen it panics with ```console [fullscreen (0) ]$ go run . panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x48 pc=0x6d0c86]...
yes, tested on `a4717f7f95ab6cf537ca6a27e7b8b7e3c0d4ab30`, still same result: ```console X Error of failed request: BadRRCrtc (invalid Crtc parameter) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 20...
youp, this one on fullscreen is fixed.
@xEricL its also my first time when I hear about zig. I think you need to care about some type of `PATH` or `INCLUDE_PATH` in zig, however it works. generally,...