![]() ![]() ![]() As backup, check the Bintray Downloads page. The current DevKit is available at the RubyInstaller download page with older versions available at the archives page.If you previously installed one of the legacy self-extracting DevKit’s, follow the SFX DevKit upgrade instructions.Remove the gcc.bat, make.bat, and sh.bat stub batch files in \bin and the \devkit subdirectory for each Ruby installation using the legacy DevKit. If you previously installed the legacy DevKit devkit-3.4.5r3-20091110.7z, its artifacts were extracted into each Ruby installation and need to be manually removed.While installation is (in general) simple, please ensure you carefully follow each step below. For RubyInstaller versions 1.8.7, 1.9.2, and 1.9.3 use the DevKit 4.5.2 from our main downloads page. NOTE: for the legacy RubyInstaller v1.8.6 use the DevKit-3.4.5 available at our archive downloads page.This is very important because whitespaces in the path to your ruby installation will cause certain error messages as soon as you try to install gems which require the DevKit. NOTE: The path to your must not contain any whitespaces (like in “C:\Program Files\Ruby193”).This is important as it will not work with any other version of Ruby (e.g. A Ruby installation from RubyInstaller.The DevKit is currently available for download as a self-extracting archive and a Windows installer is in development. Many community members also use the DevKit as their “foundation” toolkit for building other native software. ![]() The DevKit is used to build MRI Ruby and the required dependencies needed to deliver the RubyInstaller for Windows. We use the DevKit internally for the RubyInstaller project. The DevKit, based upon MSYS and MinGW components, is an easy-to-install and easy-to-use solution for quickly setting up a “sane” build environment, enabling you to use most native RubyGems developed by the Ruby community. This expectation of a “sane” build environment is not always true for Windows users and is the primary reason why the DevKit was created. A “sane” environment typically means a system with make, gcc, sh and similar *nix build tools installed. In other cases, only the extension source code is available in the gem and the user is expected to have a “sane” environment installed and configured in order to build and use the native gem. In many cases this isn’t a problem because the extension author has provided a binary gem compatible with the users Ruby environment. One of the challenges many Ruby on Windows users have is how to easily use native RubyGems from the community such as the rdiscount or curb gems. ![]() 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. 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. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |