-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feat] v2: Frameworks aren't being picked up for iOS builds #9962
Comments
@FabianLars I'm yet unfamiliar with the Tauri internals, but if you could point me in the right direction I'm willing to try my hand at a PR :) |
I haven't tried it on the release build, but for the dev build, I think the easiest way to embed the framework now is using |
Thanks, @pewsheen, didn't know that was possible, so I learned something. 😄 Decided to go the PR route and learn something about Tauri's internals. Hopefully someone will pick up the PR soon and help me with some remaining questions. :) |
Describe the bug
I'm using a Rust crate that depends on coreaudio-rs. For this work work on macOS/iOS, I need to link against the CoreAudio framework.
I'm building for iOS (using the v2 beta) and the linker tells me it's missing core audio symbols.
I've tried setting
bundle > iOS > frameworks
to[ "CoreAudio" ]
intauri.conf.json
, but I get an error that the"frameworks"
property is not allowed.I've also tried setting the same on
bundle > macOS > frameworks
, but that doesn't help. Neither do I see--framework CoreAudio
show up in the linker command.Expected behavior
I would expect
bundle > iOS > framework
to be valid and insert the frameworks into the linker commandFull
tauri info
outputThe text was updated successfully, but these errors were encountered: