Maya 2014 and Qt problems with getting it to run...very newbie

860 views
Skip to first unread message

Shannon Davis

unread,
Sep 20, 2013, 12:09:54 AM9/20/13
to python_in...@googlegroups.com
Now I see myself as fairly geeky and I take pride it in. I found just yesterday that Qt has become a part of Maya. I had put Maya on the backburner as something to play with when I get the urge. But there is so much I can do as I have been studying Qt for about 6 months and got fairly good with it.

So I have been trying every since yesterday to get Maya 2014 to work with the Qt designer inside of it. The Documentation is dodgy and after installing python 3.3.2, PyQt GPL v4.10.3 for Python v3.3(x64), sip which I had no idea of what to do with or run, set the environment path to my script file in Maya, and tried to run a simple script. I am still stuck with an error on the first line and the 4th line.

# Error:
line 1: ImportError: file <maya console> line 4: cannot import name uic #

I was getting an error for no sip module also, but I commented it out so I could tackle the two above.

So what am I not doing? Where would I be going wrong.

Is there a clear guide as to what to do to get Maya working with PyQt.

I even found out that it is packaged with PySide. So I changed it from PyQt to PySide but I am hearing PyQt is better. Somebody help please so I can get over this first little hump.

Shannon Davis

unread,
Sep 20, 2013, 2:51:11 AM9/20/13
to python_in...@googlegroups.com


&&&&&&&&&&&&&&&&&&&

I knew my geek would prevail, and I found my way over the hump after trying just about everything and nobody seeming to have an answer.

I found this....

www.geoffsamuel.com/Tutorials/Install_Maya_QT.php

Follow the directions on this site. It involves copying out of your python file and pasting the files you will need in your Python file that is inside of Maya autodesk along with the other files ie PySide and Shiboken that comes with maya. PyQt4 and sip.pyd need to be in that same file.

I know it seems basic, but everybody have to break into something sometimes and I hope this keep someone else from wasting 2 days trying to figure it out.

That link was the solution to my problem and I am going forward with my "happy coding".

Shannon Davis

unread,
Sep 20, 2013, 2:57:03 AM9/20/13
to python_in...@googlegroups.com

To add to it the link says it is for Maya 2012, but the directions work fine for 2014 too.

Justin Israel

unread,
Sep 20, 2013, 4:43:32 AM9/20/13
to python_in...@googlegroups.com
Hi Shannon,

First thing you will want to do is ditch python3. its not really of any use to you when developing for Maya, since Maya is only on python 2.x anyways. The trick with using PyQt/PySide for Maya is that it needs to be compiled against the same binary compatible version of Qt that ships with Maya. You will find, when searching, that many people have been providing pre-built installers for PyQt into Maya. I was maintaining some for OSX, and linking to others supporting Linux/Windows.

Now, with PySide shipping with Maya, it just makes sense to use that unless you have specific dependencies on PyQt or want to do the install yourself.  I have used both PyQt and Pyside, and when using PyQt with SIP API set to version 2, they are pretty much the same thing. Although I've noticed some bugs here and there with PySide, I wouldn't say PyQt is clearly any better or worse. Ultimately when you are using SIP with API 2, the only major different is the import statements, and a few naming differences (http://qt-project.org/wiki/Signals_and_Slots_in_PySide)

There is also the difference that PySide uses shiboken, while PyQt uses sip. They both accomplish the same goal when needing to access Qt pointers in Maya

All in all, I say stick with PySide since its built in and you don't even have to think twice about it :-)





--
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_m...@googlegroups.com.
To post to this group, send email to python_in...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

cloud...@gmail.com

unread,
May 25, 2014, 10:14:06 AM5/25/14
to python_in...@googlegroups.com
Hai Justin

Can You teach me how to buil PyQt with VS for maya 2014 x64 ??

i searcing the guideline but cant find the detail proses, include from autodesk.
this make me confuse a lot, thanks.

Justin Israel

unread,
May 25, 2014, 3:42:54 PM5/25/14
to python_in...@googlegroups.com

I actually don't have any experience compiling PyQt on Windows. But I am positive there are others here that work on Windows platforms and have done it.

--
You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_m...@googlegroups.com.

Marcus Ottosson

unread,
May 25, 2014, 4:46:08 PM5/25/14
to python_in...@googlegroups.com
Marcus to the rescue! :)

I've documented the process of compiling PyQt for Windows here, but as the steps for Maya are a little special, you could also pull some info from this here, which goes through how to compile something else (PyZMQ) on Windows for Maya. The steps are much the same.

In a nutshell, the differences between compiling for the vanilla Python version on Windows versus compiling for Maya on Windows is that default Python is compiled with Visual Studio 2010 whereas Maya uses a custom Python compiled in VS2012. So you must use Maya's own python, mayapy.exe for your compilation.

Best,
Marcus



For more options, visit https://groups.google.com/d/optout.



