January 2008 - cl-opengl-devel - mailman3.common-lisp.net

[cl-opengl-devel] cl-opengl and clx naming conflict
by David Lichteblau 21 Jan '08

21 Jan '08

Hi, I was hoping to add cl-opengl as a main project to clbuild. Unfortunately cl-opengl and CLX both define a package called GL, so we cannot dump a core file including them. Is there a chance that cl-opengl might switch to a more specific package name? d.

2 2

Re: [cl-opengl-devel] cl-glfw 0.3 with cl-opengl interoperability
by William Robinson 11 Jan '08

11 Jan '08

Luís Oliveira wrote: > In what ways does cl-glfw-opengl differ from cl-opengl? Well, it's more in-line with the cl-sdl style of opengl binding. As, initially I wrote my own OpenGL bindings because I was having difficulties with cl-sdl and lispbuilder on Mac OS X (and was generally averse to GLUT). So the main differences are: * You specify the function's “command suffix”, eg. (gl:color-3f 0 0.5 1) instead of just (gl:color 0 0.5 1), * The GL“enum” constants aren't defined in one large cffi defcenum, but they are just defined as constants, eg. use (gl:clear gl:+color-buffer-bit+) instead of (gl:clear :color-buffer-bit). * All of the OpenGL API and extensions are automatically generated from opengl.org's spec files. Though I have learned (after I wrote the generators) that there is a branch of cl-opengl with more dynamically generated stuff from spec files. * Each registered extension is a separate asd file (this includes the OpenGL and GLU versions, as well) * Instead of focusing on too many individual cases of lispification, I have striven to make (where possible according to the spec files) Lisp sequences transparent as OpenGL functions' array-pointer parameters (though this does require some extra allocation. of course). On the whole, I'd say the main difference is that cl-glfw-opengl is more OpenGLy and cl-opengl is more Lispy in style. Ciao bill, who forgot to CC the list first time.

1 0

[cl-opengl-devel] cl-glfw 0.3 with cl-opengl interoperability
by William Robinson 11 Jan '08

11 Jan '08

Hi. Just a little note to say I've released cl-glfw-0.3 which now is able to work with cl-opengl (as well as with its own bindings, cl-glfw-opengl). So, maybe this option apart from SDL (with its custom application entry-point issues) and GLUT (for when you get stuck in a main loop) will be appealing to some. The only caveat, at the moment, is that libglfw mostly only comes as statically linked libraries by default. We have been petitioning the glfw maintainers for dynamically loaded libraries by default to ease this problem somewhat. Thanks for listening </flamebait> Ciao bill

2 1