Please refer to Troubleshooting for known issues or RubyInstaller Google Group for further help. Next run ruby -rubygems -e "require 'rdiscount' puts RDiscount.new('**Hello RubyInstaller**').to_html" to confirm that the rdiscount gem is working. RDiscount should install correctly and you should see Temporarily enhancing PATH to include DevKit. in the screen messages. Confirm your Ruby environment is correctly using the DevKit by running gem install rdiscount -platform=ruby. NOTE: you may need to use the -force option to update (with backup of the originals) the above mentioned files as discussed at the SFX DevKit upgrade FAQ entry. This step installs (or updates) an operating_system.rb file into the relevant directory needed to implement a RubyGems pre_install hook and a devkit.rb helper library file into \lib\ruby\site_ruby. finally, ruby dk.rb install to DevKit enhance your installed Rubies.ruby dk.rb review to review the list of Rubies to be enhanced to use the DevKit and verify the changes you made to it are correct.edit the generated config.yml file to include installed Rubies not automagically discovered or remove Rubies you do not want to use the DevKit with.Your installed Rubies will be listed there (only those installed by a RubyInstaller package are detected at present). ruby dk.rb init to generate the config.yml file to be used later in this Step.In the instructions that follow, the directory that you selected is identified as. If you already have 7-Zipinstalled, you can simply right-click it and extract it’s contents as you would a normal 7z archive. NOTE: the SFX is really a 7-Zip archive with a bit of embedded magic. Left double-click the self-extracting executable (SFX) downloaded from Step 2 and choose a directory (without spaces) to install the DevKit artifacts into.As backup, check our GitHub 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. Currently no issues have been reported when either the 4.5.0 or 4.5.1 DevKit’s are used with previous RubyInstaller versions. For RubyInstaller’s previous to 1.9.2-p0 you may feel more comfortable using the DevKit-3.4.5-CCYYMMDD-sfx.exe as the earlier RubyInstallers were built using MSys/MinGW v3.4.5.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. 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 |