Skip to content
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 #61

Open
mingsai opened this issue Apr 17, 2016 · 4 comments
Open

Carthage Support #61

mingsai opened this issue Apr 17, 2016 · 4 comments

Comments

@mingsai
Copy link

mingsai commented Apr 17, 2016

Hi,

I really want to use this component. I just don't like using Cccoapods. Can this be used via Carthage (preferred)? Or (in the future) SPM when Swift 3.0 is released?

@evermeer
Copy link
Owner

At the moment there is no support for Carthage and SPM. I don't think it's very difficult to add support for this, but I don't have any experience with it. The only thing you would need is the 6 files from the AppMessage/CloudKit folder plus the pod folder from the EVReflection library (dependency). You could also copy them manually into your project. I will add Carthage and SPM support to my todo list. Any help is welcome.

@mingsai
Copy link
Author

mingsai commented Apr 18, 2016

Hi,

Medium has a short article on how to add a Carthage Framework with some files from your existing project. The SPM seems a bit tougher as it only works with Swift source files but I did find the instructions for developing an SPM. I can try to walk through the instructions on Medium along with one or two steps they've not fully covered. I found these on the main Carthage page:

Declare the frameworks compatibility by adding the following to the README.md:
Carthage compatible

git tag version

Make scheme shared ( Product > Scheme > Edit Scheme )

I can walkthrough the Carthage packaging steps on both libraries and see how it goes.

@evermeer
Copy link
Owner

evermeer commented Sep 8, 2017

Carthage support is added in evermeer/EVReflection#225

@jstheoriginal
Copy link

jstheoriginal commented Sep 23, 2017

Hey @evermeer I'm trying to add Carthage support to EVCloudKitDao but just hit one final snag.

Because EVReflection now breaks out the CloudKit subspec framework into a new EVReflection_CloudKit.framework file, the imports for EVReflection in EVCloudData.swift and EVCloudKitDao.swift no longer work when I use Carthage to first import its dependencies. The import EVReflection lines need to be changed to EVReflection_CloudKit instead to build. This works for Carthage now, but CocoaPods would break since it doesn't have an EVReflection_CloudKit framework.

Any ideas how to fix this final hiccup?

I'm thinking the only way is to not have separate EVReflection and EVReflection_CloudKit frameworks for Carthage support in EVReflection.

Unless there's a way to rename a framework with CocoaPods so it can be changed from EVReflection to EVReflection_CloudKit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants