Skip to content
This repository has been archived by the owner on Mar 29, 2024. It is now read-only.

Pb importing tulipgui (python) #22

Closed
guywiz opened this issue Sep 11, 2017 · 2 comments
Closed

Pb importing tulipgui (python) #22

guywiz opened this issue Sep 11, 2017 · 2 comments

Comments

@guywiz
Copy link

guywiz commented Sep 11, 2017

When trying to import tulipgui I get an error. Do I need to set any env variable other than PYTHONPATH?

Thanks
Guy


Eldorado:~ melancon$ python
Python 2.7.10 (v2.7.10:15c95b7d81dc, May 23 2015, 09:33:12)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

from tulip import *
import tulipgui
Traceback (most recent call last):
File "", line 1, in
File "/Applications/Tulip-5.0.0.app/Contents/lib/python/tulipgui/init.py", line 45, in
import _tulipgui
ImportError: dlopen(/Applications/Tulip-5.0.0.app/Contents/lib/python/tulipgui/native/_tulipgui.so, 2): Library not loaded: /Users/tulip/workspace/Qt/4.8.6/lib/QtOpenGL.framework/Versions/4/QtOpenGL
Referenced from: /Applications/Tulip-5.0.0.app/Contents/lib/python/tulipgui/native/_tulipgui.so
Reason: image not found


@anlambert
Copy link
Contributor

Hi Guy,

Yes I confirmed that the tulipgui module can not be imported from the Tulip standard installation without additional setup. To fix your issue, set the following environment variables before launching python:

$ export DYLD_LIBRARY_PATH=/Applications/Tulip-5.0.0.app/Contents/Frameworks/
$ export DYLD_FRAMEWORK_PATH=/Applications/Tulip-5.0.0.app/Contents/Frameworks/

I will update the Python documentation for that special case.

Antoine

@guywiz
Copy link
Author

guywiz commented Sep 11, 2017

Great, it works indeed. Thanks so much for your help and responsivity!

p-mary referenced this issue in anlambert/talipot Jan 3, 2020
QOpenGL module is marked as deprecated since a while now so it is time
to remove its use from the Talipot codebase and promote the use of
QOpenGL* classes directly integrated in the QtGui module.

The big difference between QOpenGL and QtOpenGL from Qt5 is that all
rendering is performed in framebuffer objects, there is no more direct
rendering in the underlying os windows with its own OpenGL context.

Talipot OpenGL rendering also follows that idiom, all renderings are performed
offscreen using a shared OpenGL context. This also means that there is no
more QGLWidget as viewport for QGraphicsView. Talipot OpenGL scene are
now converted to QImage in order to display them using the default Qt raster
rendering engine. This should fixes the numerous rendering glitches observed
on MacOS.

First thing observed after the migration is a consequent performance boost
in OpenGL rendering when using an Intel GPU on a Linux host machine (especially
when selecting elements, it is now 10 times faster on debian stable).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants