Should I place it to some permanent location and then run installation scripts or I can simply run installation script and then delete the unpacked DevKit folder (in a second case I assume that this script injects DevKit into Ruby installation in some way)? – the answer to this question should be placed in first lines of installation guide as it is very important.Īnswer: The file should be in its permanent location before running “ruby dk.rb init”. Questions from the end user: I downloaded DevKit as exe file, unpacked it.
#Rubyinstaller archive install#
Then cd to it, run ruby dk.rb init and ruby dk.rb install to bind it to ruby installations in your path. Quick startĭownload it, run it to extract it somewhere (permanent). Simply download, double-click, choose an installation directory, run the Ruby install helper script, possibly tweak a config.yml file for your system specifics, and you’re ready to start using native Ruby extensions. It doesn’t work with RubyInstaller-2.4 or newer! The DevKit is a toolkit that makes it easy to build and use native C/C++ extensions such as RDiscount and RedCloth for Ruby on Windows. See also the RubyInstaller-2.4 announcement. Starting with RubyInstaller-2.4 we use MSYS2 as our Development Kit. The following description is valid for RubyInstaller-2.3 and older. Below this comment is the copy and paste from Development Kit
If you have the time please edit the article the match the one in the original article I did not have ample time for formatting.
Above this comment is the previous article
0 kommentar(er)
