Python interpreter does not find compiled libraries about slicer-liver HOT 8 CLOSED

I compiled Slicer with the new Python 3.9, and looks like the bug is gone. The extension is loaded without Python complaining at all, as you can see in blank Python terminal of the attached image.

Slicer was compiled as a release version, as well as the Slicer-liver extension. I got a lot of issues trying to compile the debug version of Slicer on Windows 10.

from slicer-liver.

@jpdefrutosSINTEF is this related (https://discourse.slicer.org/t/python-message-failed-to-import-pythonqt-qslicerxxxxmodulewidgets/21575/3?. If so, please make sure that you reply to that post in discourse to add that we are experiencing similar issues (give me a mention in discourse so I have it referenced and can discuss with the developers tomorrow)

@olevs

from slicer-liver.

Could you guys open an issue on the official Slicer repo? I think not having Debug is workable, but you might need it further down the road.

from slicer-liver.

@ALive-research/alive-software Should we close this one?

from slicer-liver.

Information needed @olevs, @jpdefrutosSINTEF :

• PYTHONPATH

• LD_LIBRARY_PATH (Linux only)

• Compnent that works on load

• Component that it does not work.

• Testing another extension @jpdefrutosSINTEF

from slicer-liver.

Same for me on macOS Javier. A lot of issues in the super build when trying to build Slicer in Debug mode (stops in ITK). Release mode works ok though.

from slicer-liver.

Exactly, ITK is the package failing while compiling the debug version... sus

from slicer-liver.

Quick update: Slicer compiles fine in Debug mode, as well as Slicer-Liver. Though there is an error when creating the resection plane. I will add the information in another issue, to not glut this thread

from slicer-liver.