On Wednesday 11 January 2012 03:25:10 strattonbrazil wrote:
> I've been trying to follow this to see if I can launch my qt app from
> python using pyside.
> 
> http://lynxline.com/superhybrids-part-2-now-qt-pyside/
> 
> I think I have the general idea of how everything works, but after
> creation of my shared libraries, I can't import it in python without
> getting an import error.
> 
> libsunshine.so -> libsunshine.so.1.0.0
> libSunshine.so -> libSunshine.so.1.0.0
> libsunshine.so.1 -> libsunshine.so.1.0.0
> libSunshine.so.1 -> libSunshine.so.1.0.0
> libsunshine.so.1.0 -> libsunshine.so.1.0.0
> libSunshine.so.1.0 -> libSunshine.so.1.0.0
> libsunshine.so.1.0.0
> libSunshine.so.1.0.0
> Sunshine.so -> libSunshine.so

What's the output of: 

ldd -r Sunshine.so

?
 
> This happens importing Sunshine, libsunshine, or libSunshine.  Looking
> at the generated sunshine_module_wrapper.cpp file, I see m_name listed
> as "sunshine".  From another thread related to this topic, I
> understand this import error could be caused by a mismatch between
> the .so file name and the module name.  I tried renaming my module to
> libSunshine as the OP seemed to have success doing, but still get the
> import errors using that module name.  There are several things I
> don't understand like the difference between libsunshine.so and
> libSunshine.so, which have noticeably different sizes.  Is name
> mismatch the cause of the import error or is this something else?
> 
> I have my latest code up on github if it helps.  Thanks.
> 
> https://github.com/strattonbrazil/Sunshine/tree/dev_pyside_test
> _______________________________________________
> PySide mailing list
> PySide@lists.pyside.org
> http://lists.pyside.org/listinfo/pyside

-- 
Hugo Parente Lima
INdT - Instituto Nokia de Tecnologia

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
PySide mailing list
PySide@lists.pyside.org
http://lists.pyside.org/listinfo/pyside

Reply via email to