With the recent check-in I accidentally committed my change to rakewx to remove the -fvirtual swig option. -fvirtual is incompatible with SWIG 1.3.30. It''s not necessary (as I recall) for 1.3.29 but only reduces the size of the wrapper code slightly. If anyone feels strongly about this I can make it conditional on the SWIG version but simply removing it seems the safest and cleanest approach. Roy
Kevin Smith wrote [privately, but for the list, darn mailman]:> I think your change makes sense. Presumably at some point we will go > with 1.3.30 (after it is widely available), so we might as well get > compatible with it now. > Is the incompatibility something in our post-processing that we will > eventually be able to fix? Or is it a fundamental change. It is always > nice to have smaller code, where possible.It''s a fundamental change to the way SWIG wraps directors. I''m actually surprised they didn''t deprecate/disable -fvirtual since it''s incompatible now. It is possible there''s a situation where it works correctly I''m unaware of. Roy
Roy Sutton wrote:> With the recent check-in I accidentally committed my change to rakewx to > remove the -fvirtual swig option.Seems like a good move to me, for the reasons you give. I just committed a change to restore swig_options as an empty string, b/c it is referenced and changed later in rakemacosx. alex
Apparently Analagous Threads
- Re: -fvirtual and compactdefaultargs (was StaticBoxSizer bug?)
- Looking for volunteers (no C++ knowledge needed!)
- building wxruby2 from cvs (gentoo)
- [967] branches/wxruby2/wxwidgets_282/rake/rakewx.rb: Fix two warnings generated by the rakefile
- Patch to rakewx.rb