This repository contains two approaches to Swift/Java interoperability.
- A Swift library (
JavaKit
) and bindings generator that allows a Swift program to make use of Java libraries by wrapping Java classes in corresponding Swift types, allowing Swift to directly call any wrapped Java API. - The
jextract-swift
tool which is similar to the JDK'sjextract
which allows to extract Java sources which are used to efficiently call into Swift from Java.
🚧 🚧 🚧 This is a very early prototype and everything is subject to change. 🚧 🚧 🚧
Parts of this project are incomplete, not fleshed out, and subject to change without any notice.
The primary purpose of this repository is to create an environment for collaboration and joint exploration of the Swift/Java interoperability story. The project will transition to a more structured approach once key goals have been outlined.
To build and use this project, currently, you will need to download a custom toolchain which includes some improvements in Swift that this project relies on:
Required toolchain download:
- Go to https://www.swift.org/download/
- Find the "latest"
Trunk Development (main)
toolchain for your OS
If these are too old, you can resort to one of these fallback toolchains:
Fallback development toolchain on macOS:
Fallback development toolchain on Linux (Ubuntu 22.04):
URL=$(curl -s "https://ci.swift.org/job/oss-swift-package-ubuntu-22_04/lastSuccessfulBuild/consoleText" | grep 'Toolchain: ' | sed 's/Toolchain: //g')
wget ${URL}
or just use the provided docker image (explained below).
https://www.swift.org/download/
This project consists of different modules which have different Swift and Java runtime requirements.
JavaKit – the Swift macros allowing the invocation of Java libraries from Swift
- JDK 17+, any recent JDK installation should be sufficient, as only general reflection and JNI APIs are used by this integration
- Swift 6.0+, because the library uses modern Swift macros
jextract-swift – the source generator that ingests .swiftinterface files and makes them available to be called from generated Java sources
- Swift 6.x development snapshots, because of dependence on rich swift interface files
- JDK 22+ because of dependence on JEP-454: Foreign Function & Memory API
- We are validating the implementation using the currently supported non-LTE release, which at present means JDK-23.
The extract tool may become able to generate legacy compatible sources, which would not require JEP-454 and would instead rely on existing JNI facilities. Currently though, efforts are focused on the forward-looking implementation using modern foreign function and memory APIs.
This project contains multiple builds, living side by side together.
Depending on which part you are developing, you may want to run just the swift tests:
> swift test
or the Java tests through the Gradle build. The Gradle build may also trigger some Swift compilation because of interlinked dependencies of the two parts of Swift-Java. To run the Java build and tests use the Gradle wrapper script:
> ./gradlew test
Currently it is suggested to use Swift 6.0 and a Java 24+.
Sample apps are located in the Samples/
directory, and they showcase full "roundtrip" usage of the library and/or tools.
To run a simple app showcasing a Swift process calling into a Java library you can run:
cd Samples/JavaKitSampleApp
swift build
java -cp .build/plugins/outputs/javakitsampleapp/JavaKitExample/destination/JavaCompilerPlugin/Java -Djava.library.path=.build/debug com.example.swift.JavaKitSampleMain
To run a simple example app showcasing the jextract (Java calling Swift) approach you can:
./gradlew Samples:SwiftKitSampleApp:run
This will also generate the necessary sources (by invoking jextract, extracting the Sources/ExampleSwiftLibrary
)
and generating Java sources in src/generated/java
.
You can run Swift ordo-one/package-benchmark and OpenJDK JMH benchmarks in this project.
Swift benchmarks are located under Benchmarks/
and JMH benchmarks are currently part of the SwiftKit sample project: Samples/SwiftKitSampleApp/src/jmh
because they depend on generated sources from the sample.
To run Swift benchmarks you can:
cd Benchmarks
swift package benchmark
In order to run JMH benchmarks you can:
cd Samples/SwiftKitSampleApp
gradle jmh
Please read documentation of both performance testing tools and understand that results must be interpreted and not just taken at face value. Benchmarking is tricky and environment sensitive task, so please be careful when constructing and reading benchmarks and their results. If in doubt, please reach out on the forums.
More details about the project and how it can be used are available in USER_GUIDE.md