Java Panama Polyglot (Rust) Part 4

Hello and welcome to the final article of the Java Panama Polyglot series, where we are presenting quick tutorials or recipes on how to access native libraries written in other languages.

In this article you will be using Project Panama to talk to the Rust language.

If you are new to Java’s Foreign Function Access APIs (Project Panama) check out Panama4Newbies.

In Part 3 you had a chance to learn about how to use Java Project Panama’s abilities to access the locally installed Python interpreter.

This capability has the advantage of not only talking to Python but also to any of the installed add-on modules (libraries) such as tensorflow, numpy or pyplot.

As far as native compiled languages go, Rust is the new kid on the block.

Rust is often compared to the Go language where source code can be compiled to a specific operating system.

Unlike C/C++, the source code doesn’t contain compile time directives and #defines that handle special cases for different architectures.

By exposing native Rust functions, you can be easily accessed using Project Panama’s Foreign Function Access APIs.

Today, let’s look at how to access a native library built using the Rust language. This tutorial was derived from Jorn Vernee‘s article “Calling a rust library with the Panama FFI“.

For the impatient the example code is at


As a Java developer, you want to invoke my Rust based library function rust_get_pid() that will return an integer value representing an application’s process id.


Below are the high-level steps to access a native Rust library and function.

Step 1: Create a Rust library with a function exported following the C ABI.

Step 2: Generate a lib.h header file .h (extension) for the jextract tool to generate binding code.

Step 3: Generate Java binding code (classes) using jextract

Step 4: Create a to call the rust_get_pid() generated function


Before we can take the steps above let’s make sure we install the JDK 19 EA release of OpenJDK containing Panama and Rust correctly.

To install Rust run the following for (MacOS/Linux):

curl --proto '=https' --tlsv1.2 -sSf | sh

Assuming you’ve installed Rust you’ll want to add its binaries on the PATH as followings:

source $HOME/.cargo/env

Step 1: Creating a Native Rust Library

Let’s initialize the Rust project with the following commands:

(For the demo I created a directory rust. If you are already in a directory named rust you don’t need to create it.)

mkdir rust
cd rust
cargo init --lib

Edit and replace the contents of the file src/ with the following:

use std::process;

pub extern "C" fn rust_get_pid() -> u32 {
  return process::id();
Line number Description
1 Use Rust’s standard library module process
3 A directive to not mangle (alter) the symbol’s function name
4 To export a Rust function prefix it with pub extern "C". Here, you’ll notice the return type is u32 or an unsigned integer (32 bits).
5 Return the process id to the caller
A Rust library exported adheres to the C ABI

After you’ve edited and saved the file let’s edit the Cargo.toml file by replacing it with the following contents:

Updating build project file Cargo.toml

The following contents of the Cargo.toml file will compile and build a native Rust library created in the target/debug directory.

cbindgen = "0.20.0"

crate_type = ["cdylib"]

name = "myrustlibrary"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at


Above you’ll notice cbindgen is used to generate a C header (.h) file for jextract to later generate binding code in Java. Also, you want to make sure the name of the library will be named myrustlibrary.

On a MacOS system the library created will reside in the following directory: target/debug/libmyrustlibrary.dylib

On a Linux system the library will be named

Step 2: Create a Rust C header generator (generates a lib.h file)

Create a file called with the following contents:

extern crate cbindgen;

use std::env;

fn main() {
    let crate_dir = env::var("CARGO_MANIFEST_DIR").unwrap();

      .expect("Unable to generate bindings")

Run the following statement that will call cbindgen to generate a lib.h file.

cargo build

The output should look like the following:

Executing cargo build

This may take awhile. When this is done you can view the contents of lib.h as shown below:


uint32_t rust_get_pid(void);

Step 3: Use jextract against C header file (lib.h)

Run the following using jextract to generate binding code that will be used in the program created later.

jextract -d classes 
   -t org.rust 
   -l myrustlibrary 
   -- lib.h

Step 4: Creating a to call the native function

Edit or create a file with the following contents:

import static org.rust.lib_h.*;

public class Main {
    public static void main(String[] args) {
        System.out.println("Rust getting process id = " + rust_get_pid());

Above you’ll notice the static import will reference generated Panama binding code. The bindings will do a library lookup and a native symbol lookup of the function rust_get_pid() function based on the C ABI.


To run the Java program you’ll simply do the following:

java --add-modules jdk.incubator.foreign 
   -cp classes

The output will look like the following:

WARNING: Using incubator modules: jdk.incubator.foreign
warning: using incubating module(s): jdk.incubator.foreign
1 warning
Rust getting process id = 36396

If you’ve gotten this far you deserve a high five! Way to go!


You’ve now had a chance to build and create a Rust based native library using cargo.

Another notable tool or module was the cbindgen capable of creating a C header file that will be used with the jextract tool.

Once Panama code is generated the code can simply call the Rust function rust_get_pid() to return the application’s process id.

Adding more native languages to your skillset is really easy as long as you expose (export) native functions that follow the C ABI.

By doing so will allow your code to easily do symbol lookups.

Thank you for exploring Project Panama with me and I hope to share new and exciting use cases in the future.

As always, feel free to comment or provide feedback so I can improve the articles. The idea is to update the articles as the APIs settle and make it into the GA (final) release.

The post Java Panama Polyglot (Rust) Part 4 appeared first on foojay.