Displaying 1 result from an estimated 1 matches for "hincludesa".
Did you mean:
hincludesas
2007 Dec 27
4
build problems, part III, and runtime problems, part I
After decoding the unresolved symbols from wxruby2.so using c++filt, and
comparing with the symbols provided by wxGTK, it became clear that wxGTK was
using wchar_t whereas wxruby2.so was using char. So I rebuilt wxGTK,
turning off unicode. That worked. No more unresolved symbols. What
gives? Should the wxruby code have been built using wchar_t, and if so,
how?
However, now I get the