UnrealXR/raylib-python-cffi
Archived
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

nonworking dynamic bindings

Browse source
This commit is contained in:
Richard Smith 2019-05-21 17:51:54 +01:00
parent 2335c5275f
commit 790ff3fcf6
8 changed files with 119 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

13
README.md
View file

@ -1,12 +1,14 @@
# Python Bindings for Raylib
These bindings use CFFI rather than ctypes. Hopefully this will be faster, the static type knowledge from the C
This uses CFFI API static bindins rather than ctypes. Hopefully this will be faster, the static type knowledge from the C
headers will result in fewer bugs, and using the original headers will make it easier to maintain.
Currently the goal is make usage as similar to the original C as CFFI will allow. There are a few differences
you can see in the examples. Making a 'Pythonic' library would be an additional layer on top which hasn't been
done yet.
See test.py and examples/*.py for how to use.
# Platforms tested
* MacOS 10.12.6
@ -16,3 +18,12 @@ done yet.
* converting more examples from C to python
* testing and building on more platforms
### Dynamic bindings
I have attempted to do CFFI ABI dynamic bindings too in order to avoid the need to compile a C extension module,
but they don't work properly. They fails to work in the same place the ctypes binding fails, accessing
materials of a model, because Python can't dynamically tell the difference between a pointer and an array. There's probably
some way to specify this (e.g. in raylib_modified.h) but it's difficult to be sure we fixed them all, and the errors
are often completely silent.
See test_static.py for the non-working example.