On Sun, May 17, 2009 at 9:07 AM, Christopher Arndt <chris.ar...@web.de>wrote:
> René Dudfield schrieb: > > On Sun, May 17, 2009 at 2:36 AM, Christopher Arndt <chris.ar...@web.de > > <mailto:chris.ar...@web.de>> wrote: > > > > > > > We also have some scripts for building portmidi on windows linking > to > > > the correct C libraries for different python versions (2.4,2.5, > > 2.6,3). > > > > That's the work I was trying to avoid by going the ctypes route. > > > > > > I guess you could grab the portmidi dlls from the pygame builds for > > windows. For python2.4, and python2.5 you need to build against > > msvcrt71 and for python2.6/python3.x you need to build against msvcrt90 > > So are you saying, that even when I load the portmidi.dll (not the > pyportmidi module) through ctypes, it has to be compiled against the > same C library as the Python version I'm using? > yeah. it's possible it will work ok, or mostly work ok without doing that... but it can lead to weird crashes. Mixing C libraries is not a good idea mostly. > > That would mean that even a pure Python, ctypes-based portmidi module > would in practice only be compatible with the selection of Python > versions for which the portmidi dll it uses was compiled? That's > annoying... > > > Regards, Chris >
_______________________________________________ media_api mailing list media_api@create.ucsb.edu http://lists.create.ucsb.edu/mailman/listinfo/media_api
