These patches (should) give us support for compiling against Ruby 1.9. Roy _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users
Hi Thanks for these patches. If I understand rightly, these are a back/cross port from swig''s CVS HEAD. If so I would prefer not to apply them, and let support for 1.9 come with the release of SWIG 1.3.30. fixmodule.rb etc are probably the most magic (i.e. important but difficult, and also fragile to SWIG releases) bits of our build system. I would prefer to limit additions to fixes for serious bugs - also since we are going to want to unpick these scripts at some stage. I see support for 1.9 as a nice-to-have, but I don''t think it''s unreasonable for now to ask someone using unstable ruby to compile SWIG from CVS. But I''m open to committing these patches if people feel strongly about it? alex Roy Sutton wrote:> These patches (should) give us support for compiling against Ruby 1.9.
Alex Fenton wrote:> I see support for 1.9 as a nice-to-have, but I don''t think it''s > unreasonable for now to ask someone using unstable ruby to compile SWIG > from CVS. >I''m fine with waiting. Of course, they''ll need more than SWIG from CVS, they''re still need to patch fixmodule.rb and typemaps.i to remove the references to RSTRING(obj)->ptr and RARRAY(obj)->len. I did submit typemap.i.patch along with the patch, didn''t I? Roy
Roy Sutton wrote:> I''m fine with waiting. Of course, they''ll need more than SWIG from CVS, > they''re still need to patch fixmodule.rb and typemaps.i to remove the > references to RSTRING(obj)->ptr and RARRAY(obj)->len.Cool - this should now be googleable on the m.l. archive. Let''s update our scripts to use the new macro definition once 1.3.30 swig is released.> I did submit > typemap.i.patch along with the patch, didn''t I? >I didn''t see one ;) Thanks for tracking this. alex