Closed adamlwgriffiths closed 3 years ago
The current git release has a hard-coded filename for the raylib shared object.
This has 2 issues:
x-2.0.0
x-2
x
This makes it very difficult for the RAYLIB_BIN_PATH environment variable to function on systems that don't have Raylib 2.0.0.
RAYLIB_BIN_PATH
raylib-python-cffi has implemented this logic which should work here.
raylib-python-cffi
Ok, I can see that the raylibpy-3.7 branch has updated the filenames to match the released binaries names, which fixes this issue. But it breaks non-windows library loading.
raylibpy-3.7
The current git release has a hard-coded filename for the raylib shared object.
This has 2 issues:
x-2.0.0
,x-2
,x
).This makes it very difficult for the
RAYLIB_BIN_PATH
environment variable to function on systems that don't have Raylib 2.0.0.raylib-python-cffi
has implemented this logic which should work here.