Re: [Playerstage-users] Problem using python bindings on gumstix

[Geoffrey B. <gb...@ki...>]

An error like that (Python being unable to resolve a fundamental Python 
symbol like ErrorPrint between the importee and the interpreter) is 
generally a sign that the C library containing the Player Python 
bindings has been compiled against a different version of Python than 
the interpreter you're trying to import them with. Probably because 
you're cross compiling, I guess. You'll need to figure out how to build 
the Python bindings using the correct Python toolchain for your target 
platform.

Geoff

Chad George wrote:
> I'm trying to get the python client bindings working on a gumstix platform.
> I've managed to cross compile player-2.0.4 with shared libraries.
> 
> I couldn't get the buildroot system to automatically build the python
> bindings so I made them by hand using SWIG and the provided playerc.i
> (after using parse.py to make playerc_oo.i)
> 
> I've actually managed to get everything to compile, but when I
> transfer the _playerc.so and playerc.py to my target platform, I get
> the following error.
> 
>>>> import playerc
> python: can't resolve symbol 'ErrorPrint'
> 
> Initially I was linking _playerc.so with libjpeg, libplayerc,
> libplayerxdr, libplayerjpeg, and libplayererror, which was what it
> looked like setup.py was doing.
> 
> After getting this error I added all the remaining libraries that the
> original player build made (libplayercore, libplayerc++, libplayertcp,
> libplayerdrivers) just to see if I could get it to work...and it
> didn't so does anyone have any idea on where I should look next?
> 
> I'd greatly appreciate any help on this, or suggestions if there is a
> better way to do get python bindings to the player client on the
> gumstix.
> 
> Thanks,
> Chad

-- 
Robotics research group, University of Auckland
http://www.ece.auckland.ac.nz/~gbig005/