Needed to expose SecureEncalve through SwiftCrypto when building for Swift-Certificates. CRYPTO_IN_SWIFTPM is set all of the time in package.swift, while CRYPTO_IN_SWIFTPM_FORCE_BUILD_API is only set in development. Lets enable the one that's on all of the time, and remove the one that isn't so that we get our declarations.
Since CRYPTO_IN_SWIFTPM is enabled all of the time, would it make sense to not have it? Or what exactly is it used for?
Needed to expose SecureEncalve through SwiftCrypto when building for Swift-Certificates. CRYPTO_IN_SWIFTPM is set all of the time in package.swift, while CRYPTO_IN_SWIFTPM_FORCE_BUILD_API is only set in development. Lets enable the one that's on all of the time, and remove the one that isn't so that we get our declarations.
Since
CRYPTO_IN_SWIFTPM
is enabled all of the time, would it make sense to not have it? Or what exactly is it used for?