Holy *?!%. Thanks all. It finally works.
For any future extension builders, you must pass the compiler switch
SWIG_TYPE_TABLE=_wxPython_table to the wrapper code generated by swig
1.3.24(with patches) in addition to the command line options(-c++ -python
-Wall -nodefault -keyword -new_repr -modern -DwxMSW -DwxUSE_UNICODE **last
two are my setup**) passed to swig.exe when generating the _wrap.cpp and .py
files themselves.
Thanks again for everyone's help. You've been great.
Mike
···
-----Original Message-----
From: Ricardo Pedroso [mailto:ricardo.pedroso@netvisao.pt]
Sent: Thursday, September 29, 2005 5:20 PM
To: wxPython-users@lists.wxwidgets.org
Subject: RE: [wxPython-users] Problem with wxPython extension
On Thu, 2005-09-29 at 15:43 -0400, Mike Heanssgen wrote:
Thanks Nitro, you're been a great help so far. Unfortunately you're
suggestion didn't work. I can't believe that creating an extension would
be
so difficult, or, maybe I am just not getting the gist of it.
I didn't follow this thread so my question may not be pertinent, but
here they are.
Are you passing the -DSWIG_TYPE_TABLE=_wxPython_table switch to the
compiler when compiling the source code generated by swig?
Have you build swig with the Robin Dunn patches?
Ricardo
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org