Closed Julyyq closed 9 years ago
Thanks for your suggestion. I will add the cocoapods command in README; but I would not merge your commit as its description is incorrect.
@truebit The commands is worked for me, it's not professional as I'm not a pythoner, just a recommend, :).
What you meant is to replace your command with the original one, right?
@truebit Nope, to add my code, not replace.
I do not quite understand what Cocoapods does, I found that it seems that pod install
will update Pods.xcodeproj if any changes found. So it seems that there's no need to add this extra command?
@truebit Cocoapods is a package manager for cocoa, like bundler or pip. Exactly that pod install
will udpate the Pods.xcodeproj if any changes found, but for the same Podfile, team members get the different Pods/Pods.xcodeproj/project.pbxproj
file, pod install
don't do sort stuff like xUnique
. By default, Pods folder is not added to gitignore, so I think adding the python2 -mxUnique "${PODS_ROOT}/Pods.xcodeproj/project.pbxproj"
command is needful.
OK, I have added note for cocoapods users in 34a3aca1de678da1ad1a7b8dce3cb94d92d98625
@truebit Good tips,but I saw that your sample code is: $ python2 -mxUnique "${PODS_ROOT}/Pods.xcodeproj"
, It should be ${PODS_ROOT}/Pods.xcodeproj/project.pbxproj
. Pod install
updates the project.pbxproj
file. 😁
maybe you do not know that xUnique supports both path to find project file😄 you can try it😉
— Sent from my mobile phone
On Mon, Mar 23, 2015 at 11:38 PM, Allen.Young notifications@github.com wrote:
@truebit Good tips,but I saw that your sample code is:
$ python2 -mxUnique "${PODS_ROOT}/Pods.xcodeproj"
, It should be${PODS_ROOT}/Pods.xcodeproj/project.pbxproj
.Pod install
updates theproject.pbxproj
file. 😁Reply to this email directly or view it on GitHub: https://github.com/truebit/xUnique/pull/19#issuecomment-85053388
@truebit You must be prepense.😢
nope, actually I used these two paths in the two introduced methods if you noticed:)
Cocoapods is a common tool for iOS development stuff, adding "cocoapods support document" makes sense of convenience for preventing being confused to many developers I think.