Calling Native C-code from Clojure

221 views
Skip to first unread message

John Doe

unread,
Dec 4, 2020, 9:53:31 AM12/4/20
to Clojure
Hello Everyone,

Motivation: I want to invoke C-code functions from Clojure: writing Java functions in Clojure.

Plan of Attack: Rather than go with the JNI approach I want to interface with C-Library via JNR-FFI (https://github.com/jnr/jnr-ffi)

Based on some example of using JNR-FFI


The wrapper in Java might look like
```
package blahblah;

public class BlahNative {
private static int[] intDummy;
private static double[] doubleDummy;

public BlahNative() {
}

public static native void native_a(char var0, char var1, int var2, int var3, int var4, double[] var7, int var8, int var9);

static {
lib = LibraryLoader
            .create(LibSodium.class)
            .search("/usr/local/lib")
            .search("/opt/local/lib")
            .search("/usr/lib")
            .search("/lib")
            .load(LIBRARY_NAME);
        initializeLibrary(lib);
    }
}
```

Question: For my package
```
(defproject mypkg
:dependencies [[org.clojure/clojure "1.10.1"]
   [com.github.jnr/jnr-ffi "2.2.0"]])
```
How do I write the wrapper for the native functions in
```
(ns mypkg.native
(:import [jnr.ffi LibraryLoader])
(:import [jnr.ffi.annotations IgnoreError])
(:import [jnr.ffi.provider FFIProvider]))
```
For the Java interop I am assuming the above namespace should be based on gen-class (http://clojure-doc.org/articles/language/interop.html).

What is not clear to me is:
1. How does one create the `native` method (since most (defn foo) are static methods)?
2. How do I access the native functions after loading the Native Library (LibraryLoader.load(LIBRARY_NAME))?

I am neither a C nor a Java expert so any guidance will be much appreciated.

Thanks,
Ngwua

Laurens Van Houtven

unread,
Dec 4, 2020, 10:37:47 AM12/4/20
to clo...@googlegroups.com
Hi,

I did a talk on this and conveniently my library caesium wraps the library you're referencing :)


I still think that approach is great particularly for libraries like libsodium where some care was taken to make them easy to FFI. That is typically less true for more complex, often C++, libraries. In that case I would consider JavaCPP, where you basically do more up front work to tell it how it works and it generates JNI for you (up front, not dynamically like jnr). Which one I'd recommend depends on what you're binding. Like I said, for libsodium I think jnr is probably easier to use.

lvh

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@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+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/3bd05d7a-297e-49cf-86d4-aec4a88c83cbn%40googlegroups.com.

Chris Nuernberger

unread,
Dec 4, 2020, 10:52:25 AM12/4/20
to clo...@googlegroups.com

Ngwua,

Looking through the caesium bindings just mentioned, it appears the author dynamically creates an interface and then you can simply ask the native library to instantiate a concrete implementation of that interface.  So you do not always have to create a class with 'native' methods.

Integrating with C libraries is part of the reason I wrote dtype-next which has the ability to efficiently write/read from either java heap or native heap storage.  dtype-next has no dependency on either JNA or JNR.

Hope this helps,

Chris


--

John Doe

unread,
Dec 5, 2020, 10:06:04 AM12/5/20
to Clojure
Thanks so much lvh.

Your Youtube presentation was one of the main reasons I chose JNI-FFI :-)

I did not consider looking into Caesium, let alone the source code: probably, because my current work does not involve cryptography. Thank you so much for the github link to the repo. Looking at the source code I found it very useful. It gave me all sorts of ideas to move forward :-)

John Doe

unread,
Dec 5, 2020, 10:06:30 AM12/5/20
to Clojure
Thank you Chris. It's very helpful.

The approach you took for dtype-next is very interesting. This library is closer to my work (numerical computation). Also, the efficient use of Java heap is very interesting although I admit I don't know enough about it. This reminds me of Rich Hickey's emphasis of understanding data structures.

Chris Nuernberger

unread,
Dec 5, 2020, 10:09:39 AM12/5/20
to clo...@googlegroups.com
You are most welcome :-).  For numerical computation, libjulia-clj may interest you :-).

John Doe

unread,
Dec 5, 2020, 12:25:23 PM12/5/20
to Clojure

Cool! Thanks again Chris.
Reply all
Reply to author
Forward
0 new messages