-
Notifications
You must be signed in to change notification settings - Fork 767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Carthage support #42
Comments
+1 |
@alexpersian thanks for your compliments and for using the project! @AndrewSB gave Carthage support a shot in PR #46. I think he came to the correct conclusion that since R.swift is not a Dynamic Framework, but a extra buildstep you add to a project we can't add Carthage support. Carthage in the end is "just" an amazing dynamic framework builder where you still have to do the integration yourself. The only thing we "abuse" Cocoapods for is the integration part, since that is exactly the main thing Carthage is not doing (on purpose) this is a no go. If I'm seeing this wrong, please let me know! |
Thanks for the response and explanation. The main advantage I personally see with Carthage over CocoaPods is you are not forced into using a workspace with that additional overhead. But I can see your point, especially since this isn't a Dynamic Framework. Also props to @AndrewSB for building a PR to try and make it possible. |
Carthage is a awesome tool, totally agree on that! It's just that it's not so suited for R.swift, would absolutely recommend it for including frameworks. :) |
Update per R.swift version 1.0: The generated code references the Rswift library, which is available through Carthage: https://github.com/mac-cain13/R.swift.Library#carthage |
Great news! |
Do you have any plans as of yet to implement Carthage support for this repo?
Fantastic project by the way!
The text was updated successfully, but these errors were encountered: