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
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
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 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: rakewx_rb.patch Url: http://rubyforge.org/pipermail/wxruby-users/attachments/20060825/4145982c/attachment.pl
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=1I 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