Well, I'm down to two libraries left to build as debug versions against
python15_d.lib, wxPython and Stackless. I've compiled a debug version of
wxWindows, and am trying to follow the instructions in build.txt for
wxPython. However, when I get to wxbuild -b, I get a few hundred messages
like this:
wx22_1d.lib(wx22_1d.dll) : error LNK2005: "public: __thiscall
wxInitDialogEvent:
:wxInitDialogEvent(int)" (??0wxInitDialogEvent@@QAE@H@Z) already defined in
dumm
y.obj
wx22_1d.lib(wx22_1d.dll) : error LNK2005: "public: virtual __thiscall
wxInitDial
ogEvent::~wxInitDialogEvent(void)" (??1wxInitDialogEvent@@UAE@XZ) already
define
d in dummy.obj
Then lots of unresolved symbol messages:
dummy.obj : error LNK2001: unresolved external symbol "public: static class
wxCl
assInfo wxTextValidator::sm_classwxTextValidator"
(?sm_classwxTextValidator@wxT
extValidator@@2VwxClassInfo@@A)
wxc.pyd : fatal error LNK1120: 153 unresolved externals
NMAKE : fatal error U1077: 'link' : return code '0x460'
Stop.
My entire build.local file is:
PYTHONLIB = "d:\\bin\\lang\\python\\libs\\python15_d.lib"
Which I added since the build script was complaining about not being able to
find python15_d.lib . (The above errors were still there without this file,
there was just an extra error regarding the unlocatable lib file).
I notice that the make files have a rule "dbg" which seems to call an
unincluded batch file. Not sure if that's an oversight or a deliberate
attempt to keep shotguns out of the hands of kiddies :o) . I don't see any
obvious reasons for the errors in a search of MSDN for LNK2001 errors, but
then I'm a C++ newbie, so I could be staring at it and not realise it.
Suggestions appreciated,
Mike
ยทยทยท
__________________________________
Mike C. Fletcher
Designer, VR Plumber
http://members.home.com/mcfletch
_______________________________________________
wxPython-users mailing list
wxPython-users@lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/wxpython-users