title: Trying to install dev kit for ruby in windows 7 but fails
body: <p>I am trying to install the dev kit for ruby for the CommandT plugin for vim and I am hit with</p>
  
  <pre><code>C:\Users\Administrator&gt;gem install rdiscount --platform=ruby
  ERROR:  Error installing rdiscount:
          The 'rdiscount' native gem requires installed build tools.
  
  Please update your PATH to include build tools or download the DevKit
  from 'http://rubyinstaller.org/downloads' and follow the instructions
  at 'http://github.com/oneclick/rubyinstaller/wiki/Development-Kit'
  </code></pre>
  
  <p>I have already run install devkit at shown below </p>
  
  <pre><code>C:\devkit&gt;ruby dk.rb init
  [INFO] found RubyInstaller v1.9.3 at C:/Ruby193
  
  Initialization complete! Please review and modify the auto-generated
  'config.yml' file to ensure it contains the root directories to all
  of the installed Rubies you want enhanced by the DevKit.
  
  C:\devkit&gt;ruby dk.rb review
  Based upon the settings in the 'config.yml' file generated
  from running 'ruby dk.rb init' and any of your customizations,
  DevKit functionality will be injected into the following Rubies
  when you run 'ruby dk.rb install'.
  
  C:/Ruby193
  
  C:\devkit&gt;ruby dk.rb install
  [INFO] RubyGems override already in place for C:/Ruby193, skipping.
  [WARN] DevKit helper library already exists for C:/Ruby193, skipping.
  </code></pre>
  
  <p>What could be possibly going wrong? </p>
  
  <p><strong>Edit:</strong> I tried </p>
  
  <pre><code>c:\devkit&gt;ruby dk.rb install --force
  
  Configures an MSYS/MinGW based Development Kit (DevKit) for
  each of the Ruby installations on your Windows system. The
  DevKit enables you to build many of the available native
  C-based RubyGems that don't yet have a binary gem.
  
  Usage: ruby dk.rb COMMAND
  
  where COMMAND is one of:
  
    init     prepare DevKit for installation
    review   review DevKit install plan
    install  install required DevKit executables
  </code></pre>
  
  <p>uninstalled and installed again with a clean directory. But the error remains the same. </p>