Download-and-point SDK bundles: the Flutter→Swift framework plus the engine binaries it links against, in one tree. No engine checkout needed.
New in this release: Windows. Apps are hosted by the engine's own Win32 embedder (flutter_windows.dll) driven in Swift mode, so windowing, input, IME and accessibility come from the same code path real Flutter Windows apps use — the counterpart of the GTK host on Linux. The framework itself needed almost nothing to get there.
Install — Linux x86_64
curl -LO https://github.com/starling-build/starling/releases/download/sdk-v0.2.0/starling-sdk-linux-x86_64.tar.gz
sudo tar -xzf starling-sdk-linux-x86_64.tar.gz -C /opt/Install — Windows x86_64
curl.exe -LO https://github.com/starling-build/starling/releases/download/sdk-v0.2.0/starling-sdk-windows-x86_64.zip
Expand-Archive starling-sdk-windows-x86_64.zip -DestinationPath C:\Then depend on it by path — see the getting-started guide at https://starling.build/start.html, which now covers both platforms.
Contents. Framework sources, Examples/, and the engine built at release config for each platform:
engine/lib/ |
engine/share/ |
|
|---|---|---|
| Linux | libflutter_engine.so, libflutter_linux_drm.so, libflutter_linux_gtk.so |
icudtl.dat, flutter_assets |
| Windows | flutter_engine.dll, flutter_windows.dll, each with its .lib import library |
icudtl.dat, flutter_assets |
Two things to know.
Your manifest imports FlutterGTK on Linux and FlutterWin32 on Windows; everything else is identical, except that the Ubuntu 26.04 -Xcc math .unsafeFlags are Linux-only and must not be copied into a Windows manifest.
Neither bundle carries the Swift runtime — that belongs to your toolchain, exactly as libswiftCore does on Linux. On Windows its absence is 0xC0000135 before main(), with no diagnostic at all, so copy the runtime DLLs beside your .exe when you ship.
Both bundles were verified from these artifacts rather than from the tree: unpack on a clean machine, depend on it by path, build with FLUTTER_SWIFT_ENGINE_OUT/FLUTTER_ENGINE_OUT unset, run the app and click it. Linux was checked in a live GNOME session; Windows 11 under an account with no Swift toolchain installed.
Verify your download against SHA256SUMS.