-
-
Notifications
You must be signed in to change notification settings - Fork 874
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 #8
Comments
Hey @MarvinNazari, |
💯 👍 |
So I just tried this and it seems to be working... What else is needed to be done? |
works for me as well |
I wrote this in my Cartfile and it didn't work...
The error message was: https://gist.github.com/bojanstef/2544b0f7b5273121ca42 Any suggestions? |
Doesn't work for me. I'm getting the following when doing a
|
👍 Looks like Bolts framework is a fake static framework. Carthage only works with dynamic frameworks. |
While the main branch is not yet fully compatible with Carthage or iOS9 Bitcode, you can use my branch for Carthage github "dgrekov/Parse-SDK-iOS-OSX" |
That's great! Would love to see a PR for this! |
Yes, the changes that I have made center mainly around project configuration and making a bitcode compatible Bolts build. Let me look to see how I can make it a clean pull request and make it happen. For reference, bolts is at: github "dgrekov/Bolts-iOS" |
@dgrekov I added following lines in github "dgrekov/Bolts-iOS" "358dd4ee49b9befb76c3005327ea417c4197bfa8"
github "dgrekov/Parse-SDK-iOS-OSX" "b532ee86b83bf865ad9386aead3e4aeba06e3ee0” … and still get:
How am I supposed to try this instead? Thanks. |
@dgrekov @nlutsenko where did things land with this pull request #281 I'm trying to get my cartfile to work with
Dimitry's fork only goes up to 1.8.1.7. Does this mean that there is currently no Swift 2.0, Xcode 7, Carthage compatible version of the Parse iOS SDK? |
@danstepanov There is no Carthage compatible version for iOS indeed. |
Though we are fully compatible with Swift 2.0/2.1, Xcode 7 and friends... |
Currently, there is no way to build the framework using Carthage. I am exploring the use of the framework zip file and will update the thread as I know more. |
I'm working on it as we speak, with a clean rake build script that would build both Bolts and Parse as dylibs and compatible with Carthage |
So at present, if I want to use the parse framework in a project actively using carthage, do I just need to manually import it? Can carthage work with cocoapods and those xcworkspaces? |
Any updates on Carthage support? |
You Can get it from here, https://github.com/flovilmart/ParseKit the supported versions are detailed in the readme. PR are welcome for updating to the latest versions of submodules. This repo essentially builds all the dependencies, including FBSDK, as proper modules through custom configurations at build time. |
Official update: it's coming very soon, targeting next or one after release (before end of year or in first week of new year). |
Add the following to your Cartfile: P.S. I would recommend waiting until the release of |
Thanks @nlutsenko. I'm actually just starting a brand new project -- first from scratch-scratch in a while. I didn't want to use Cocoa Pods, but am totally new to looking at Carthage. My timeline is such that I'm certain 1.12.0 will be released way before my project is. :) |
I think some basic setup instructions in README would be nice to have for Carthage at this point. What do you think? |
^ 👍 |
Agreed, will update the README with release of 1.12.0, since we didn't release the new version yet. |
@nlutsenko @flovilmart: I'm transitioning over from @flovilmart branch to this master repo, any idea on how to integrate everything else @flovilmart was offering through Carthage?
Any ideas? Hoping that over time ParsePlatform will modularize all of the repos (relevant https://github.com/ParsePlatform/ParseFacebookUtils-iOS/issues/21 & https://github.com/ParsePlatform/ParseTwitterUtils-iOS/issues/18), and then maybe, a while later, the FBSDK can come around too |
ParseTwitterUtils - on it. |
@AndrewSB you could still use the other kits without Parse, now that Parse is offering the Carthage support, I can remove it from the repo to only build the FB dependencies, including ParseFacebookUtilsV4.framework, also passing a custom XC_CONFIG_FILE to carthage, that may be possible to force building the FBSDK's as dynamic module. I'll investigate that option |
@nlutsenko awesome! what do you think are the odds that Facebook will decide to support Carthage? Slim to none? @flovilmart that would be awesome. Thank you for maintaining that 😄 |
@AndrewSB, as I work at FB 😁, let me try to get it done, so there is a good chance it will happen, though I don't have a timeline for it. |
Wasn't sure how much pull you had there 😛 That would be super cool, keep us updated! |
Thank you young based @nlutsenko |
When I build Parse with Carthage I only get an OSX framework and no iOS one. Am I doing something wrong? |
@Bogidon, use the |
@nlutsenko How can I tell Carthage to use the |
@Bogidon Nope, it should use the latest tag avaiable.
|
@nlutsenko sorry for the trouble but now I'm getting this error: I'm up-to-date with Carthage, Xcode and OS X. |
I deleted my |
I have update latest Parse version 1.12.0, but it freeze UI while using Live and Local query. can you please help me. |
@kirank-canwill Unrelated to Carthage. Can you file another issue for this problem? We'll also need more details to provide any assistance. |
Would be awesome to have Carthage support.
The text was updated successfully, but these errors were encountered: