swiftlang / swiftlang/swift-java
SwiftJavaExtract sample apps fail to build on Windows
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 1.2k
- Forks
- 123
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 16
Description
Commit hash: 4cf5605a03219fc7c99149020b0923c0a73a4f3c
Context:
I was trying to build the SwiftJavaExtractJNISampleApp and SwiftJavaExtractFFMSampleApp samples on Windows x86_64.
Both samples fail during their validation process on Windows.
Steps to reproduce:
- Clone the repository:
git clone https://github.com/swiftlang/swift-java.git - Run the JNI sample validation:
cd swift-java/Samples/SwiftJavaExtractJNISampleApp ./ci-validate.sh - Run the FFM sample validation:
cd ../SwiftJavaExtractFFMSampleApp ./ci-validate.sh - Observe that the validation does not complete successfully on Windows.
Result:
For example, one of the failures I encountered was while invoking the Gradle wrapper. A path such as:
/C:/Users/user/swift-java/gradlew
was passed to the Windows process and could not be executed correctly.
SwiftJavaExtractFFMSampleApp also fails during validation. For example, generated Swift output can end up with an invalid path containing an absolute Windows path as part of the filename:
C:/Users/user/swift-java/Samples/SwiftJavaExtractFFMSampleApp/.build/plugins/outputs/swiftjavaextractffmsampleapp/MySwiftLibrary/destination/JExtractSwiftPlugin/Sources/C:/Users/user/swift-java/Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/MySwiftClass+SwiftJava.swift
resulting in:
Error Domain=NSCocoaErrorDomain Code=512 "(null)"
UserInfo={
NSUnderlyingError=Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument",
NSUserStringVariant=["Folder"],
...
}
Expected result:
The sample validation scripts should complete successfully on Windows x86_64.
$ swift --version
Swift version 6.3.3 (swift-6.3.3-RELEASE)
Target: x86_64-unknown-windows-msvc
Build config: +assertions
Operating system: Windows x86_64
$ uname -a
MINGW64_NT-10.0-26200 DESKTOP-C8619AE 3.6.9-b4195d69.x86_64 2026-06-06 17:49 UTC x86_64 Msys
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running ci-validate.sh in Samples/SwiftJavaExtractJNISampleApp and Samples/SwiftJavaExtractFFMSampleApp on Windows, then inspect how each script invokes the Gradle wrapper and handles generated Swift paths. Done means both sample validation scripts complete successfully on Windows x86_64 without malformed executable or generated-source paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, swift
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100