您的位置:首页 > 其它

CocoaPods安装历险

2014-02-28 14:46 337 查看
网上一直说cocoapods好用,所以我一直想安装试试,可是还真蛋疼啊,总是装不上去,终于有一天不辞辛苦的研究出来原因了/Users/Second/.rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find 'cocoapods' (>= 0) among 14 total gem(s) (Gem::LoadError)from /Users/Second/.rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/dependency.rb:309:in `to_spec'from /Users/Second/.rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_gem.rb:53:in `gem'from /Users/Second/.rvm/rubies/ruby-2.1.0/bin/pod:22:in `<main>'from /Users/Second/.rvm/gems/ruby-2.1.0@global/bin/ruby_executable_hooks:15:in `eval'from /Users/Second/.rvm/gems/ruby-2.1.0@global/bin/ruby_executable_hooks:15:in `<main>'解决:这里是安装好cocoapods之后使用命令pod install的时候显示出来的,原因是我安装命令是sudo gem install cocoapods所以,我们以后在使用cocoapods的命令时候就要前面加个sudo命令,原理自己慢慢想吧,其实应该看到这里都懂了2、还有就是如果使用命令sudo gem install cocoapods的时候一直装不上去,就需要修改gem sources,修改一定要修改正确,我蛋疼的地方就在这,明明淘宝的地址加载进去是正确的,可就是不对,后面我是复制过去的,呵呵,可以了- -!没办法做朋友了3/
Analyzing dependencies
[!] Pod::Executable pull
解决:
If you landed here on or after January 30th 2014, there is a break in CocoaPods causing this. Please read the related blog post found here: http://blog.cocoapods.org/Repairing-Our-Broken-Specs-Repository/or do:
pod repo remove master
pod setup
[!] Unable to find a pod named `AFNetworking'
解决:Something went wrong with the setup of the ~/.cocopods directory initially, it wasn't a git directory. I deleted it, reinstalled the gem, then ran pod setup again, and it is working.删除电脑用户中的.cocopods文件夹,重新设置cocoapods,当然,保险点的话是要重新安装cocoapods
the file pods.xcodeproj could not be unlocked
解决:I had this problem recently. I don't know about the missing frameworks, but if you go to your project folder within terminal and modify the permissions on the project files, you should be able to open the project. I personally had to modify multiple files and folders to be able to get it to stop asking me if I want to unlock my files.Steps that Worked for Me:Use the terminal to go to the folder that contains the xcworkspace file. Type "sudo chmod 777 NameOfYourWorkspaceFile.xcworkspace" (Please don't literally use that file name unless that's what your xcworkspace file is called). This should change the permissions for your entire workspace, but you will still have the unlock problem with your Pods project.From within the same directory, you can do another chmod on the Pods folder like so: "sudo chmod 777 Pods".After that, go into your Pods folder by typing "cd Pods" and then modify the permissions on your Pods.xcodeproj file as so: "sudo chmod 777 Pods.xcodeproj".Like I said previously, these permission changes were enough to get xCode to stop asking me if I want to unlock my projects. I don't know if it will be enough for you though. Hopefully it helps!文件权限不足,需要修改权限
                                            
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息