PubNub.xcframework

[pawelini1]

This message is not to report any issue actually, but to ask how you guys create PubNub.xcframework you serve with all releases as a Release asset. I tried to do the similar but eventually I ended up just renaming the "PubNub" target into e.g. "PubNubKit" to avoid that naming clash as in this target you have also the type called "PubNub". I checked your xcframework and noticed

// swift-interface-format-version: 1.0
// swift-compiler-version: Apple Swift version 5.10 (swiftlang-5.10.0.13 clang-1500.3.9.4)
// swift-module-flags: -target arm64-apple-ios12.0 -enable-objc-interop -enable-library-evolution -swift-version 5 -enforce-exclusivity=checked -O -enable-bare-slash-regex -module-name PubNub -module-alias Module___PubNub=PubNub -module-alias Module____StringProcessing=_StringProcessing -module-alias Module____SwiftConcurrencyShims=_SwiftConcurrencyShims -module-alias Module____Concurrency=_Concurrency -module-alias Module___Foundation=Foundation -module-alias Module___CommonCrypto=CommonCrypto -module-alias Module___UniformTypeIdentifiers=UniformTypeIdentifiers -module-alias Module___MobileCoreServices=MobileCoreServices -module-alias Module___CoreServices=CoreServices
import Module___CommonCrypto
import Module___CoreServices
import Module___Foundation
import Module___MobileCoreServices
import Swift
import Module___UniformTypeIdentifiers
import Module____Concurrency
import Module____StringProcessing
import Module____SwiftConcurrencyShims
public protocol PubNubLocalFile : Module___PubNub.PubNubFile {
  var fileURL: Module___Foundation.URL { get set }
  init(from other: any Module___PubNub.PubNubLocalFile) throws
  init(from other: any Module___PubNub.PubNubFile, withFile url: Module___Foundation.URL) throws
}

it seems you fixed that issue by using "Module___PubNub" as a module name together with -module-alias Module___PubNub=PubNub. Can you share how you guys configured Xcode/SwiftC/Whatever else to get the result?

[jguz-pubnub]

Hi @pawelini1. Since Apple recommended renaming in the long run in cases where a public type shared the same name as a module, we applied this change starting with version 8.0.0. However, we found a way that served us well until we released the major version mentioned above. It's specifying "-alias-module-names-in-module-interface" as OTHER_SWIFT_FLAGS when building our frameworks first (before packing them into .xcframework):

OTHER_SWIFT_FLAGS="-alias-module-names-in-module-interface"