search

clayallsopp / motion-require

Dependency management for RubyMotion, using a pseudo `require`
MIT License
34 stars 5 forks source link

Ripper issues in High Sierra (Apple changed system ruby from 1.8 to 2.3) #16

Open amirrajan opened 6 years ago

amirrajan commented 6 years ago

Looks like the ruby that ships with High Sierra is 2.3.1 now as opposed to 1.8. It looks like there were some major changes to ripper in 2.3.1 that's making motion-support compilation fail. Any ideas? I can help fix it, just need to be pointed in the right direction.

amirrajan commented 6 years ago

Looks like it's effecting motion-support and formotion.

hboon commented 6 years ago

I'm using Ruby 2.3.1 via RVM for RubyMotion, but on macOS 10.12.6. Is there an easy way to reproduce the issue?

amirrajan commented 6 years ago

... have two laptops T_T

Looking for a way to reproduce the issue on Sierra.

amirrajan commented 6 years ago

Related: https://github.com/rubymotion/motion-support/issues/38#issuecomment-366676898

We may not need motion_require anymore?