It dies looking for nmake.  I try it again in the visual c++ command line environment and it dies compiling config.h
because it insists on MS C version 1200, which is very old.  I think it is VC 6.0.  I have an old version of MSC but
it is version 13.something.  There is a free download of 'Visual C++ 2008 Express' from Microsoft but that's not version
1200 either.

The config.h is apparently installed with ruby, not ruby-debug. Is that version of C what ruby is built out of?

I presume there is a reason for requiring version 1200 and I do not feel like debugging the debugger right now, since
I suspect there is a windows binary somewhere I can download.

If you want me to hack at it and try building it with the old C compiler from Visual Studio 2003, or to try the free
version of 2008, let me know; I just might do it.  But I'm not going to dive in only to find I'm reproducing someobody
else's work.  So let me know the resolution of this.

If I could find the old debug.rb I would use it but it isn't in ruby\bin, and the debugger command fails in script\console.
There's a debug.rb in ruby\lib, but I don't know if it's the command I'm looking for, as they put in lib for what is
probably a good reason.

I put a debugger call into my login controller and it just skipped over it, leaving a message in development.log, nothing
appeared in my mongrel window; undoubtedly because ruby-debug is simply not installed.  Running script\server --debugger
told me to install ruby-debug, which is how I started.

>gem install ruby-debug
Building native extensions.  This could take a while...
ERROR:  Error installing ruby-debug:
        ERROR: Failed to build gem native extension.

C:/InstantRails/ruby/bin/ruby.exe extconf.rb install ruby-debug
creating Makefile

nmake

Microsoft (R) Program Maintenance Utility Version 7.10.3077
Copyright (C) Microsoft Corporation.  All rights reserved.

        cl -nologo -I. -IC:/InstantRails/ruby/lib/ruby/1.8/i386-mswin32 -IC:/InstantRails/ruby/lib/ruby/1.8/i386-msw
-c -Tcruby_debug.c
ruby_debug.c
c:\InstantRails\ruby\lib\ruby\1.8\i386-mswin32\config.h(2) : fatal error C1189: #error :  MSC version unmatch
NMAKE : fatal error U1077: 'cl' : return code '0x2'
Stop.


Gem files will remain installed in C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/ruby-debug-base-0.10.0 for inspection
Results logged to C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/ruby-debug-base-0.10.0/ext/gem_make.out

Date: 2010-02-11 10:01
Sender: Katherine Katherine

Great workaround to install ruby-debug and ruby-debug-ide:
http://www.definenull.com/content/netbeans-6-ruby-fast-debugger

In brief:

Download ruby-debug-base gem 
from http://rubyforge.org/frs/download.php/46863/ruby-debug-base-
0.10.3-mswin32.gem to
C:\some_location

cd /d C:\some_location

gem install ruby-debug-base -l
gem install ruby-debug
gem install ruby-debug-ide -v 0.4.6

Date: 2008-02-28 18:09
Sender: Fred Seltzer

Hmmm.   I just hacked up my copy of config.h to no longer 
require the specific version of the C compiler and it built 
and ran just fine.  I don't want to go back and revisit 
this. Let's call it closed...

Fredonrails...

Date: 2008-02-28 11:52
Sender: Martin Krauskopf

Seem the binary was released and this might be fixed?

Date: 2008-02-13 14:28
Sender: Martin Krauskopf

We quickly tried on colleague's Windows:

  gem install -l ruby-debug-base-0.10.0-mswin32.gem
  gem install -r --ignore-dependencies ruby-debug -v 0.10.0

and seems to work smoothly.

Date: 2008-02-13 07:24
Sender: Martin Krauskopf

Fred, could you try the gem Rocky built. I do not have access
to Windows machine just now but I'll try later today (Europe)
in the office. If it works for both of us it would likely mean
kind of 'go'.

Date: 2008-02-08 01:46
Sender: Rocky Bernstein

Using instructions from eigenclass
http://eigenclass.org/hiki.rb?cmd=view&p=cross+compiling+rcov
rt&key=mingw I've been able to build a mswin32 gem for
ruby-debug-base.

I'm not sure how well it works or if it works at all. So I've
put it temporarily at http://bashdb.sf.net/ruby-debug-base-0.10.0
-mswin32.gem

But if this is useable, let me know and I'll add it to the ruby-debug
files section on rubyforge.

Martin: the intention wasn't not to provide mswin32 binaries,
so much as not knowing how to do so. Windows remains a pest.
In the past, Kent has handled making mswin32 gems.

Fred: My understanding regarding the problem with using a newer
C compiler is that the runtime is not compatible with the older
one. I am given to believe that you'd find a problem when you
have extensions using the older runtime that use things that
are not compatible with the newer runtime. Caveat Emptor.

Date: 2008-02-07 17:01
Sender: Fred Seltzer

I finally decided to gamble with my slightly newer compiler,
which says it is:
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version
13.10.3077 for 80x86

I just took out the lines in config.h that asked for version
12 and reinstalled the gem.  It built fine and installed the
debugger.  The debugger seems to work fine. I've used to
find bugs in my Rails app.  This is version 0.10.0 of
ruby-debug and ruby-debug-base.

Kinda like living on the edge.  Or the fast lane.  Or something.

Date: 2008-02-06 20:03
Sender: Martin Krauskopf

Hi Rocky. Do you plan to release pre-compiled binary for 0.10.0
and the future releases. This was used to be in "<=
0.9.3" times. We somehow "depend" on it in the
IDE.

Date: 2008-01-07 23:05
Sender: Rocky Bernstein

To install on Microsoft Windows, unless you run under cygwin
or mingw, you'll need Microsoft Visual C++ 6.0 --  also known
as VC6.
 http://rubyforge.org/tracker/index.php?func=detail&aid=16774
&group_id=1900&atid=7436
suggests why.

Or as you note, use an older pre-compiled binary.

Date: 2008-01-03 08:59
Sender: Fred Seltzer

The workaround is to go back one version:

> gem install ruby-debug -v 0.9.3