[egenix-users] Anyone successfully compiled mxTextTools beta5 with MingW32?

[Mike C. Fletcher]

I've been poking at this problem for a while now, basically, my attempts 
always fail with this error:

c:\bin\cygwin\bin\gcc.exe -mno-cygwin -mdll -static -s 
build\temp.win32-2.2\Release\mx\TextTools\mxTextTools\mxTextTools\mxtexttools.o 
build\temp.win32-2.2\Release\mx\TextTools\mxTextTools\mxTextTools\mxte.o 
build\temp.win32-2.2\Release\mx\TextTools\mxTextTools\mxTextTools\mxbmse.o 
build\temp.win32-2.2\Release\mx\TextTools\mxTextTools\mxTextTools\mxTextTools.def 
-LC:\bin\lang\py22\libs -L/lib -lpython22 -o 
build\lib.win32-2.2\mx\TextTools\mxTextTools\mxTextTools.pyd
build\temp.win32-2.2\Release\mx\TextTools\mxTextTools\mxTextTools\mxte.o(.text+0x1b74):mxte.c: 
undefined reference to `_imp__mxTagTable_Type'
build\temp.win32-2.2\Release\mx\TextTools\mxTextTools\mxTextTools\mxte.o(.text+0x1bf0):mxte.c: 
undefined reference to `_imp__mxTagTable_Type'
build\temp.win32-2.2\Release\mx\TextTools\mxTextTools\mxTextTools\mxte.o(.text+0x2fb4):mxte.c: 
undefined reference to `_imp__mxTagTable_Type'
build\temp.win32-2.2\Release\mx\TextTools\mxTextTools\mxTextTools\mxte.o(.text+0x3030):mxte.c: 
undefined reference to `_imp__mxTagTable_Type'
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1

Which, is just about what VC++6 also complains about as well:
    Creating library 
build\temp.win32-2.2\Release\mx\TextTools\mxTextTools\mxTextTools\mxTextTools.lib 
and object 
build\temp.win32-2.2\Release\mx\TextTools\mxTextTools\mxTextTools\mxTextTools.exp
LINK : warning LNK4049: locally defined symbol "_mxTagTable_Type" imported


Now, if I understand this problem correctly, the __declspec( dllexport ) 
stuff that's defined in mxTextTools.h and mxh.h for mxTagTable_Type is 
somehow making mxTagTable_Type wind up mangled as if it were a 
dll-loaded function within mxte.c instead of a locally-defined but 
exported one?  VC++ seems able to work about it, but not MingW32.

I'm not really a C/C++ guy, so I'm not sure what the _solution_ to the 
problem would be.  All discussions I can find on the web about it seem 
to assume it's such an obvious fix that there's no point describing it :o/ .

Any suggestions welcome,
Mike
_______________________________________
   Mike C. Fletcher
   Designer, VR Plumber, Coder
   http://members.rogers.com/mcfletch/