compas-dev/compas_occ

can't run compas_viewer2 due to competing Qt wrappers

jf--- opened this issue · 1 comments

jf--- commented

Could not use the compas_view2 viewer ( on osx, 10.15.7 )

  • currently, both pyside2 and pyqt5 are installed, AFAIK mixing & matching these is not advisable...
/Users/jelleferinga/miniconda3/envs/occ/bin/python /Users/jelleferinga/Code/CADCAM/compas_occ/scripts/compas_to_occ_tubmesh5.py
200
171
684
342
objc[22399]: Class QMacAutoReleasePoolTracker is implemented in both /Users/jelleferinga/miniconda3/envs/occ/lib/python3.8/site-packages/PySide2/Qt/lib/QtCore.framework/Versions/5/QtCore (0x15ba5a198) and /Users/jelleferinga/miniconda3/envs/occ/lib/libQt5Core.5.12.9.dylib (0x16081c528). One of the two will be used. Which one is undefined.
objc[22399]: Class QT_ROOT_LEVEL_POOL__THESE_OBJECTS_WILL_BE_RELEASED_WHEN_QAPP_GOES_OUT_OF_SCOPE is implemented in both /Users/jelleferinga/miniconda3/envs/occ/lib/python3.8/site-packages/PySide2/Qt/lib/QtCore.framework/Versions/5/QtCore (0x15ba5a210) and /Users/jelleferinga/miniconda3/envs/occ/lib/libQt5Core.5.12.9.dylib (0x16081c5a0). One of the two will be used. Which one is undefined.
objc[22399]: Class KeyValueObserver is implemented in both /Users/jelleferinga/miniconda3/envs/occ/lib/python3.8/site-packages/PySide2/Qt/lib/QtCore.framework/Versions/5/QtCore (0x15ba5a238) and /Users/jelleferinga/miniconda3/envs/occ/lib/libQt5Core.5.12.9.dylib (0x16081c5c8). One of the two will be used. Which one is undefined.
objc[22399]: Class RunLoopModeTracker is implemented in both /Users/jelleferinga/miniconda3/envs/occ/lib/python3.8/site-packages/PySide2/Qt/lib/QtCore.framework/Versions/5/QtCore (0x15ba5a288) and /Users/jelleferinga/miniconda3/envs/occ/lib/libQt5Core.5.12.9.dylib (0x16081c618). One of the two will be used. Which one is undefined.
QObject::moveToThread: Current thread (0x7fa1536629c0) is not the object's thread (0x7fa153696eb0).
Cannot move to target thread (0x7fa1536629c0)

You might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
qt.qpa.plugin: Could not load the Qt platform plugin "cocoa" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: cocoa, minimal, offscreen, webgl.


Process finished with exit code 134 (interrupted by signal 6: SIGABRT)
tomvanmele commented

this should all be fixed with the conda package.

the recipe has been merged since yesterday but they seem to have been experiencing some problems and the feedstocks are backed up. should be available later today or tomorrow...

  • 👍1