Jake Skinner wrote:
Hello,
I'm trying to compile the wxPython src. I have the wxPython-src-2.6.0.0
tar ball. I have 4NT installed so that I could use the supplied build
scripts.command line was '.make debug'
below is the last few lines
link /DLL /NOLOGO /OUT:..\..\lib\vc_dll\wxmsw26d_vc.dll /INCREMENTAL:NO
/DEBUG /LIBPATH:..\..\lib\vc_dll @C:\DOCUME~1\Jake\LOCALS~1\Temp\nmg01556.
Creating library ..\..\lib\vc_dll\wxmsw26d.lib and object
..\..\lib\vc_dll\wxmsw26d.exp
monodll_object.obj : error LNK2001: unresolved external symbol "void *
__cdecl wxDebugAlloc(unsigned int,char *,int,bool,bool)"
(?wxDebugAlloc@@YAPAXIPADH_N1@Z)
monodll_object.obj : error LNK2001: unresolved external symbol "void
__cdecl wxDebugFree(void *,bool)" (?wxDebugFree@@YAXPAX_N@Z)
..\..\lib\vc_dll\wxmsw26d_vc.dll : fatal error LNK1120: 2 unresolved
externals
NMAKE : fatal error U1077: 'link' : return code '0x460'I believe that this is due to wxUSE_GLOBAL_MEMORY_OPERATORS being set,
however in setup.h it is set to 0 - this is the default I believe.
Double check in %WXWIN%\lib\vc_dll\mswd\wx\setup.h as that is the actual setup.h that will be used for this build. Also look at the settings of wxUSE_DEBUG_CONTEXT and wxUSE_MEMORY_TRACING. Finally, make sure that you do a complete clean before rebuilding to ensure that there are no object files left over from a prior build with different settings.
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!