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

[Mike C. Fletcher]

The package does compile w/out problem for the _Cygwin port of Python_, 
but what I'm trying to do is to compile it with the Mingw32 extensions 
to GCC so that the resulting binaries can be used with the "regular" 
ActiveState/PythonLabs distributions (compiled with VC++).

I've asked Steve to confirm whether he's got the Mingw32 or the Cygwin 
version working, but given my tests here, I'm assuming he was working on 
the pure-Cygwin version, not the Mingw32 version (or that I'm missing 
something about something :) ).

Oh, it's the latest beta-5, no alterations, just unzipping and running 
setup.py

Have fun all,
Mike

M.-A. Lemburg wrote:
> Mike C. Fletcher wrote:
> 
>> 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 
...
>> undefined reference to `_imp__mxTagTable_Type'
>> collect2: ld returned 1 exit status
>> error: command 'gcc' failed with exit status 1
...
> Is this the latest beta you are testing here ?
> 
> http://lists.egenix.com/mailman-archives/egenix-users/2002-August/000078.html 
> 
> 
> It should be compatible to CYGWIN since Steve Holden has done a lot
> of testing on that platform.
> 
>> 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
...