carthage update fails

[declarativehub]

carthage update fails

[toshi0383]

Using --platform iOS

$ carthage update --platform ios
*** Cloning ReactiveFoundation
*** Cloning ReactiveUIKit
*** Cloning ReactiveKit
*** Checking out ReactiveFoundation at "v1.0.4"
*** Checking out ReactiveUIKit at "v1.0.6"
*** Checking out ReactiveKit at "v1.0.8"
*** xcodebuild output can be found in /var/folders/tr/3lftss053tqdh731cgt0w1p00000gn/T/carthage-xcodebuild.bOvVcK.log
Failed to discover shared schemes in project ReactiveKit.xcworkspace—either the project does not have any shared schemes, or xcodebuild never returned

[srdanrasic]

@toshi0383, do you have latest version of Carthage?

[toshi0383]

Yes, should be the latest.

$ carthage version
0.10.0

[srdanrasic]

Oh I love Carthage. Looks like Cartfiles for dependencies were causing problems. I've removed them so I hope it will work now. Please try.

[ivanmoskalev]

Let's use CocoaPods primarily?
On Sun, 29 Nov 2015 at 18:06, Srđan Rašić [email protected] wrote:

Oh I love Carthage. Looks like Cartfiles for dependencies were causing
problems. I've removed them so I hope it will work now. Please try.

—
Reply to this email directly or view it on GitHub
#13 (comment)
.

[Danappelxx]

@ivanmoskalev A lot of people use Carthage over cocoa pods so I don't think it's worth only using cocoa pods.

[ivanmoskalev]

@Danappelxx I think there is no trouble making the framework Carthage-supported even if we use another dependency manager as main :)

[Danappelxx]

I think the reason Carthage is being used in reactive kit is due to it being more stable and less involved. I personally think we should stick with it (at least, primarily).

[toshi0383]

** BUILD SUCCEEDED **

Thanks !

[srdanrasic]

@ivanmoskalev, I guess by "main" you mean dependency manager for "sub-frameworks" like ReactiveFoundation dependency on ReactiveKit? I've switched all that to git submodules :) Carthage honours git submodules and CocoaPods manages dependencies well so I think we should be good to go.