Open amirrajan opened 6 years ago
Looks like it's effecting motion-support
and formotion
.
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?
... have two laptops T_T
Looking for a way to reproduce the issue on Sierra.
Related: https://github.com/rubymotion/motion-support/issues/38#issuecomment-366676898
We may not need motion_require anymore?
Looks like the ruby that ships with High Sierra is
2.3.1
now as opposed to1.8
. It looks like there were some major changes toripper
in 2.3.1 that's makingmotion-support
compilation fail. Any ideas? I can help fix it, just need to be pointed in the right direction.