Moving to Swift Cross UI and Swift Bundler

[philocalyst]

Currently included are commits moving to SPM and Swift Bundler, and fixes to the warnings I encountered in the process. What is NOT included is the work needed to run the app ENTIRELY off of Swift Bundler, because the mesh-shaders dep doesn't expose their shaders in a way in which Bundler can compile them. We would need to contribute or fork to handle this. That, and the inclusion of libswiftCompatibilitySpan.dylib throws Bundler for ANOTHER loop, and we'd have to move the project in a direction where it would no longer be needed to avoid that.

Locally, I have a build script that patches over both issues, but it's very messy.

Just wanted to let you know.

[llsc12]

i was hoping you’d make a new project rather than migrate the existing one. the existing app uses a lot of appkit and uikit that won’t work with scui!

[philocalyst]

I haven't made a new project yet, so no worries! Just migrated to Swift Bundler. Wanted feedback on that migration before creating the project. Apologies for the miscommunication. ▰▰▰▰▰ Miles Wirth 🙃

…

From: Lakhan Lothiyi ***@***.***> Sent: 15 March 2026 14:43 To: llsc12/Paicord ***@***.***> Cc: Miles Wirht ***@***.***>, Author ***@***.***> Subject: Re: [llsc12/Paicord] Moving to Swift Cross UI and Swift Bundler (PR #39) llsc12 left a comment (llsc12/Paicord#39) i was hoping you’d make a new project rather than migrate the existing one. the existing app uses a lot of appkit and uikit that won’t work with scui! -- Reply to this email directly or view it on GitHub: #39 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[llsc12]

yeah i think that might have been my bad. my apologies! i don’t think migration of the main swiftui application really requires migration to swift bundler if only the scui application needs it. also im struggling to make an scui app to test out scui, not sure why. fails at package resolution :c

[philocalyst]

It's frankly really nice for me to work with as I don't really touch XCode and makes it nice for other contributors as well, pretty easy to maintain alongside the XCode setup if you're comfortable there, too. Can be used for the Linux branch (probably) too! Are you using [this template](https://docs.swiftcrossui.dev/documentation/swiftcrossui/quick-start/#Using-Swift-Bundlers-SwiftCrossUI-template)? ▰▰▰▰▰ Miles Wirth 🙃

…

From: Lakhan Lothiyi ***@***.***> Sent: 15 March 2026 15:22 To: llsc12/Paicord ***@***.***> Cc: Miles Wirht ***@***.***>, Author ***@***.***> Subject: Re: [llsc12/Paicord] Moving to Swift Cross UI and Swift Bundler (PR #39) llsc12 left a comment (llsc12/Paicord#39) yeah i think that might have been my bad. my apologies! i don’t think migration of the main swiftui application really requires migration to swift bundler if only the scui application needs it. also im struggling to make an scui app to test out scui, not sure why. fails at package resolution :c -- Reply to this email directly or view it on GitHub: #39 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[llsc12]

i suppose so, though i'm a bit sad you removed the camera dependency since it looked nice lol.

i did use the template without modifying it to no avail, which is odd. i tried using swift 5.10 which didn't help either.

[stackotter]

Would you happen to have a copy of the specific error you're facing?

[llsc12]

🌱 Finding latest version of swift-bundler
🌱 Running swift-bundler v2.0.7...
info: Starting debug build
Fetching https://github.com/stackotter/swift-cross-ui from cache
Fetched https://github.com/stackotter/swift-cross-ui from cache (4.26s)
Fetching https://github.com/stackotter/swift-windowsappsdk from cache
Fetched https://github.com/stackotter/swift-windowsappsdk from cache (0.44s)
Fetching https://github.com/thebrowsercompany/swift-windowsfoundation from cache
Fetched https://github.com/thebrowsercompany/swift-windowsfoundation from cache (0.47s)
error: package 'swift-windowsfoundation' is required using a revision-based requirement and it depends on local package 'swift-cwinrt', which is not supported
error: Failed to build 'paicordscui': Failed to run '/usr/bin/swift build -c debug --product paicordscui --arch x86_64': The process returned a non-zero exit status (1)'

[stackotter]

Ah yeah, that’s an outdated version of Swift Bundler - kind of. It’s a complicated story, but tldr I’m working on a Swift Bundler release (and have been for quite a while), so there are a ton of new things on main that are not in a tagged release. You should run moreSwift/swift-bundler@main instead for now. You may have to run swift bundler templates update after updating to the main branch of Swift Bundler, but ideally not if my v2 to v3 migration code works as advertised.

In your case the immediate issue is that the SwiftCrossUI version used in the old template broke due to an upstream package (which we have since forked) that made a strange broken commit a while ago and never fixed it. If you manually change the scui version in the Package.swift file to 0.2.1, things should work.

[llsc12]

oh ok, thank you!