If your target audience is people who bought their computers or upgraded their operating system on or after April 29, 2005, you should be safe using Ruby in your installer.
I can't personally verify that Snow Leopard (10.6) contained Ruby, but it would be shocking if it was present in the previous and subsequent versions but not Snow Leopard. I can verify from machines in my own home that Lion (10.7), Mountain Lion (10.8), and Mavericks (10.9) all come with Ruby. The Ruby download page indicates that Tiger (10.4) and Leopard (10.5) both include Ruby. Plus, if youre just starting out with Ruby, dont use an old. While you might be tempted to stick with that, you probably shouldnt for a couple reasons: Old versions of the OS shipped with a buggy version of Ruby RVM provides the flexibility to use any version of Ruby that you require. So if you use rbenv you should be able to replace the last part asdf install ruby 2.1.10 with rbenv install 2.1.10.
Optflags= "-Wno-error=implicit-function-declaration" \Īsdf is using ruby-build behind the scene. RUBY_CONFIGURE_OPTS= "-with-openssl-dir= $(brew -prefix ) -with-readline-dir= $(brew -prefix readline)" \ PATH= " $(brew -prefix )/bin: $PATH" \ĬONFIGURE_OPTS= "-with-openssl-dir= $(brew -prefix )" \ LDFLAGS= "-L $(brew -prefix )/lib" \ĬPPFLAGS= "-I $(brew -prefix )/include" \ PKG_CONFIG_PATH= " $(brew -prefix )/lib/pkgconfig" \ Install Ruby 2.1.10 using asdf with some additional compiler configurations. This can live side by side with the latest version of OpenSSL available in Homebrew. So here is a TLDR version of the solution that did work for me. However when I tried to install the Ruby 2.1.10 for the project I got a lot of compilation errors and Google suggested a lot of solutions for me that did not work. And testing in the old ruby version the project was written for first is not a bad start. You should probably not use 2.1 for new projects but if you like me you may have an old project around that needs an upgrade.
Installing ruby 2.1 on macOS Big Sur may be cumbersome.
0 kommentar(er)
