Describe the bug
Running carthage bootstrap --platform iOS --cache-builds downloads the AWS framework binaries as expected, but they are incompatible due to being built with Xcode 10.1 / Swift 4.2.1. I am then forced to build the frameworks locally, which can take over an hour since there is no way to specify specific AWS libraries in the cartfile.
To Reproduce
Steps to reproduce the behavior:
carthage bootstrap --platform iOS --cache-buildsWhich AWS service(s) are affected?
aws-sdk-ios
Expected behavior
The prebuilt binaries should be built with the current version of Xcode (10.2.1)
Environment(please complete the following information):
Same thing
+1
Building in Carthage seriously takes 15-30 minutes. Please update it to Swift 5.0
@cbommas
Experiencing the same issue :/ Are there any plans to improve it?
+1
Building in Carthage seriously takes 15-30 minutes. Please update it to Swift 5.0
@cbommas
Even much more on a Macbook pro 2019 2,4 GHz Intel Core i9.
Do you have any plan to update it ?
@rohandubal @kvasukib @cbommas is there any timeline on this? Swift 5 and Xcode 10.2 have been out for months now. Xcode 11 with Swift 5.1 will be officially released next week which will make your binaries even more out of date. You should either support specifying individual AWS frameworks in Carthage or keep your prebuilt binaries reasonably up to date, but forcing every developer to deal with these build times is ridiculous.
I've had to reluctantly switch to cocoapods because of this. Can't understand why you can target individual packages in Pods but not in Carthage.
+1
Whoops, should have closed this when we released #1935. Carthage will now be built with an ABI-compatible version of Swift, which should solve the original problem of incompatible Swift versions.
Regarding not being able to build individual libraries--I'm not aware that there is a way to specify individual targets in the cartfile--it seems that Carthage wants to build all shared schemes.
Most helpful comment
+1
Building in Carthage seriously takes 15-30 minutes. Please update it to Swift 5.0
@cbommas