Update README to describe more recent ruby versions #181
Conversation
| @@ -251,7 +251,7 @@ several settings for `Rake::ExtensionTask`: | |||
| ## Cross compilation - the future is now. | |||
|
|
|||
| Rake-compiler also provides a standardized way to generate, from either Linux | |||
| or OSX, extensions and gem binaries for your Windows users! | |||
| or OSX, extensions and gem binaries for your Windows and Linux users! | |||
There was a problem hiding this comment.
I think that macOS users can't generate fat gems for Linux without rake-compiler-dock.
There was a problem hiding this comment.
Ah, Homebrew provides x86_64-elf-gcc.
How do users prepare Rubies for Linux on macOS?
There was a problem hiding this comment.
I think by specifying rake-compiler cross-ruby HOST=x86_64-elf-gcc or so. But I have little experience with MacOS only.
There was a problem hiding this comment.
cross-ruby expects only Mingw-w64 builds. For example, it uses .exe extension for Ruby binary.
rake-compiler doesn't support cross compiling fat gems for Linux. Could you revert related changes?
There was a problem hiding this comment.
cross-rubyexpects only Mingw-w64 builds.
Not by any means! It is pretty agnostic to the build target. Just the default is mingw, if no HOST=triple is given.
But you're right, ruby.exe is an expected file target. However this actually doesn't hurt on other cross targets - it's only that the file target is never satisfied so that the build is triggered in any case. Maybe we should fix this inaccuracy, now that rake-compiler cross-ruby is used for many different targets.
There was a problem hiding this comment.
It just works accidentally. It's not a "supported" feature. :-)
Could you revert this for now?
The current README is quite outdated and should be updated.