Skip to content

wayland feature assumes one is using glfw-sys #577

@EriKWDev

Description

@EriKWDev

Hi!

I'm using debian with libglfw3-wayland installed, meaning my glfw uses wayland.

When I use this crate with default-features=false since I don't want the glfw-sys crate to compile and then try to enable the feature "wayland" in order for raw_window_handle to return the correct handle, suddenly glfw-sys is included again.

This leads to a linking error for me at least when the raw-window-handle feature is also enabled since it branches depending on wether the wayland feature was enabled:

ld.lld: error: undefined symbol: glfwGetX11Window

and since my glfw version doesn't seem to have x11 this happens :/

I propose that wayland should not enable glfw-sys by default, and only if glfw-sys is also enabled, or for those things to be separated

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions