multiarch-scala

multiarch-scala

Multi-architecture native library distribution and JVM application packaging for Scala.

What this is

Three SBT AutoPlugins and a core library:

Artifact	Purpose
sbt-multiarch-scala	SBT plugin bundle: NativeProviderPlugin, MultiArchNativeReleasePlugin, MultiArchJvmReleasePlugin
multiarch-core	Shared models, JSON codec, extraction logic, and runtime NativeLibLoader — sbt-independent
sn-provider-curl	Pre-built static curl libraries for 6 desktop platforms with sn-provider.json manifest

What do they do? Let's take a look at some examples.

Quick Start: Using an existing provider

1. Add the plugin

In project/plugins.sbt:

addSbtPlugin("com.kubuszok" % "sbt-multiarch-scala" % "<version>")

// Required dependencies
addSbtPlugin("org.scala-native" % "sbt-scala-native" % "0.5.10")

2. Add a provider dependency and enable the plugin

In build.sbt:

lazy val myApp = (project in file("my-app"))
  .enablePlugins(NativeProviderPlugin)
  .settings(
    scalaVersion := "3.8.3",
    libraryDependencies ++= Seq(
      // STTP on Scala Native requires libcurl, normally you would
      // have to have it installed on your system, or SN would not
      // be able to link the complete binary...
      "com.softwaremill.sttp.client4" %%% "core" % "4.0.19",
      // ...but here we just need to add a dependency and NativeProviderPlugin
      // will extract the necessary native artifact and set up SN flags!
      "com.kubuszok" % "sn-provider-curl" % "<version>"
    )
  )

3. Build

sbt nativeLink

That's it. The plugin automatically discovers sn-provider.json manifests on the classpath, extracts native libraries for your platform, and configures Scala Native's nativeConfig with the correct linker flags.

Quick Start: JVM multi-architecture packaging

lazy val myApp = (project in file("my-app"))
  .enablePlugins(MultiArchJvmReleasePlugin)
  .settings(
    Compile / mainClass := Some("com.example.Main"),
    releaseTargets := Map(
      Platform.LinuxX86_64    -> "https://cdn.azul.com/zulu/bin/zulu25-...-linux_x64.tar.gz",
      Platform.MacosAarch64   -> "https://cdn.azul.com/zulu/bin/zulu25-...-macosx_aarch64.tar.gz",
      Platform.WindowsX86_64  -> "https://cdn.azul.com/zulu/bin/zulu25-...-win_x64.zip",
      // ... all 6 desktop platforms
    )
  )

sbt "releasePlatform linux-x86_64"   # single platform
sbt releaseAll                       # all configured platforms
sbt releasePackage                   # simple mode (system JDK required)

If you used JDKPackager you might wonder what's the fuss?

Well, JDKPackagerPlugin can only build package for the currently used JDK on the current platform. If you need to package for several architectures, you'd have to e.g. use GitHub actions with multiple different runners (one for each platform) to do it for you.

MultiArchJvmReleasePlugin lets you build on your own computer packages for multiple different architectures, and let you select the JDK to use for each of them. That means that you can build all the release artifacts completely offline, on your own computer!

Quick Start: NativeLibLoader (JNI/Panama runtime)

For JVM projects that need to load native shared libraries at runtime:

// Add dependency
libraryDependencies += "com.kubuszok" %% "multiarch-core" % "<version>"

import multiarch.core.{ NativeLibLoader, ProviderType }

// Auto-discover and load all libraries from jni-provider.json on classpath
NativeLibLoader.loadAll(ProviderType.Jni)

// Or load specific configs
NativeLibLoader.loadConfigs(ProviderType.Panama, Set("mylib"))

// Or load a single library by name
val path = NativeLibLoader.load("mylib")

How to create your own provider

Step 1: Cross-compile your native code

Build your native library for each target platform. For Scala Native, you need static archives (.a / .lib). For JNI/Panama, you need shared libraries (.so / .dylib / .dll).

Step 2: Create a manifest file

Choose the right manifest filename for your provider type:

Filename	Provider Type	Use Case
sn-provider.json	Scala Native	Static libraries linked at compile time
jni-provider.json	JNI	Shared libraries loaded at runtime via JNI
pnm-provider.json	Panama	Shared libraries loaded at runtime via Panama FFI