no. neanderthal is enqueuing the kernels that have already been compiled and outside clojure. if you write your own kernels, it is in the domain of clojurecl, not neanderthal.

basically, you are just calling the functions, but the functions are "remote", working on the gpu, not in jvm.

The latest neanderthal is great, thanks. Though I need to some work (copy dylibs to /usr/local/lib, and can’t figure out why java.library.path does not work). This time, I managed to run clojurecl (though yes, on my mac only version 1.2 is supported). Thanks again.

@chunsj Thanks for reporting that. java.library.path doesn't work, but did you try DYLD_LIBRARY_PATH or LD_LIBRARY_PATH? I believe that setting one of those two (i'm not sure which one) should have the same effect as copying to /usr/local/lib.

http://dragan.rocks/articles/17/Neanderthal-090-released-Clojure-high-performance-computing

@blueberry right, DULD_LIBRARY_PATH works, however, I’d like to try more portable solution 🙂

@blueberry Oh, I mean DYLD_… not DULD...

@chunsj but DYLD_LIBRARY_PATH (OSX), LD_LIBRARY_PATH (Linux), and PATH (Windows) is actually the recommended portable solution. I doubt you can get more portable than that with native libraries 🙂 Even Java has different installation procedures for each of those 😉