Intriguing developments

Non-debug build of wxRuby allows the tip of the day to be
visible on 
Windows.  Also, I get the caret example crashes with page-up
on Windows 
with the ANSI build of wxWindows.  I may try the unicode
build to see 
how that works.

I've been up to my eyeballs working on a release of my
company's 
software.  Once that's out the door I can hopefully put a
few more 
cycles into the release.

Roy
_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users

Roy Sutton wrote:
> Non-debug build of wxRuby allows the tip of the day to
be visible on 
> Windows. 
Interesting - this and other threads got me to try building
a debug 
WxWidgets and compiling wxRuby against it. Turns out that
doing so 
causes quite a lot of stuff to hang and not display,
including tips, 
password and font dialogs. Weird. Definitely need to ensure
we ship gems 
from release builds.

a
_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users

Alex Fenton wrote:
> Definitely need to ensure we ship gems 
> from release builds.
>   
Meant to submit the attached patch, to enable forcing use of
a release 
build via rake, via

rake RELEASE=1

Otherwise, I don't think there is a way to tell our compile
system to 
build against a release wxWidgets, if the default wx-config
happens to 
point to a debug one.

alex


Index: wxruby2/rake/rakewx.rb
============================================================
=======
RCS file: /var/cvs/wxruby/wxruby2/rake/rakewx.rb,v
retrieving revision 1.40
diff -b -u -r1.40 rakewx.rb
--- wxruby2/rake/rakewx.rb	25 Aug 2006 15:09:47 -0000	1.40
+++ wxruby2/rake/rakewx.rb	25 Aug 2006 16:12:49 -0000
 -17,7
+17,12 
 $swig_options = " -fvirtual "
 $swig_minimum_version = '1.3.29'
 
+# force building against either a release build or debug
build of
+# wxWidgets. Only one should be used; if neither is
specified, the
+# default wx configuration will be used. Use of these
options depends on
+# there being an appropriately compiled version of
wxWidgets available.
 $debug_build = ENV['DEBUG'] ? true : false
+$release_build = ENV['RELEASE'] ? true : false
 
 def have_good_swig
 	begin
 -36,6
+41,8 
 def wx_config(opt)
     if $debug_build
       debug_mode = '--debug=yes'
+    elsif $release_build
+      debug_mode = '--debug=no'
     end
     return `wx-config # #`.strip + "
"
 end
_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users

On Fri, 2006-08-25 at 17:15 +0100, Alex Fenton wrote:
> Alex Fenton wrote:
> > Definitely need to ensure we ship gems 
> > from release builds.

I have mixed feelings about that, because it is really just
hiding
actual problems. But for now, it's ok.

> Meant to submit the attached patch, to enable forcing
use of a release 
> build via rake, via
> 
> rake RELEASE=1

I see you changed this to WXRUBY_RELEASE, which is good. I
like the
idea, but your patch wouldn't actually force a RELEASE
build if DEBUG
was the default (as it is on my system). So I made a few
further changes
and checked it in.

Thanks,

Kevin


_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users