carthage

问题 I am getting this error while building the SwiftJSON framework to the Some Xcode project through Carthage Dependency Manager. Sivaramaiahs-Mac-mini:GZipDemoApp vsoftMacmini5$ carthage update --platform iOS *** Fetching GzipSwift *** Fetching SwiftyJSON *** Checking out GzipSwift at "3.1.1" *** Downloading SwiftyJSON.framework binary at "3.1.3" *** xcodebuild output can be found in /var/folders/7m/y0r2mdhn0f16zz1nlt34ypzr0000gn/T/carthage-xcodebuild.apLXCc.log A shell task (/usr/bin/xcrun

问题 I had a project with both Carthage and Cocoapods. They both have one common dependency (PureLayout, to be precise). Strange, but project compiles fine without any errors about class redeclaration, etc. So the question is: why it works and which version of dependency is actually used when I call PureLayout's methods – Carthage's or Cocoapods' one? 回答1: Carthage and CocoaPods are very different in terms of building the dependencies and integrating them in the project. CocoaPods is centralized

问题 Is it possible to install GoogleMap SDK via Carthage? I only saw the tutorial for Cocoapods only. Or I only can install manually if I am using Carthage? 回答1: According to Carthage docs: The only supported origins right now are GitHub repositories (both GitHub.com and GitHub Enterprise) Carthage actually builds binary framework from the sources it checkouts from the specified repository. Developer needs to link this built binary frameworks to the project afterwards. Google already provides you

问题 I have been researching a while and with no success on how I can build a cocoa touch framework, add dependency manger for 3rd party libraries and finally add the framework in an app project. First, I would like to say that the framework I am planning to work with will be developed and tested while I write the app, it will be a git submodule of the main git project and. Ideally, The structure of my the whole project looks like that Finder: Project Is that a good way to work? Secondly, the main

问题 I'm trying to port an objc app which uses Facebook's KVOController, to Swift. I've been encouraged to look at RC3 as an alternate and more Swiftish approach. I've read some blogs and I'm encouraged to give this a try. But much of the docs and blogs seem to concentrate on sockets and timers as examples. So I have two simple questions right now: 1) Given an objc fragment like: [self.KVOController observe: self.site keyPath: @"programs" options: NSKeyValueObservingOptionInitial block:^(id

问题 I am trying to update Alamofire to version 4.0. When I run carthage update I get many errors when building Alamofire scheme. It looks like files weren't updated to Swift 3.0 syntax. What I am doing wrong? Log from terminal: *** Checking out Alamofire at "4.0.0" *** xcodebuild output can be found in /var/folders/ls/6t_b5mqx5s187hq2dtts6ys00000gn/T/carthage-xcodebuild.ORghi2.log *** Building scheme "Alamofire watchOS" in Alamofire.xcworkspace /Users/liborzapletal/Documents/Aplikace/PNG/PNG

问题 What are the list of Carthage related files which are good if pushed to git. I know, - Cartfile - Cartfile.private - Cartfile.resolved What about the Build and Checkout folders? 回答1: From this link: Whether you commit the Build and Checkouts directories to your version control repository is entirely up to you. It’s not required, but doing so means that anybody who clones your repository will always have the binaries and / or source for each dependency available. This can be a useful insurance

问题 I'm having problems trying to realize the following dependency setup between two frameworks and an app, all developed by me: Util containts a bunch of low-level utilities and extensions to Foundation types such as String , Date , etc. UI contains a bunch of custom UIView and UIViewController subclasses, class extensions for UIColor , UIImage , etc.. The app and each framework has its own repository on GitHub. The UI framework is set up to depend on the Util framework, using Carthage: The

问题 Scenario My project (codebase shared for iOS/watchOS/tvOS ) has build settings with ENABLE_BITCODE = YES and takes advantage of fundamental libraries which are not yet supporting bitcode, although quoting Apple documentation in App Thinning Bitcode is the default, but optional. For watchOS and tvOS apps, bitcode is required. If you provide bitcode, all apps and frameworks in the app bundle (all targets in the project) need to include bitcode I am currently integrating those fundamental

问题 My project has linked with like 30 different libraries. Very few of them support Carthage. Do I need to make a branch and make them support Carthage one by one? Is there any better way to do so? 回答1: The carthage idea is based on frameworks. So if your dependencies do not support them, carthage is unable to build them for you. Simple as that. But: You can use carthage also to manage dependencies only by using the param "--no-build". Then carthage will only fetch the dependencies into your