wxruby development - Mar 2008 - How to build and test wxRuby

Greetings,

I''m using wxRuby2 to develop an app, and I''d like to have a
build of
wxRuby2 to work from so that when I find something that doesn''t work,  
I can maybe attempt to find out why and, who knows, maybe even submit  
a patch once in a while.  I should start by saying that I''m on Mac OS  
X 10.5.2.  What I''d like to do is to have this build of wxRuby2  
corralled in a directory along-side the wxWidgets build that it  
depends.  I''ve managed to do this, almost.

I created a directory, wxRuby-dev, into which I''ve checked out the  
trunk of wxRuby2 and wxWidgets 2.8.7.  I configured and built  
wxWidgets using these instructions: HowToBuildWxWidgets, with the  
exception of setting --prefix=$HOME/src/wxRuby-dev.  After ''make  
install'', things looked good.

Then I built wxRuby2 by first setting PATH=$HOME/src/wxRuby-dev/bin: 
$PATH so that rake would find wx-config there.  It seemed to build ok,  
but ''rake install'' doesn''t seem to be doing much.  At
this point I
should say that I had, before this, zero experience with the whole  
rake experience, so I''m probably doing something blatantly obvious to  
the rest of you.  Here''s the output from rake install:

(in /Users/david/src/wxRuby-dev/wxruby2)
Enabling STATIC build
Enabling RELEASE build
Enabling UNICODE build
The following wxWidgets features are not available and will be skipped:
   StyledTextCtrl
   StyledTextEvent

Even if rake install was successful, I''m not quite sure how to make  
ruby use this particular version of wxRuby.

All of this corralling is an attempt to keep separate my own version  
of wxRuby from the one I''ve installed through rubygems.  Perhaps this  
is the wrong way to go about it.  I''m open to any and all suggestions.

Thanks in advance,
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/wxruby-development/attachments/20080303/cca190f4/attachment.html

Hi David

David Whetstone wrote:
> I''m using wxRuby2 to develop an app, and I''d like to have
a build of
> wxRuby2 to work from so that when I find something that doesn''t
work,
> I can maybe attempt to find out why and, who knows, maybe even submit 
> a patch once in a while. 
Great .. we love patches
> I created a directory, wxRuby-dev, into which I''ve checked out the
> trunk of wxRuby2 and wxWidgets 2.8.7.  I configured and built 
> wxWidgets using these instructions: HowToBuildWxWidgets 
> <http://wxruby.rubyforge.org/wiki/wiki.pl?HowToBuildWxWidgets>, with 
> the exception of setting --prefix=$HOME/src/wxRuby-dev.  After
''make
> install'', things looked good.
This sounds fine.
> Even if rake install was successful, I''m not quite sure how to
make
> ruby use this particular version of wxRuby.
>
> All of this corralling is an attempt to keep separate my own version 
> of wxRuby from the one I''ve installed through rubygems.
In developing wxRuby and wxRuby-based apps I have a couple of different 
versions around. For me the most efficient way to switch is by using 
ruby -I argument to add library paths.

So I have my debug, self-compiled wxRuby directory from SVN HEAD in 
~/code/wxruby2. I build this using ''rake'' default task (not
''install'').
To run code with this build I do:
ruby -I~/code/wxruby2/lib test_script.rb

To run code against the reference rubygems last release:
ruby -rubygems test_script.rb

If you''re looking to do development work on the SWIG/C++ side
I''d
suggest using a DEBUG build of wxWidgets. Change
''--disable-debug'' in
the configure parameters. The debug builds are bigger, slow to link and 
marginally slower to use, but you''ll get the benefit of assertions and 
accurate gdb backtraces.

cheers
alex

Thanks for your help Alex.  I''m up and running!

- David