Re: Re: problems building strings
"Roger Binns" <[email protected]>
| Newsgroups | gmane.comp.mobile.bitpim.devel |
|---|---|
| Message-ID | <001601c50ca8$d08bf780$3501a8c0@rogersqyvr14d3> |
>> You don't build it that way. Just use >> python setup.py build --compiler=mingw32 > > I did it that way first, same error. > (undefined reference to `_imp__PyString_Type') That is because you don't have the import libraries. Go into the native/usb directory and run build.bat. It first builds the import libraries for Python 2.3 and then tries to build the USB stuff. Don't worry about the USb stuff not building (it is almost totally worthless on Windws anyway). > I know with Perl it's very difficult to build compiled modules on > windows without an old Microsoft compiler. I'm glad python works better. The issue isn't the compiler as such, but which C/runtime library it links to. The Windows dynamic linking mechanism is different than other platforms. Additionally all the compilers and linkers use a different format for how libraries and how those libraries specify symbols that are in DLLs. Getting all that right isn't a big deal (MinGW does it), but the actual documentation is scattered all over the place. Roger ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl