Comment - Can't build framework using rakefile #14
Comments
|
Hmm. It looks like something is preventing you from installing the gem itself, which looks to be unrelated to how our build scripts work, but rather to your local gem environment. |
|
I was able to repro this locally on OS X 10.11. The issue is that in El Capitan, the header Simple way to solve it, create a symlink from the new path to the old path, e.g.: Then re-run |
|
@avnerbarr It's Chinese Great Fire Wall problem .It says, Then I configure the proxy. It fixed the problem. Also, you can try use another mirror which is not blocked in china. |
|
Yep this doesn't work, tried a bunch of times, this is the error I'm getting, and NO it's not the Great Firewall, I'm in the USA. Here's the error code: first off, I'm running Yosemite, all up to date, everything is up to date, latest version of all Apple software. Perhaps this is a Ruby version or Rake version problem? I don't know, I've been searching all day for answers. I refuse to use Cocoa Pods, and my hope is that perhaps you can just rebuild it quickly on your end and push that build, prebuild would save everyone time and allow those who enjoy NOT using Pods to use Parse, thank you sir! rake aborted! just deleted .rvm folder and reinstalled, and just installed ruby 2.2.2, this is the result, hug:Parse-SDK-iOS-OSX ghrd$ rake package:deployment --trace Don't know how to build task 'package:deployment' here's my gemfile.lock after running bundle install, here's my gemfile.lock GEM PLATFORMS DEPENDENCIES BUNDLED WITH |
|
Here's some info that may help, or it may not help, either way, this is what I've managed to extract so far from the rake building process: My set up, ruby 2.2.2 with rvm, my Gemfile.lock looks exaclty like the post above me and I'm on a late release 2014 Mac Book Pro, I'm up to date on everything using Yosemite, no updates pending. I deleted and reinstalled Home Brew and RVM just to make sure I wasn't going insane when I couldn't build the library using the RakeFile. So, with that said, I then did the following: First off, I cloned the Repo using this: git clone --recursive https://github.com/ParsePlatform/Parse-SDK-iOS-OSX.git then the following steps produced the large error mess in the Pastebin I've attached to this message: $ cd Parse-SDK-iOS-OSX rake build:ios # Build iOS framework NO listing for "package:deployment", but that's fine, so I went wild west and derived the "best guess" based on what I saw, back to terminal: $ rake package:prepare //why not give it a shot, perhaps I have to prepare something? **nothing happened with the above command, but I didn't get shut down, so that is a good sign* $ rake package:frameworks[aRandomNumber] //I'm guessing here, so I picked 1.1 as a solid number just to see what happened// AFTER my handy guess work of putting in "1.1" the following happened: ▸ Cleaning Parse/Parse-iOS [Release] I was feeling pretty good about myself, but THEN, the following nightmare happened: That's a lot nasty errors, so, I looked in the build folder and I found this: This is a screenshot of the Parse 1.7.5 build to my new "I'm just playing with rake commands build" and here's the comparison. I've not tried to run with this library since it had a lot errors due to my not so successful guess work:
So, anyway, I zipped up this entire folder and did this: $ git clone --recursive https://github.com/ParsePlatform/Parse-SDK-iOS-OSX.git rake build:ios # Build iOS framework and BOOM, here's the output: Here's the very long output: So, this looks like the build MAY have worked, right? Well, I'd say that I feel confident that the build worked, but the truth is that my knowledge of Ruby is building just a simple web site, and as such, my knowledge of Ruby is at the level of ZERO knowledge at all, but it looks like I may have a good start, so here's the final screenshot, but I'll need a "hell yeah" or a "you f*&cked up bad" before I'll know if this is what I'm supposed to be seeing. Screenshot of Ruby experiment:
Oh yeah, there's more to this screenshot, but it looks the same as the iphonesimulator release and is named "Release-ios-iphoneos" Thanks a billion, you are doing a good service! ... Continuation, after all of that, I just did the same thing as above again, but I just called to these two items: $ rake package:prepare I didn't put any numbers in the "frameworks" brakects, I just left it blank, and here's the log, no errors, the script built a zipped archive named "Parse-OSX.zip", and looks like it may have done what it was suppose to do, I'll wait for you to decide if this method works, but here's the screen shot:
And here's the log: Again, thanks for everything you do, let me know if you need any other information to help you out! |
|
@larceneaux, this is mind-blowingly amazing repro. The best one I've seen in my life! I think we have a wrong statement on the read me - the one you are looking for is definetly 'rake package:frameworks'. It should produce 2 archives inside 'build/release' folder. Will dive deep into this tomorrow and will update this issue on my findings. |
nlutsenko
added
type:docs
|
No problem, I'm anal about getting stuff to work, again, thanks for everything! |
|
Also, one last quick thing, I just tested it, and it works, here's the layout in Xcode, it compiled AND ran on the simulator with a "You're all set with Parse" message after a quick "clean" and everything is linking perfectly:
|
Did
git clone --recursive https://github.com/ParsePlatform/Parse-SDK-iOS-OSX.gitfrom root directory tried running rake command
I guess I need to install the "Gemfile" (? )
Tried :
gem install bundlerand then:
bundle installand then got errors:
An error occurred while installing nokogiri (1.6.6.2), and Bundler cannot continue.
Make sure that
gem install nokogiri -v '1.6.6.2'succeeds before bundling.The text was updated successfully, but these errors were encountered: