[cl-opengl-devel] cl-opengl in win32, was working now not so much
cl-opengl seemed to be working fine for me on 01/30; see: http://article.gmane.org/gmane.lisp.cl-lispbuilder.general/648 But after downloading the latest version of CFFI I get the following error in CLISP. Anyone know what the problem may be? Thanks, - Luke EVAL: undefined function CFFI::LISP-FUNCTION-NAME [Condition of type SYSTEM::SIMPLE-UNDEFINED-FUNCTION] Restarts: 0: [USE-VALUE] You may input a value to be used instead of (FDEFINITION 'CFFI::LISP-FUNCTION-NAME). 1: [RETRY] Retry 2: [STORE-VALUE] You may input a new value for (FDEFINITION 'CFFI::LISP- FUNCTION-NAME). 3: [RETRY] Retry performing #<ASDF:COMPILE-OP NIL #x19FF2479> on #<ASDF:CL- SOURCE-FILE "funcs" #x19FF1F49>. 4: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL #x19FF2479> on #<ASDF:CL- SOURCE-FILE "funcs" #x19FF1F49> as having been successful. 5: [ABORT-REQUEST] Abort handling SLIME request.
Luke Crook <luke@balooga.com> writes:
But after downloading the latest version of CFFI I get the following error in CLISP. Anyone know what the problem may be? [...] EVAL: undefined function CFFI::LISP-FUNCTION-NAME [Condition of type SYSTEM::SIMPLE-UNDEFINED-FUNCTION]
That function doesn't exist anymore, so that's the problem. BTW, on an unrelated note, I really don't understand very well how the current cl-opengl works in windows at all, since it doesn't specify the stdcall convention. (It doesn't matter for SBCL and Allegro as they handle stdcall automagically but should be an issue for CLISP, Lispworks, etc.) I guess you have three options: 1. Substitute cffi::lisp-function-name for cffi::lisp-name. 2. Use http://common-lisp.net/~loliveira/darcs/cl-opengl-thomas which requires http://common-lisp.net/~loliveira/darcs/cffi-newtypes and should have much better Win32 support. 3. Wait until CFFI and cl-opengl merge all or some of the changes in the above trees. HTH. -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/
participants (2)
-
Luis Oliveira -
Luke Crook