Tommaso Piazza

> @blender we are filtering by only frameworks that are located at the `Carthage/Build//`. However, user can specify input file with any arbitrary location which is not subject for filtering....

> By recursive inspection we will find both target's and umbrella's dependencies and gonna copy then to the main target's frameworks directory. It mean that in the final Sample.app frameworks...

Also, this case with Umbrella frameworks is __only relevant for macOS__

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...

Can anyone actually build Carthage on Xcode 11 Swift 5.1?

Yeah, I was trying to go around this by specifying a lower version of swift in the Makefile but I'm hitting a wall.

I’m 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

@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...

@mdiep as far as I can tell yes. But I'm not sure how dsyms will be packaged.