--
Marcus Ottosson
konstr...@gmail.com

Marcus Ottosson

unread,
May 25, 2014, 4:55:01 PM5/25/14
to python_in...@googlegroups.com
I just remembered, I posted a compiled version not too long ago. If you'd rather hop the compile, just grab this.
--
Marcus Ottosson
konstr...@gmail.com

Eric Siawan

unread,
May 26, 2014, 4:18:09 AM5/26/14
to python_in...@googlegroups.com
Thanks Justin and Marcus for reference and help, but still not clear for me because im newbe in programming.
Maybe I You guys have time to spend please write a detail prosess for community it will be a great recourse.

Thanks again :D


You received this message because you are subscribed to a topic in the Google Groups "Python Programming for Autodesk Maya" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/python_inside_maya/PGJvh_MRZw0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to python_inside_m...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAXHAd_%3DTa51_1B38vOk%3DMRr8-AATgrRf_u1AjmcgH5Wg%40mail.gmail.com.

Justin Israel

unread,
May 26, 2014, 4:31:50 AM5/26/14
to python_in...@googlegroups.com
Similar topic was discussed on another thread, but you might find less and less interest in supporting PyQt in Maya now that 2014 ships with PySide. I was doing PyQt builds for OSX, but I stopped after 2013. Also, compiling tends to not be for the faint of heart. But maybe if Marcus is up for the task, he can document his 2014 windows procedure. 



Marcus Ottosson

unread,
May 26, 2014, 5:47:30 AM5/26/14
to python_in...@googlegroups.com
Hi Eric,

Its difficult to know exactly how much to document, but if you could give this a try and let me know where you get stuck, that would help a lot.

Best,
Marcus



For more options, visit https://groups.google.com/d/optout.



--
Marcus Ottosson
konstr...@gmail.com

Marcus Ottosson

unread,
May 26, 2014, 5:50:58 AM5/26/14
to python_in...@googlegroups.com
About PySide, despite its inclusion in later releases of certain DCCs (like Maya) I still can't imagine it becoming any sort of standard; mainly because it hasn't been developed in many years, as opposed to PyQt which is getting updates regurlarly. The inclusion, to me, seems more like a mere "aw, lets just throw it in there" than any actual attempt at standardisation.

In that regard, I'd still go for PyQt whenever I'm given the option.
--
Marcus Ottosson
konstr...@gmail.com

Eric Siawan

unread,
May 26, 2014, 6:12:09 AM5/26/14
to python_in...@googlegroups.com

Justin Israel

unread,
May 26, 2014, 6:38:14 AM5/26/14
to python_in...@googlegroups.com

Eric Siawan

unread,
May 26, 2014, 6:40:08 AM5/26/14
to python_in...@googlegroups.com

Justin Israel

unread,
May 26, 2014, 6:50:14 AM5/26/14
to python_in...@googlegroups.com
Sorry Eric. My comment was actually for Marcus...


On Mon, May 26, 2014 at 9:50 PM, Marcus Ottosson <konstr...@gmail.com> wrote:
About PySide, despite its inclusion in later releases of certain DCCs (like Maya) I still can't imagine it becoming any sort of standard; mainly because it hasn't been developed in many years, as opposed to PyQt which is getting updates regurlarly. The inclusion, to me, seems more like a mere "aw, lets just throw it in there" than any actual attempt at standardisation.

 

In that regard, I'd still go for PyQt whenever I'm given the option.

PySide is actively developed. And I assume the licensing situation was a lot easier to deal with, in bundling LGPL libraries instead of GPL libraries
 

Marcus Ottosson

unread,
May 26, 2014, 7:03:04 AM5/26/14
to python_in...@googlegroups.com
Straying off-topic here, but I hardly consider updates to a repo as any form of development or updates; that's a keep-alive with bugfixes. Where is Qt 5?



For more options, visit https://groups.google.com/d/optout.



--
Marcus Ottosson
konstr...@gmail.com

Marcus Ottosson

unread,
May 26, 2014, 7:08:28 AM5/26/14
to python_in...@googlegroups.com

please look this guide and help to explain which point is wrong ?

I don’t think any of that is wrong, Eric. How do you mean? How about you tell me where you get stuck? Then we could possibly make some progress :)

Best,
Marcus
--
Marcus Ottosson
konstr...@gmail.com

Justin Israel

unread,
May 26, 2014, 7:14:17 AM5/26/14
to python_in...@googlegroups.com
I don't necessarily think Qt5 support is the mark of maintaining development, and it is 100% irrelevant since Maya ships with Qt4. If PySide is maintaining their Qt4 support then they are doing their job and have just as much validity for being apart of Maya's deployment as PyQt. Again, I am sure the licensing situation was easier in choosing between the two options. If Maya wanted to update their platform to Qt5, then it would be a different story, and it is possible they may have not decided to include any python Qt bindings at all.
Also, it wasn't off topic to reply to my comment. My comment was in response to your comment about the inclusion of PySide over PyQt. I didn't really follow your bit about "aw lets just throw it in there". I can't see that being the gist of how it went down in the Autodesk conference room when that decision was made. 



Eric Siawan

unread,
May 26, 2014, 7:43:43 AM5/26/14
to python_in...@googlegroups.com
Im not clear about:

*folder placement, which folder exactly:
i put PyQt-win-gpl-4.10 and sip-4.14.5 folder in(D:\__sdkext\_Maya2014 Scripts), is that right?

* i need just use VS command promt or need to open VS app it self??

*Follow the instructions from the API docs to setup your environment:
How to setup environment??

*i create Qt folder and unzip qt-4.8.2-64-include.tar.gz to thath folder, inside ->C:\Program Files\Autodesk\Maya2014\include
*i unzip qt-4.8.2-64-mkspecs.tar.gz inside ->C:\Program Files\Autodesk\Maya2014\mkspecs
this step is right??

i try to execute vcvars64.bat in VS comand promt and then try to set location( D:\__sdkext\_Maya2014 Scripts\sip-4.14.5) in comand promt and paste the code:

------------------------------------------------ @echo off
 
set MAYAQTBUILD=%~dp0
set MAYAQTBUILD=%MAYAQTBUILD:~0,-1%
if exist v:\nul subst v: /d
subst v: "%MAYAQTBUILD%"
v:
 
set SIPDIR=v:\sip-4.14.5
set MSVC_DIR=C:\Program Files (x86)\Microsoft Visual Studio 10.0
if [%LIBPATH%]==[] call "%MSVC_DIR%\VC\vcvarsall" amd64
 
set MAYA_LOCATION=C:\Program Files\Autodesk\Maya2014
set INCLUDE=%INCLUDE%;%MAYA_LOCATION%\include\python2.7;%MAYA_LOCATION%\Python\include
set LIB=%LIB%;%MAYA_LOCATION%\lib
 
cd %SIPDIR%
"%MAYA_LOCATION%\bin\mayapy" configure.py
nmake
nmake install


----------------------------------------------------------------------------
and show like this:

Setting environment for using Microsoft Visual Studio 2010 x86 tools. C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC>"C:\Program Files (x86)\M icrosoft Visual Studio 10.0\VC\bin\amd64\vcvars64.bat" Setting environment for using Microsoft Visual Studio 2010 x64 tools. C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC>d: D:\>cd __sdkext\_Maya2014 Scripts\sip-4.14.5 D:\__sdkext\_Maya2014 Scripts\sip-4.14.5>@echo off set MAYAQTBUILD=%~dp0 set MAYAQTBUILD=%MAYAQTBUILD:~0,-1% if exist v:\nul subst v: /d subst v: "%MAYAQTBUILD%" Path not found - %~dp v: The system cannot find the drive specified. set SIPDIR=v:\sip-4.14.5 set MSVC_DIR=C:\Program Files (x86)\Microsoft Visual Studio 10.0 if [%LIBPATH%]==[] call "%MSVC_DIR%\VC\vcvarsall" amd64 C:\Windows\Microsoft.NET\Framework64\v3.5 was unexpected at this time. set MAYA_LOCATION=C:\Program Files\Autodesk\Maya2014 set INCLUDE=%INCLUDE%;%MAYA_LOCATION%\include\python2.7;%MAYA_LOCATION%\Python\i nclude set LIB=%LIB%;%MAYA_LOCATION%\lib cd %SIPDIR% The system cannot find the drive specified. "%MAYA_LOCATION%\bin\mayapy" configure.py This is SIP 4.14.5 for Python 2.7.3 on win32. The SIP code generator will be installed in C:\Program Files\Autodesk\Maya2014\Python. The sip module will be installed in C:\Program Files\Autodesk\Maya2014\Python\Lib\site-packages. The sip.h header file will be installed in C:\Program Files\Autodesk\Maya2014\Python\include. The default directory to install .sip files in is C:\Program Files\Autodesk\Maya2014\Python\sip. The platform/compiler configuration is win32-msvc2008. Creating siplib\sip.h... Creating siplib\siplib.c... Creating siplib\siplib.sbf... Creating sipconfig.py... Creating top level Makefile... Creating sip code generator Makefile... Creating sip module Makefile... nmake Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. cd sipgen "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\amd64\nmake. exe" Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. cd siplib "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\amd64\nmake. exe" Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. cl -c -nologo -Zm200 -Zc:wchar_t- -O2 -MD -W0 -DNDEBUG -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -I. -I"C:\Program Files\Autodesk\Maya2014\Python\include " -Fo @C:\Users\MYCOMP~1\AppData\Local\Temp\nmD743.tmp siplib.c apiversions.c descriptors.c qtlib.c threads.c objmap.c voidptr.c Generating Code... cl -c -nologo -Zm200 -Zc:wchar_t- -O2 -MD -W0 -DNDEBUG -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -I. -I"C:\Program Files\Autodesk\Maya2014\Python\include " -Fo @C:\Users\MYCOMP~1\AppData\Local\Temp\nmDA40.tmp bool.cpp link /NOLOGO /DYNAMICBASE /NXCOMPAT /DLL /MANIFEST /MANIFESTFILE:sip.pyd .manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /OUT:sip.pyd @C:\Users\MYCOMP~1\App Data\Local\Temp\nmDA61.tmp Creating library sip.lib and object sip.exp mt -nologo -manifest sip.pyd.manifest -outputresource:sip.pyd;2 nmake install Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. cd sipgen "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\amd64\nmake. exe" install Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. copy /y sip.exe "C:\Program Files\Autodesk\Maya2014\Python\sip.exe" 1 file(s) copied. cd siplib "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\amd64\nmake. exe" install Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. copy /y sip.pyd "C:\Program Files\Autodesk\Maya2014\Python\Lib\site-pack ages\sip.pyd" 1 file(s) copied. copy /y "D:\__sdkext\_Maya2014 Scripts\sip-4.14.5\siplib\sip.h" "C:\Prog ram Files\Autodesk\Maya2014\Python\include\sip.h" 1 file(s) copied. copy /y sipconfig.py "C:\Program Files\Autodesk\Maya2014\Python\Lib\site -packages\sipconfig.py" 1 file(s) copied. copy /y "D:\__sdkext\_Maya2014 Scripts\sip-4.14.5\sipdistutils.py" "C:\P
rogram Files\Autodesk\Maya2014\Python\Lib\site-packages\sipdistutils.py"
1 file(s) copied.
--------------------------------------------------------

