Does anyone have a dmg image or .bundle of wxRuby built against wxwindows 2.4/2.5/2.6 and Ruby 1.8? I attempted to build all the parts with not much success. -- -- I am not a number I am a man! _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users
Hi Sal Sal Scotto wrote:> Does anyone have a dmg image or .bundle of wxRuby built against > wxwindows 2.4/2.5/2.6 and Ruby 1.8? >I''ve built both wxruby and wxruby2 against 1.8, wx 2.6 on OS X 10.3. For OS X WxWidgets 2.6 is better than 2.4 - which means you are best using wxruby2, which supports this version. I can happily send you a wxruby2.bundle, but it''s a little dated (Sept/Oct CVS HEAD). It''d be better to build an up-to-date if poss, and also for 10.4> I attempted to build all the parts with not much success. >Perhaps you could post the problem you''ve run into - there are a few people using OS X so hope we can help you track down the problem, alex
I had slews of compiler errors, I search long and hard trying to find fixes, but had little luck. Buildign via darwinports fails badly. Does wxruby2 support draop and drop yet ? Thats the biggest feature im using (cross platform ruby app) the bundle would be appreciated On 11/10/05, Alex Fenton <alex at pressure.to> wrote:> > Hi Sal > > Sal Scotto wrote: > > > Does anyone have a dmg image or .bundle of wxRuby built against > > wxwindows 2.4/2.5/2.6 and Ruby 1.8? > > > I''ve built both wxruby and wxruby2 against 1.8, wx 2.6 on OS X 10.3. For > OS X WxWidgets 2.6 is better than 2.4 - which means you are best using > wxruby2, which supports this version. > > I can happily send you a wxruby2.bundle, but it''s a little dated > (Sept/Oct CVS HEAD). It''d be better to build an up-to-date if poss, and > also for 10.4 > > > I attempted to build all the parts with not much success. > > > Perhaps you could post the problem you''ve run into - there are a few > people using OS X so hope we can help you track down the problem, > > alex > _______________________________________________ > wxruby-users mailing list > wxruby-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users >-- -- I am not a number I am a man! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wxruby-users/attachments/20051110/1804a064/attachment.htm
> I had slews of compiler errors, I search long and hard trying to find > fixes, but had little luck.Just compiled CVS HEAD on OS X 10.3 - I''ll send you the bundle off-list. It''d still be useful if you could post the errors you got though, just in case there''s a problem with Tiger.> Buildign via darwinports fails badly.Haven''t tried it -- I have ruby 1.8.2, swig 1.3.25, wxwidgets 2.6.2 all built from source. Dunno if anyone has had success with this?> Does wxruby2 support draop and drop yet ? Thats the biggest feature im > using (cross platform ruby app)I might be wrong, but I don''t think the relevant classes (DropSource, DropTarget, DataObject etc) are available yet. Just for list reference - though the bundle seems to work OK, I got a lot of warnings of this type, which I haven''t seen before on OS X / wxruby: swig/classes/include/wxBitmapButton.h:9: Warning(471): Unable to use return type wxPoint in director method wxBitmapButton::ScreenToClient (skipping method). (similarly for lots of methods, with return type wxPoint, wxSize, wxRect, wxRegion, wxString, wxColour) alex
Alex Fenton wrote:> Just for list reference - though the bundle seems to work OK, I got a > lot of warnings of this type, which I haven''t seen before on OS X / wxruby: > > swig/classes/include/wxBitmapButton.h:9: Warning(471): Unable to use > return type wxPoint in director method wxBitmapButton::ScreenToClient > (skipping method). > > (similarly for lots of methods, with return type wxPoint, wxSize, > wxRect, wxRegion, wxString, wxColour)This is a known problem on all platforms. SWIG automatically handles returns of object pointers, but not returns of actual objects like these. We need to add typemaps for each returned class, to create a new ruby object of the appropriate type. Kevin