Re: build problems, part III, and runtime problems, part I

Robert Anderson wrote:
>
> Somehow my build is configured otherwise.  I don't
understand the 
> mechanisms for how this is configure, so I don't know
how it got out 
> of whack.

wxRuby doesn't even try to configure this; it simply depends
on there 
being a unicode not ANSI build. I am wondering whether SWIG
is the issue 
here...
>
> Here's the evidence:
>
> nm obj/App.o | grep wxStringBase8InitWithEPK | c++filt
>          U wxStringBase::InitWith(char const*, unsigned
int, unsigned int)
>
> whereas I would assume a unicode build would be using
wchar_t instead 
> of char.
>  
>
So would I; here's what my build (OS X) says:

Abaddon:wxruby2 alex$ nm obj/App.o | grep
wxStringBase8InitWithEPK | c++filt
         U wxStringBase::InitWith(wchar_t const*, unsigned
long, 
unsigned long)
>
>
> http://rubyforge.org/pipermail/wxruby-users
/2007-December/003497.html
Thanks. Will follow this up.


>
>  % swig -version
>
> SWIG Version 1.3.33
>
> Should I downgrade?

Yes, definitely, to 1.3.31 please. SWIG versions are
notoriously 
incompatible even between minor versions, and wxRuby
hincludesas 
numerous hacks to work around SWIG bugs.

Then you should be able to do
rake reswig && rake

If this improves things I will update the wiki to make it
clearer that 
there is the specific version dependency

Thanks
alex

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