-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
FR: Officially support Carthage release #1862
Comments
No problem! |
The Carthage distribution is still experimental and we're not promising to make every minor release available via Carthage. Even if the latest distribution is not available via Carthage, the latest binary frameworks are always available at https://firebase.google.com/docs/ios/setup#frameworks. We're continuing to improve the release process and hope to make Carthage official and in sync with the rest of the release in the future. |
Where is the development process to support carthage |
@techmehra See https://github.com/firebase/firebase-ios-sdk/tree/master/ZipBuilder for the zip and Carthage libraries are build scripts. There is additional internal code for deploying the libraries to Google servers. |
@paulb777 when will "make Carthage official and in sync with the rest of the release in the future" happen? Mid 19 or End 19? As Fabric.io isn't a optiona any longer i have to know how to handle future projects... and pods is not a option as we are using carthage in most of our projects... |
@mmalesevic We've been making progress and are now consistently recently Carthage within a day of the CocoaPods releases. However, we still need better staging and testing infrastructure before we can make Carthage support official. I'm hoping that it can happen in the next few months, but can't make any promises. |
Linking this issue as cross-reference, because it should be taken into consideration when providing official Carthage support: Carthage/Carthage#2777 |
Just moved Firebase from pods to carthage in one project. |
Yes, you can specify the dependency in the Cartfile as follows: |
Closing. Now that Swift Package Manager is the future (see #3136), we no longer plan to officially support Carthage. We will continue Carthage updates and support as experimental until SPM migration is ready. |
Since you don't plan on open sourcing all you frameworks isn't Carthage the best bet for now ? Using SPM with binary isn't even drafted |
We plan to continue existing CocoaPods, zip, and Carthage support. After WWDC 2019, we think that investing in a swiftPM solution is better than further Carthage improvements. |
Nice to know, we will definitely move to SPM when available too. I was just worried you would drop Carthage support right now as we spent quite a lot of time investing in Carthage related tooling. |
I'd really like to see this support comes true yet, because even though SPM is already being adopted for you guys, but it still does not have the support for Binaries Distribution which ultimately reduces compilation time. I'd to invite you to compare the diferences between a medium-sized project based on cocoapods and SPM and one which has prebuilt carthage frameworks, you will notice the difference and I can guarantee that it is not a small one and because that I think Carthage is a big deal yet. Thanks for everything you ever did for us that still use carthage! |
Im new to carthage but like it. Seems a bit cleaner and clearer than what the pod installation. I am having some trouble though with this since I am working on a project that uses older versions of certain firebase libraries (manually copied into the project) and for that reason I can not use this as is. I intend to update and migrate though so I definitely would prefer carthage support. |
As it is obvious this is not really an issue but I really wanted to leave some feedback about your experimental carthage integration as I really hope it ends up being officially supported!
ps: feel free to close this issue :)
pps: sorry if I am abusing the issues guidelines, I hope the end justified the means ;)
The text was updated successfully, but these errors were encountered: