PDA

View Full Version : (Linux tip!) PySide in Maya 2012x64 by using Nuke 6.3v5


Greken
11-11-2011, 09:35 AM
Hi!

This is not a question, rather a tip for people struggling with getting PySide (Nokia's Python wrapper for Qt, instead of the other alternative PyQt) to work inside Maya2012x64. This is a Linux-only tip since I don't have a Windows setup in front of me:

Since Nuke 6.3v5 PySide is now included in the install. Previously you had to compile it yourself, which can be very troublesome for Linux beginners like me.
Because Nuke and Maya are compiled with the same gcc (4.1.2) and uses the same Python (2.6.4) we can actually just copy the PySide install from Nuke to Maya. Please remember that this will only work as long as these two applications uses the same gcc and Python.

Run the following commands as sudo if you have installed the applications at their default locations:

# Copy the PySide folder
rsync -a /usr/local/Nuke6.3v5/plugins/PySide/ /usr/autodesk/maya2012-x64/lib/python2.6/site-packages/PySide/

# Copy the libpyside library
rsync -a /usr/local/Nuke6.3v5/libpyside-python2.6.so.1.0 /usr/autodesk/maya2012-x64/lib/libpyside-python2.6.so.1.0
rsync -a /usr/local/Nuke6.3v5/libpyside-python2.6.so.1.0.3 /usr/autodesk/maya2012-x64/lib/libpyside-python2.6.so.1.0.3
rsync -a /usr/local/Nuke6.3v5/libpyside-python2.6.so /usr/autodesk/maya2012-x64/lib/libpyside-python2.6.so

# Copy the libshiboken library
rsync -a /usr/local/Nuke6.3v5/libshiboken-python2.6.so /usr/autodesk/maya2012-x64/lib/libshiboken-python2.6.so
rsync -a /usr/local/Nuke6.3v5/libshiboken-python2.6.so.1.0 /usr/autodesk/maya2012-x64/lib/libshiboken-python2.6.so.1.0
rsync -a /usr/local/Nuke6.3v5/libshiboken-python2.6.so.1.0.3 /usr/autodesk/maya2012-x64/lib/libshiboken-python2.6.so.1.0.3
So far this have been working pretty good for me but as I have just started using PySide myself there might be something that I have been missing :) Will post it here in that case!

CGTalk Moderation
11-11-2011, 09:35 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.