**some sip file success create in (C:\Program Files\Autodesk\Maya2014\Python\Lib\site-packages)
but when i try this step for build PyQt, i not get PyQt4 folder, how to make this right??

---------------------------
use this code:
@echo off
 
set MAYAQTBUILD=%~dp0
set MAYAQTBUILD=%MAYAQTBUILD:~0,-1%
if exist v:\nul subst v: /d
subst v: "%MAYAQTBUILD%"
v:
 
set MAYA_LOCATION=C:\Program Files\Autodesk\Maya2014
if exist m:\nul subst m: /d
subst m: "%MAYA_LOCATION%"
set MAYA_LOCATION=m:
 
set QTDIR=%MAYA_LOCATION%
set MSVC_VERSION=2010
set QMAKESPEC=%QTDIR%\mkspecs\win32-msvc%MSVC_VERSION%
if not exist "%QMAKESPEC%\qmake.conf" (
    echo "You need to uncompress %MAYA_LOCATION%\mkspecs\qt-4.8.2-64-mkspecs.tar.gz !"
    goto :end
)
if not exist "%MAYA_LOCATION%\include\Qt\QtCore\qdir.h" (
    echo "You need to uncompress %MAYA_LOCATION%\include\qt-4.8.2-64-include.tar.gz in %MAYA_LOCATION%\include\Qt !"
    goto :end
)
findstr /L /C:"Headers=../include/Qt" %MAYA_LOCATION%\bin\qt.conf >nul 2>&1
if ERRORLEVEL 1 (
    echo "You need to edit %MAYA_LOCATION%\bin\qt.conf to use 'Headers=../include/Qt'"
    goto :end
)
 
set SIPDIR=v:\sip-4.14.5
set PYQTDIR=v:\PyQt-win-gpl-4.10
 
set MSVC_DIR=C:\Program Files (x86)\Microsoft Visual Studio 10.0
if [%LIBPATH%]==[] call "%MSVC_DIR%\VC\vcvarsall" amd64
 
set INCLUDE=%INCLUDE%;%MAYA_LOCATION%\include\python2.7;%MAYA_LOCATION%\Python\include
set LIB=%LIB%;%MAYA_LOCATION%\lib
 
cd %PYQTDIR%
set PATH=%QTDIR%\bin;%PATH%
"%MAYA_LOCATION%\bin\mayapy" configure.py LIBDIR_QT=%QTDIR%\lib INCDIR_QT=%QTDIR%\include\Qt MOC=%QTDIR%\bin\moc.exe -w --no-designer-plugin
nmake
nmake install
 
:end
pause
----------------------------------------------------------
and show like this:
More?     goto :end
More? )
if not exist "%MAYA_LOCATION%\include\Qt\QtCore\qdir.h" (
More?     echo "You need to uncompress %MAYA_LOCATION%\include\qt-4.8.2-64-inclu
de.tar.gz in %MAYA_LOCATION%\include\Qt !"
More?     goto :end
More? )
findstr /L /C:"Headers=../include/Qt" %MAYA_LOCATION%\bin\qt.conf >nul 2>&1
if ERRORLEVEL 1 (
More?     echo "You need to edit %MAYA_LOCATION%\bin\qt.conf to use 'Headers=../
include/Qt'"
More?     goto :end
More? )

