raylib5.c3l failing to link with glfw3

[Book-reader]

on arch, fedora, and debian linux, glfw3 is linked with using -lglfw instead of -lglfw3.
this causes raylib5.c3l and raylib.c3l to fail to build with the message /usr/bin/ld: cannot find -lglfw3: No such file or directory.
it can be fixed by replacing "linked-libraries" : [ "glfw3" ] with "linked-libraries" : [ "glfw" ]

[lerno]

Ok, from what I see on the Raylib site, glfw3 is the correct one. Unless glfw works on ALL Linux distros, some other solution must be found.

[Book-reader]

after more testing,
method: install gcc and glfw3 (libglfw3-dev, glfw-devel, etc) in a distrobox container, then run a raylib hello world that uses the library, but use either glfw or glfw3 in the manifest.json of raylib5.c3l
work means the program ran
fail means the compilation failed with the error /usr/bin/ld: cannot find -lglfw3: No such file or directory

Distro	glfw	glfw3
Arch	work	fail
Fedora 40	work	fail
Debian 12	work	fail
Ubuntu 24.04	work	fail
OpenSUSE Tumbleweed	work	fail

also glfw.c3l uses "linked-libraries" : [ "glfw" ]

running pkg-config --libs glfw3 also returns -lglfw

[Book-reader]

To clarify my incoherent ramblings, I belive that -lglfw is the correct way to link with glfw3, when installed using a system package manager as can be seen in the raylib makefile:

# Check the version name. If GLFW3 was built manually, it may have produced
# a static library known as libglfw3.a. In that case, the name should be -lglfw3
LDLIBS = -lglfw

[Book-reader]

And because, as far as I am aware, on linux "linked-libraries": ["glfw3"] is directly converted to -lglfw3, which does not work when glfw3 is installed using the system package manager. Instead "linked-libraries": ["glfw"] would be needed