Interface and bindings to the Allegro 5 game programming library
I hope for it to be as clean and neat as cl-opengl.
- You need both the libffi and allegro5 libraries
- Requires the CFFI version on/after November 5, 2014
(al:rest-time secs)because of symbol interference with #'cl:rest.
- Enums/constants are shortened, check constants.lisp if you need help finding them.
- Type names have changed too, check types.lisp if you need help finding them.
- Also check type-accessors.lisp on how to get to the slot values.
- I've got a neat lispy interface here
- Everything else is pretty much 1-to-1
Feel free to raise an issue to request a feature or for me to work on something
- Look over lisp interface design again. Might have to ditch the generic methods because of 2. & 3.
- Go over unwind-protect to ensure things safely get deleted.
- Get the restart-cases working so users can recover from screwing up. (Also check out handler-case?)
- Think about whether to use (al:uninstall-system) to cleanup or not.
Everything is pretty much added.
I won't work on the following sections because Common Lisp has more suitable implementations. (Might eventually do it for completeness though) Feel free to explain otherwise and I'll listen.
- How do I
(ql:quickload "cl-liballegro")from any location?
- Either add the path to your asdf by putting this line to your ~/.sbclrc file (remember to change '\' -> '/'):
(push #p"/path/to/cl-liballegro/" asdf:*central-registry*)
- Or copy cl-liballegro to /path/to/quicklisp/local-projects/cl-liballegro
Why can't my program find the DLL in Windows?
There are path problems in Windows because the DLL files (which contain all the functions the CFFI calls upon) doesn't have a default location unlike in Unix environments. When the library loads in Windows, it will look for the DLL in the current folder of the FILE.LISP that evaluates
(ql:quickload "cl-liballegro")This means you must have a copy of the DLL file in the directory of FILE.LISP, not in the cl-liballegro directory unless the FILE.LISP is in there. SLIME however, likes to change the default search folder to the one Emacs is in when it starts.
SBCL Only -
Open command prompt in the folder that contains both the DLL and game.lisp
> sbcl > (load "game.lisp") ; File contains (ql:quickload "cl-liballegro")
Emacs + SLIME
C-x C-f /path/to/Desktop/file9.lisp M-x slime C-x C-f /path/to/Desktop/game/game.lisp ; File contains (ql:quickload "cl-liballegro") C-c C-l ; Looks for the DLL at /path/to/Desktop/allegro.dll
C-x C-f /path/to/Desktop/file9.lisp C-x C-f /path/to/Desktop/game/game.lisp ; File contains (ql:quickload "cl-liballegro") M-x slime C-c C-l ; Looks for the DLL at /path/to/Desktop/game/allegro.dll
M-x slime C-x C-f /path/to/Desktop/game/game.lisp ; File contains (ql:quickload "cl-liballegro") C-c C-l ; Looks for the DLL at /whatever/default/emacs/directory/allegro.dll