set SIPDIR=v:\sip-4.14.5
set PYQTDIR=v:\PyQt-win-gpl-4.10

set MSVC_DIR=C:\Program Files (x86)\Microsoft Visual Studio 10.0
if [%LIBPATH%]==[] call "%MSVC_DIR%\VC\vcvarsall" amd64
C:\Windows\Microsoft.NET\Framework64\v3.5 was unexpected at this time.

set INCLUDE=%INCLUDE%;%MAYA_LOCATION%\include\python2.7;%MAYA_LOCATION%\Python\i
nclude
set LIB=%LIB%;%MAYA_LOCATION%\lib

cd %PYQTDIR%
The system cannot find the drive specified.
set PATH=%QTDIR%\bin;%PATH%
"%MAYA_LOCATION%\bin\mayapy" configure.py LIBDIR_QT=%QTDIR%\lib INCDIR_QT=%QTDIR
%\include\Qt MOC=%QTDIR%\bin\moc.exe -w --no-designer-plugin
Determining the layout of your Qt installation...
m:\bin\qmake.exe -o qtdirs.mk qtdirs.pro
nmake -f qtdirs.mk release

Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation.  All rights reserved.

        "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\amd64\nmake.
exe" -f qtdirs.mk.Release

Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation.  All rights reserved.

        cl -c -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -GR -EHsc -W3 -w34100 -w341
89 -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB
 -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQ
T_THREAD_SUPPORT -I"m:\include\Qt\QtCore" -I"m:\include\Qt" -I"m:\include\Qt\Act
iveQt" -I"release" -I"m:\mkspecs\win32-msvc2010" -Forelease\ @C:\Users\MYCOMP~1\
AppData\Local\Temp\nmC826.tmp
qtdirs.cpp
        link /LIBPATH:"m:\lib" /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /D
EBUG /MANIFEST /MANIFESTFILE:"release\qtdirs.intermediate.manifest" /SUBSYSTEM:W
INDOWS "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls
' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArch
itecture='*'" /OUT:release\qtdirs.exe @C:\Users\MYCOMP~1\AppData\Local\Temp\nmCA
D6.tmp
qtmain.lib(qtmain_win.obj) : warning LNK4099: PDB 'vc100.pdb' was not found with
 'qtmain.lib(qtmain_win.obj)' or at 'D:\__sdkext\_Maya2014 Scripts\PyQt-win-gpl-
4.10\release\vc100.pdb'; linking object as if no debug info
        mt.exe -nologo -manifest "release\qtdirs.intermediate.manifest" -outputr
esource:release\qtdirs.exe;1
release\qtdirs.exe
This is the GPL version of PyQt 4.10 (licensed under the GNU General Public
License) for Python 2.7.3 on win32.

Type '2' to view the GPL v2 license.
Type '3' to view the GPL v3 license.
Type 'yes' to accept the terms of the license.
Type 'no' to decline the terms of the license.

Do you accept the terms of the license? nmake
Do you accept the terms of the license? nmake install
Do you accept the terms of the license?
Do you accept the terms of the license? :end
Do you accept the terms of the license? yes
Found the license file pyqt-gpl.sip.
Checking to see if the QtGui module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_GUI_LIB
-I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtGui -Im:\include\Q
t -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtGui.cpp -Fe /link /LIBPAT
H:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /MANIFESTFILE:
cfgtest_QtGui.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG QtGui4.lib QtCo
re4.lib gdi32.lib comdlg32.lib oleaut32.lib imm32.lib winmm.lib winspool.lib ws2
_32.lib ole32.lib user32.lib advapi32.lib kernel32.lib shell32.lib uuid.lib
cfgtest_QtGui.cpp
Checking to see if the QtHelp module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB
 -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtHelp -Im:\include
\Qt\QtCore -Im:\include\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_Qt
Help.cpp -Fe /link /LIBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:N
O /MANIFEST /MANIFESTFILE:cfgtest_QtHelp.manifest /SUBSYSTEM:CONSOLE /INCREMENTA
L:NO /DEBUG QtHelp4.lib QtSql4.lib QtGui4.lib gdi32.lib comdlg32.lib oleaut32.li
b imm32.lib winmm.lib winspool.lib ws2_32.lib ole32.lib user32.lib advapi32.lib
QtCore4.lib kernel32.lib user32.lib shell32.lib uuid.lib ole32.lib advapi32.lib
ws2_32.lib
cfgtest_QtHelp.cpp
Checking to see if the QtMultimedia module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_MULTIMED
IA_LIB -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtMultimedia
-Im:\include\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtMultimedia.
cpp -Fe /link /LIBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MA
NIFEST /MANIFESTFILE:cfgtest_QtMultimedia.manifest /SUBSYSTEM:CONSOLE /INCREMENT
AL:NO /DEBUG QtMultimedia4.lib QtGui4.lib QtCore4.lib gdi32.lib comdlg32.lib ole
aut32.lib imm32.lib winmm.lib winspool.lib ws2_32.lib ole32.lib user32.lib advap
i32.lib kernel32.lib shell32.lib uuid.lib
cfgtest_QtMultimedia.cpp
Checking to see if the QtNetwork module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_NETWORK_
LIB -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtNetwork -Im:\i
nclude\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtNetwork.cpp -Fe /
link /LIBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /M
ANIFESTFILE:cfgtest_QtNetwork.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG
 QtNetwork4.lib QtCore4.lib ws2_32.lib kernel32.lib user32.lib shell32.lib uuid.
