Carthage and CocoaPods support #309
Reference in New Issue
Block a user
No description provided.
Delete Branch "cocoapods-support"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is first attempt to add support for CocoaPods. It is currently not working because CocoaPods requires a valid semver number (and a corresponding git tag) as the library version.
This is based on #305 and should be merged after that PR is merged.
@emilsjolander @dshahidehpour Please check if the author information in the
YogaKit.podspec
file is correct.Once this PR is merged in order for people to actually be able to install this using CocoaPods, the pod must be published to CocoaPods' trunk. Which requires to have an account. For more information check https://guides.cocoapods.org/making/getting-setup-with-trunk.html.
Also keep in mind that every time you make a new release you need to update the
version
property insideYogaKit.podspec
and publish a new version to trunk.@@ -0,0 +1,21 @@
Pod::Spec.new do |spec|
dshahidehpour@gmail.com ;)
@@ -0,0 +1,21 @@
Pod::Spec.new do |spec|
YogaKit is a view layout library which is powered by Yoga, a layout engine which implements Flexbox.
@@ -0,0 +12,4 @@
@property (strong, nonatomic) UIWindow *window;
nit: delete
@@ -0,0 +6,4 @@
* LICENSE-examples file in the root directory of this source tree.
*/
#import "AppDelegate.h"
Do we have to regenerate this? Let's revert this.
@guidomb, this is amazing! I left a few comments.
@@ -0,0 +1,21 @@
Pod::Spec.new do |spec|
I've copied pasted that description from the one that appears in Yoga's GitHub repository. Should I change it anyways?
@dshahidehpour You made some comments in files that are originally part of @hartbit PR, #305 . For some reason I could not make
hartbit/carthage-support
as the target branch for this PR (GitHub did not show @hartbit's fork as an option and I couldn't fork his repo because I've already had a fork of yoga). I think those suggestion should be addressed in #305. Sorry for the extra work in the review process@guidomb but as you improved on my PR, wouldn't it be better to rename this PR Cocoapods + Carthage support and fix everything here?
@hartbit If you agree with that, sure. In that case I would suggest closing the other PR and focus on trying to fix the buck build and the comments suggested by @dshahidehpour here.
@guidomb Any update on this? The changes to add swift support have landed, so, you probably won't run into as many (if any) rebase problems.
@dshahidehpour Sorry, I've been on vacations the last week. Cool that #322 has been merged!!! I'll try to get this working tomorrow. I'll let you know if I had any issues.
Have you defined a version number that should be used in the CocoaPods podspec file?
@guidomb No defined a version yet. I'll do that tomorrow! Thanks for reminding me. Will most likely be version
1.0.0
but i'll have to discuss it with some others.@guidomb lets wait on #328 to merge this.
OK, I was about to start working on it. I'll subscribe to #328 and get back to this once that one is merged. Thanks for letting me know!
@guidomb #328 is going to be closed momentarily, any chance we could start on this again? @emilsjolander can help with the versioning :)
I'll try to work on this tomorrow. Will #328 be merged into
master
?yeahp!
I've made a new PR to address this -> https://github.com/facebook/yoga/pull/352
Pull request closed