[Openmcl-devel] Threads and lispbuilder-sdl and cocoa

[R. Matthew Emerson]

On Apr 24, 2010, at 8:34 PM, Elliott Slaughter wrote:

> Lispbuilder has some known problems running on CCL OS X. Recently a user pointed out that the failures seen in CCL can be duplicated in SBCL by starting lispbuilder in a new thread. Our guess is that cocoa doesn't like being called from any thread other than the initial thread. (Lispbuilder uses a portable wrapper around cocoa.) I'm wondering if there is any way to arrange to have our cocoa code run in the initial thread (preferably without having to rewrite the existing wrapper)?


In addition to what Gary mentioned, you could look at ccl:examples;opengl-ffi.lisp too.  That uses some ccl internals to make the initial thread run the GLUT event loop.