-
Notifications
You must be signed in to change notification settings - Fork 122
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
Catalyst Build Issue - MacOS 11.6.4 #714
Comments
Heres the full log if desired click here to expand➜ cargo +nightly build -Z build-std --release --lib --target x86_64-apple-ios-macabi Compiling skia-bindings v0.55.0 error: failed to run custom build command for `skia-bindings v0.55.0` |
Update, the output changed, this is what I'm not getting Click here to show full log➜ cargo +nightly build -Z build-std --release --lib --target aarch64-apple-ios-macabi Compiling skia-bindings v0.55.0 error: failed to run custom build command for `skia-bindings v0.55.0` In Summary
It appears to be looking for Anyway if I find a solutions I'll post it here. |
For Catalyst, I think:
|
Never mind, I'm being stupid (I was trying to mirror the IOS build stuff), finally got rust Skia to compile with |
TLDR
I'm having issues with Catalyst and I suspect it's trying to build with IOS 15 SDK and I'm on MacOS
11.6.4
(and therefore doesn't support it). If my hunch is correct, is there a way I can buildskia-bindings
for the IOS 14 (Catalyst) SDK specially?Overview
I've played with this before and (even wrote some misc notes on building with IOS over here, which I'm super glad I documented) and I'm pretty sure I was able to build this lib with Catalyst...
Anyway, now I'm having issues and my suspicion is that its trying to build for IOS 15 which my system doesn't support since my laptop is old (specially, I'm on
11.6.4
).Environment - MacOS
11.6.4
Output
The full output is somewhat long. Heres the summary
Conclusion
If my hunch is correct, is there a way I can build
skia-bindings
for the IOS 14 (Catalyst) SDK specially?Thanks!
The text was updated successfully, but these errors were encountered: