Post

Replies

Boosts

Views

Activity

Reply to Apple on Metal and Moltenvk
MoltenVK simply calls the Metal API in the end, there isn't any issue at all from an App Store review point of view. The main issues are that it adds an overhead over calling Metal directly, and that it might be missing some of the newer features available in Metal, but it's up to you and to what you actually needs are whether it's could work for your app or not.
Topic: Graphics & Games SubTopic: General Tags:
Nov ’22
Reply to Why does @available not work?
@available requires that the symbols in the code block are available in the sdk. If you are using a previous sdk, you have to fall back to the good old C preprocessor and disable the code block. @available is not a way to make it possible to compile code that requires a newer sdk on an older Xcode version.
Topic: Programming Languages SubTopic: Swift Tags:
Nov ’22
Reply to Xcode 14 and supporting macOS 10.9 - 10.12
Xcode ships only one SDK per platform. Xcode 14 still has the old macOS 12 SDK, while the beta had the macOS 13 SDK. This is because, just like last year and the year before, the new macOS version is still in beta, and Apple doesn't ship a beta SDK in a public release. The macOS 12 SDK allows to deploy to 10.9, the 13 SDK that was in the beta and that will be in Xcode 14.1 will allow only to deploy to 10.13 and higher.
Sep ’22
Reply to On building an universal binary on Xcode 12.3, why are the dynamic libraries under Example.app/Contents/Frameworks directory buillt for x86_64 archirecture only and not for arm64?
Swift ABI got stable in 10.14.4, this means that those libraries are now bundled with macOS. Probably you set the deployment target to a version older than 10.14.4, so Xcode bundles the Swift libraries, but only for Intel because the first macOS version for arm was 11, and it already includes those libraries.
Topic: App & System Services SubTopic: Core OS Tags:
Aug ’22