-
Notifications
You must be signed in to change notification settings - Fork 133
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 #36
Comments
weissazool
pushed a commit
to weissazool/TransitionKit
that referenced
this issue
Feb 9, 2016
- Added dynamic frameworks for OS X and iOS - Added shared schemes Resolves blakewatters#36
weissazool
pushed a commit
to weissazool/TransitionKit
that referenced
this issue
Feb 10, 2016
- Added dynamic frameworks for OS X and iOS - Shared and added schemes to repository Resolves blakewatters#36
weissazool
pushed a commit
to weissazool/TransitionKit
that referenced
this issue
Feb 10, 2016
- Added dynamic framework targets for OS X and iOS - Shared and added schemes to repository Resolves blakewatters#36
weissazool
pushed a commit
to weissazool/TransitionKit
that referenced
this issue
Mar 3, 2016
- Added dynamic framework targets for OS X and iOS - Shared and added schemes to repository - Add Carthage info to README - Change Product Name to be based on Project Name rather than Target Name in order to be able to use shared umbrella header. Resolves blakewatters#36
weissazool
pushed a commit
to weissazool/TransitionKit
that referenced
this issue
Mar 4, 2016
- Added dynamic framework targets for OS X and iOS - Shared and added schemes to repository - Add Carthage info to README - Change Product Name to be based on Project Name rather than Target Name in order to be able to use shared umbrella header. Resolves blakewatters#36
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there any interest in adding Carthage support?
At a glance, it seems like it should be compatible with TransitionKit's current use of CocoaPods, since it's used only for test targets rather than being a dependency.
As far as I can tell, the changes necessary would be to add a framework target and a shared scheme.
The text was updated successfully, but these errors were encountered: