Apparently in order for this to work Carthage will need to build .xcframeworks now: https://twitter.com/NeoNacho/status/1135691439734575104.
.xcframework can be made by xcodebuild -create-xcframework which takes -framework and -output options. So that's means that we should run the command instead of lipoing after building per-platform frameworks.
example:
$ xcodebuild archive -workspace Alamofire.xcworkspace -scheme "Alamofire iOS" -sdk iphoneos13.0 OBJROOT=build/iOS
$ xcodebuild archive -workspace Alamofire.xcworkspace -scheme "Alamofire iOS" -sdk iphonesimulator13.0 OBJROOT=build/simulator
$ xcodebuild -create-xcframework -framework build/iOS/UninstalledProducts/iphoneos/Alamofire.framework -framework build/simulator/UninstalledProducts/iphonesimulator/Alamofire.framework -output build/Alamofire.xcframework
Can anyone actually build Carthage on Xcode 11 Swift 5.1?
@blender I just tried, it seems unhappy with the currying in the OptionsProtocol objects evaluation (e.g. in CheckoutCommand.Options.evaluate):

Using Options.init seems to work, though.
Yeah, I was trying to go around this by specifying a lower version of swift in the Makefile but I'm hitting a wall.
Looks like building Carthage itself with Xcode 11 (Swift 5.1) is a separate issue.
I鈥檓 on this btw ;)
https://github.com/Carthage/Carthage/pull/2801 is in progress but can already build xcframeworks with carthage build --platform iOS --no-skip-current --create-xcframework
I'm not sure what we're supposed to do with dSYMs
Can anyone actually build Carthage on Xcode 11 Swift 5.1?
yes I did but no luck,
It seems the framework will be build in swift 4.1.2, that is very strange.
@haithngn I believe this is a problem with your setup. Carthage itself is both building correctly on Xcode 11 Swift 5.1 and so frameworks built by Carthage that support Swift 5.1
@blender , you right :D I have tried on xcode 9.4 then the IDE say "module compiled with Swift 5.1 cannot be imported in Swift 4.1.2" 馃槀
I will try on xcode 11 later
This should mean that we can stop using copy-frameworks then?
@mdiep as far as I can tell yes. But I'm not sure how dsyms will be packaged.
Hey guys, I was just wondering was there a resolution to this problem?
It looks like dSYM files are inside each architecture package. ios.xcarchive/dSYMs Can they simply be copied next to the XCFramework or something? Is there a way to package them inside the xcframework as part of the create-xcframework command?
Hello, any ETA planned for this feature?
CocoaPods recently added support for xcframeworks in 1.9.0, we (PSPDFKit) sponsored part of the development. Would anyone be interested in a similar agreement?
I鈥檇 be happy to implement Catalyst functionality on my employer鈥檚 time but I am worried that Carthage has no forward movement. There are multiple other pull requests that seem to be stuck.
@DavidBrunow which ones? I have merged quite a few recently. Please contact me on twitter about this https://twitter.com/tmpz
I also have contacted @steipete since I have some time on my hands but I can't guarantee it will be enough.
@tmspzz Sorry I was wrong about the pull requests not being merged -- I hadn't noticed that they had been. But we are still waiting on a release for those pull requests so I'm still worried.
I just tried to install a binary xcframework via Carthage. It installed the simulator .framework slice and threw out the arm .framework slice.
is carthage dead? or will a fix come one day?
is carthage dead? or will a fix come one day?
Probably is :D I had to switch to spm because I can't wait anymore
It's most certainly not dead. XCFramework support is actually now on master as of a few weeks ago. https://github.com/Carthage/Carthage/pull/3071
Ah wonderful! Any ETA for a public release?
looks like the changes are released in today's 0.37 release.
O.37.0 includes support for .xcframeworks but not yet for Catalyst
Now that we have XCFrameworks support, is there a way to get the Catalyst slice built?
Most helpful comment
Hey guys, I was just wondering was there a resolution to this problem?