[Wxruby-users] The great MSVC wxruby-swig bug hunt!

Curt Hibbs
Tue, 20 Jul 2004 13:24:12 -0000

Nick wrote:
>
> Hi everyone,
>
> As Kevin has just announced, wxruby-swig has been moved into CVS as a
> toplevel project. It still is not in a "releasable" form yet, but
it now
> builds on more systems than it doesn''t, and is moving towards
stability.
> Because of the complexity of the build environment, we''re using
rake
> (http://rake.rubyforge.org) as a build system instead of the standard
> extconf.rb file.
>
> A lot of work has recently been put into getting wxruby-swig to build on
> Windows using the Microsoft Visual C++ compiler (MSVC) tools. It now
> successfully builds (or should successfully build), but it isn''t
> running. We''re tracking what the problem is, but we could use some
help.
>
> So all you ruby programmers with MSVC/wxWidgets knowledge, we''re
calling
> out for help! Pull the head branch from CVS, break out the debuggers and
> help us figure out whats going wrong! Are we incorrectly initializing
> wxWidgets? Is SWIG generating bad code? Did we forget a semicolon? Any
> help is appreciated! (This is also a good time to comment on the new
> build system)

One tip that may or may not be helpful...

When I was getting the old, non-swig version to run on Windows, I also ran
into problems where everything would compile, but it would not run. In my
case, I was building wxWidgets using the MSVC project files (i.e., I was
building it from the IDE) -- I could never get wxRuby work with this. When I
switched to using nmake wxWidget''s msvc makefiles, I finally got it
work.

Also, with wxRuby version 0.3.0, I tried switching to the vc++ 7.1 compiler
(from VS .NET 2003). This also compiled just fine but would not run. At that
point I was trying to get the release out as quickly as possible, so I
didn''t even try to figure it out -- I just went back to vc++ 6.0 and
that
worked, once again, without any problems.

Hope that helps.

Curt