lib ole32.lib advapi32.lib
cfgtest_QtNetwork.cpp
Checking to see if the QtDBus module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -I. -ID:\qt\4
.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtDBus -Im:\include\Qt -nologo -Z
m200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtDBus.cpp -Fe /link /LIBPATH:m:\lib /N
OLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /MANIFESTFILE:cfgtest_QtD
Bus.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG QtDBus.lib
cfgtest_QtDBus.cpp
cfgtest_QtDBus.cpp(5) : error C2653: 'QDBusConnection' : is not a class or names
pace name
cfgtest_QtDBus.cpp(5) : error C3861: 'systemBus': identifier not found
Checking to see if the QtDeclarative module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_DECLARAT
IVE_LIB -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtDeclarativ
e -Im:\include\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtDeclarati
ve.cpp -Fe /link /LIBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO
/MANIFEST /MANIFESTFILE:cfgtest_QtDeclarative.manifest /SUBSYSTEM:CONSOLE /INCRE
MENTAL:NO /DEBUG QtDeclarative4.lib QtNetwork4.lib QtGui4.lib QtCore4.lib ws2_32
.lib gdi32.lib comdlg32.lib oleaut32.lib imm32.lib winmm.lib winspool.lib ole32.
lib user32.lib advapi32.lib kernel32.lib shell32.lib uuid.lib
cfgtest_QtDeclarative.cpp
Checking to see if the QtOpenGL module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_OPENGL_L
IB -DQT_CORE_LIB -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtO
penGL -Im:\include\Qt\QtCore -Im:\include\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD
-Zi -W0 cfgtest_QtOpenGL.cpp -Fe /link /LIBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXC
OMPAT /INCREMENTAL:NO /MANIFEST /MANIFESTFILE:cfgtest_QtOpenGL.manifest /SUBSYST
EM:CONSOLE /INCREMENTAL:NO /DEBUG QtOpenGL4.lib QtGui4.lib glu32.lib opengl32.li
b gdi32.lib user32.lib comdlg32.lib oleaut32.lib imm32.lib winmm.lib winspool.li
b ws2_32.lib ole32.lib advapi32.lib QtCore4.lib kernel32.lib user32.lib shell32.
lib uuid.lib ole32.lib advapi32.lib ws2_32.lib glu32.lib opengl32.lib gdi32.lib
user32.lib
cfgtest_QtOpenGL.cpp
Checking to see if the QtScript module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_SCRIPT_L
IB -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtScript -Im:\inc
lude\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtScript.cpp -Fe /lin
k /LIBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /MANI
FESTFILE:cfgtest_QtScript.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG QtS
cript4.lib QtCore4.lib kernel32.lib user32.lib shell32.lib uuid.lib ole32.lib ad
vapi32.lib ws2_32.lib
cfgtest_QtScript.cpp
Checking to see if the QtScriptTools module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_SCRIPTTO
OLS_LIB -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtScriptTool
s -Im:\include\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtScriptToo
ls.cpp -Fe /link /LIBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO
/MANIFEST /MANIFESTFILE:cfgtest_QtScriptTools.manifest /SUBSYSTEM:CONSOLE /INCRE
MENTAL:NO /DEBUG QtScriptTools4.lib QtScript4.lib QtGui4.lib QtCore4.lib gdi32.l
ib comdlg32.lib oleaut32.lib imm32.lib winmm.lib winspool.lib ws2_32.lib ole32.l
ib user32.lib advapi32.lib kernel32.lib shell32.lib uuid.lib
cfgtest_QtScriptTools.cpp
Checking to see if the QtSql module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_SQL_LIB
-I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtSql -Im:\include\Q
t\QtGui -Im:\include\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtSql
.cpp -Fe /link /LIBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /M
ANIFEST /MANIFESTFILE:cfgtest_QtSql.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO
/DEBUG QtSql4.lib QtCore4.lib kernel32.lib user32.lib shell32.lib uuid.lib ole32
.lib advapi32.lib ws2_32.lib QtGui4.lib QtCore4.lib gdi32.lib comdlg32.lib oleau
t32.lib imm32.lib winmm.lib winspool.lib ws2_32.lib ole32.lib user32.lib advapi3
2.lib kernel32.lib shell32.lib uuid.lib
cfgtest_QtSql.cpp
Checking to see if the QtSvg module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -I. -ID:\qt\4
.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtSvg -Im:\include\Qt -nologo -Zm
200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtSvg.cpp -Fe /link /LIBPATH:m:\lib /NOL
OGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /MANIFESTFILE:cfgtest_QtSvg
.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG QtSvg4.lib QtXml4.lib QtGui4
.lib QtCore4.lib gdi32.lib comdlg32.lib oleaut32.lib imm32.lib winmm.lib winspoo
l.lib ws2_32.lib ole32.lib user32.lib advapi32.lib kernel32.lib shell32.lib uuid
.lib
cfgtest_QtSvg.cpp
Checking to see if the QtTest module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_TEST_LIB
 -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtTest -Im:\include
