On Dec 6, 12:40 am, Phil Hagelberg <p...@hagelb.org> wrote: > Zach Tellman <ztell...@gmail.com> writes: > > If that's what it takes, great. Someone just needs to define what a > > multi-platform JNI package looks like. I'm willing to go along with > > whatever is decided upon by technomancy et al. > > I don't think this is necessarily within the scope ofleiningen > itself; it should be able to be implemented within a plugin. I'm happy > to provide support for how to write a plugin, but since I'm pretty > ignorant of the challenges of native code I'm not sure my input is all > that helpful. > > -Phil
I looked at the code of the swank plugin and some other I found but it seems like plugins are just new tasks? In order to AOT compile some clojure code that uses native libraries (e.g. penumbra) they need to be on the java.library.path at compile time (because the native libs are loaded in static blocks so simply importing their java classes causes them to be linked in), which means that the compile task needs to know about java.library.path. I've made a rather ham-fisted attempt at adding this functionality to leiningen. The result can be viewed here: http://github.com/bagucode/leiningen However, when trying to build penumbra with it, it still fails with an UnsatisfiedLinkError. It seems like setting the java.library.path property in the ant task in eval-in-project is ignored..? /Mac -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