\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtTest.cpp -Fe /link /LIB
PATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /MANIFESTFI
LE:cfgtest_QtTest.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG QtTest4.lib
 QtGui4.lib QtCore4.lib gdi32.lib comdlg32.lib oleaut32.lib imm32.lib winmm.lib
winspool.lib ws2_32.lib ole32.lib user32.lib advapi32.lib kernel32.lib shell32.l
ib uuid.lib
cfgtest_QtTest.cpp
Checking to see if the QtWebKit module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_WEBKIT_L
IB -DQT_CORE_LIB -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtW
ebKit -Im:\include\Qt\QtCore -Im:\include\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD
-Zi -W0 cfgtest_QtWebKit.cpp -Fe /link /LIBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXC
OMPAT /INCREMENTAL:NO /MANIFEST /MANIFESTFILE:cfgtest_QtWebKit.manifest /SUBSYST
EM:CONSOLE /INCREMENTAL:NO /DEBUG QtWebKit4.lib QtNetwork4.lib QtGui4.lib ws2_32
.lib gdi32.lib comdlg32.lib oleaut32.lib imm32.lib winmm.lib winspool.lib ole32.
lib user32.lib advapi32.lib QtCore4.lib kernel32.lib user32.lib shell32.lib uuid
.lib ole32.lib advapi32.lib ws2_32.lib
cfgtest_QtWebKit.cpp
Checking to see if the QtXml module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_XML_LIB
-I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtXml -Im:\include\Q
t -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtXml.cpp -Fe /link /LIBPAT
H:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /MANIFESTFILE:
cfgtest_QtXml.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG QtXml4.lib QtCo
re4.lib kernel32.lib user32.lib shell32.lib uuid.lib ole32.lib advapi32.lib ws2_
32.lib
cfgtest_QtXml.cpp
Checking to see if the QtXmlPatterns module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_XMLPATTE
RNS_LIB -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtXmlPattern
s -Im:\include\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtXmlPatter
ns.cpp -Fe /link /LIBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO
/MANIFEST /MANIFESTFILE:cfgtest_QtXmlPatterns.manifest /SUBSYSTEM:CONSOLE /INCRE
MENTAL:NO /DEBUG QtXmlPatterns4.lib QtNetwork4.lib QtCore4.lib ws2_32.lib kernel
32.lib user32.lib shell32.lib uuid.lib ole32.lib advapi32.lib
cfgtest_QtXmlPatterns.cpp
Checking to see if the phonon module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_PHONON_L
IB -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\phonon -Im:\inclu
de\Qt -nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_phonon.cpp -Fe /link /L
IBPATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /MANIFEST
FILE:cfgtest_phonon.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG phonon4.l
ib QtGui4.lib QtCore4.lib gdi32.lib comdlg32.lib oleaut32.lib imm32.lib winmm.li
b winspool.lib ws2_32.lib ole32.lib user32.lib advapi32.lib kernel32.lib shell32
.lib uuid.lib
cfgtest_phonon.cpp
Checking to see if the QtAssistant module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -DQT_CORE_LIB
 -I. -ID:\qt\4.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtAssistant -Im:\in
clude\Qt\QtCore -Im:\include\Qt\QtGui -Im:\include\Qt\QtNetwork -Im:\include\Qt
-nologo -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtAssistant.cpp -Fe /link /LI
BPATH:m:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /MANIFESTF
ILE:cfgtest_QtAssistant.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG QtAss
istantClient4.lib QtCore4.lib kernel32.lib user32.lib shell32.lib uuid.lib ole32
.lib advapi32.lib ws2_32.lib QtGui4.lib gdi32.lib comdlg32.lib oleaut32.lib imm3
2.lib winmm.lib winspool.lib ws2_32.lib ole32.lib user32.lib advapi32.lib QtNetw
ork4.lib ws2_32.lib
cfgtest_QtAssistant.cpp
cfgtest_QtAssistant.cpp(1) : fatal error C1083: Cannot open include file: 'qassi
stantclient.h': No such file or directory
Checking to see if the QtDesigner module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -I. -ID:\qt\4
.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\QtDesigner -Im:\include\Qt -nolog
o -Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QtDesigner.cpp -Fe /link /LIBPATH:m
:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /MANIFESTFILE:cfg
test_QtDesigner.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG QtDesigner4.l
ib QtGui4.lib QtCore4.lib gdi32.lib comdlg32.lib oleaut32.lib imm32.lib winmm.li
b winspool.lib ws2_32.lib ole32.lib user32.lib advapi32.lib kernel32.lib shell32
.lib uuid.lib
cfgtest_QtDesigner.cpp
Checking to see if the QAxContainer module should be built...
cl -DUNICODE -DWIN32 -DQT_LARGEFILE_SUPPORT -DQT_DLL -DQT_NO_DEBUG -I. -ID:\qt\4
.8.2-64\mkspecs\win32-msvc2008 -Im:\include\Qt\ActiveQt -Im:\include\Qt -nologo
-Zm200 -Zc:wchar_t -O2 -MD -Zi -W0 cfgtest_QAxContainer.cpp -Fe /link /LIBPATH:m
:\lib /NOLOGO /DYNAMICBASE /NXCOMPAT /INCREMENTAL:NO /MANIFEST /MANIFESTFILE:cfg
test_QAxContainer.manifest /SUBSYSTEM:CONSOLE /INCREMENTAL:NO /DEBUG QAxContaine
r.lib QtGui4.lib QtCore4.lib gdi32.lib comdlg32.lib oleaut32.lib imm32.lib winmm
.lib winspool.lib ws2_32.lib ole32.lib user32.lib advapi32.lib kernel32.lib shel
l32.lib uuid.lib
cfgtest_QAxContainer.cpp
LINK : fatal error LNK1181: cannot open input file 'QAxContainer.lib'
Qt v4.8.2 free edition is being used.
SIP 4.14.5 is being used.
The Qt header files are in D:\qt\4.8.2-64\include.
The shared Qt libraries are in D:\qt\4.8.2-64\lib.
The Qt binaries are in D:\qt\4.8.2-64\bin.
The Qt mkspecs directory is in D:\qt\4.8.2-64.
These PyQt modules will be built: QtCore, QtGui, QtHelp, QtMultimedia,
QtNetwork, QtDeclarative, QtOpenGL, QtScript, QtScriptTools, QtSql, QtSvg,
QtTest, QtWebKit, QtXml, QtXmlPatterns, phonon, QtDesigner.
The PyQt Python package will be installed in C:\Program
Files\Autodesk\Maya2014\Python\Lib\site-packages.
PyQt is being built with deprecated Qt v4 features.
PyQt is being built with generated docstrings.
The PyQt .sip files will be installed in C:\Program
Files\Autodesk\Maya2014\Python\sip\PyQt4.
pyuic4, pyrcc4 and pylupdate4 will be installed in C:\Program
Files\Autodesk\Maya2014\Python.
Embedding sip flags...
Generating the C++ source for the QtCore module...
"C:\Program Files\Autodesk\Maya2014\Python\sip" -w -o -x VendorID -t WS_WIN -x P
yQt_NoPrintRangeBug -t Qt_4_8_0 -x Py_v3 -g -a QtCore.api -c D:\__sdkext\_Maya20
14 Scripts\PyQt-win-gpl-4.10\QtCore -b QtCore\QtCore.sbf -I D:\__sdkext\_Maya201
4 Scripts\PyQt-win-gpl-4.10\sip D:\__sdkext\_Maya2014 Scripts\PyQt-win-gpl-4.10/
sip/QtCore/QtCoremod.sip
sip: Usage: sip [-h] [-V] [-a file] [-b file] [-c dir] [-d file] [-e] [-g] [-I d
ir] [-j #] [-k] [-m file] [-o] [-p module] [-P] [-r] [-s suffix] [-t tag] [-T] [
-w] [-x feature] [-X id:file] [-z file] [file]
Error: Unable to create the C++ code.



Thanks justin and Marcus


Marcus Ottosson

unread,
May 26, 2014, 7:47:18 AM5/26/14
to python_in...@googlegroups.com

I’m not really referring to it being in Maya or not, but to it becoming the standard.

As the question in this thread was about compiling it for Maya, to which you suggested PySide instead, I felt it necessary to point out that PyQt is an equally valid option and not something to dismiss simply because Autodesk has chosen to bundle PySide with Maya.

At the end of the day, we’re talking about basing our development on something that has a clear future versus something that may splutter and die any second.

I can’t see that being the gist of how it went down in the Autodesk conference room when that decision was made.

I actually can. :)

Also, it wasn’t off topic to reply to my comment

This whole discussion is off-topic no? This thread is about getting PyQt to work with Maya, PySide isn’t even relevant here.




For more options, visit https://groups.google.com/d/optout.



--
Marcus Ottosson
konstr...@gmail.com

Message has been deleted

Eric Siawan

unread,
May 26, 2014, 9:18:04 AM5/26/14
to python_in...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages