Hey Mark, Thanks for confirming that I’m not living in some crazy parallel universe here.
I think it’s important to note that running ldd from a terminal won’t necessarily give you accurate results, as the loader is not running in the context of the Nuke application. Nuke is most likely compiled with an rpath pointing to its executable’s directory, so ld will look there first when invoked from within the Nuke application. I have confirmed this by running Nuke (unthreaded) with $LD_DEBUG set to 'libs' and dumping stderr to a text file. In it, I can see that the Qt libs are being loaded from Nuke’s installation directory (/usr/local/Nuke6.3v7 in my case), not from the /usr/lib64. In the case of libQtDesigner, it first checks the Nuke install directory and, after failing to locate the library, falls through to the ld cache and /usr/lib64. I’ve put in a support request for this (to include libQtDesigner and libQtScript in the Nuke distribution). Since both libraries are, I believe, part of a standard Qt build, they may have been omitted to try and keep the distribution size of Nuke as small as possible. However, given that QUiLoader becomes all but necessary for UI-heavy PySide development, this seems to be a pretty critical omission. I’ll follow up with results from support. -Nathan From: Mark Boorer Sent: Monday, May 21, 2012 8:45 PM To: [email protected] Subject: Re: [Nuke-python] PySide: Issue with QtUiTools (Linux + OSX) Hey Nathan, Running nuke 6.3v7 here on Centos 5 linux. ldd reports that plugins/PySide/QtUiTools.so is linking against our local /usr/lib64/qt4 install for libQtCore.so.4 libQtGui.so.4 libQtDesigner.so.4 Those libraries are provided by the rpm qt4-4.2.1-1 installed via the base centos 5 repository. This seems to work fine. On our testing Centos 6 version, I run across undefined symbol erros where QtScript.so tries to link against /usr/lib64/libQtScript.so.4, which is provided by the rpm qt-4.6.2-20 So I'll no doubt have to compile a version of Qt and append it to the LD_LIBRARY_PATH for nuke (unless the developers add the required libraries) Hope that sheds some light. -Mark On 05/22/2012 08:35 AM, Nathan Rusch wrote: Also, this issue doesn’t seem to be present on Windows, so... is everyone just using Windows now? From: Nathan Rusch Sent: Monday, May 21, 2012 3:31 PM To: Nuke-Python Subject: [Nuke-python] PySide: Issue with QtUiTools (Linux + OSX) Hey everyone, Looking for a bit of a sanity check here. I’m in the process of converting some PyQt tools to PySide, and I’m running into a big issue with the QtUiTools module (while trying to make use of the QUiLoader). Namely, one of its dependencies (libQtDesigner.so) is just straight-up missing from the Nuke Qt distribution, so when ld tries to find it, it ends up picking up a (different, incompatible) version of it from /usr/lib64 or OSX’s Frameworks path. I did a quick scan of the list archives and noticed people seem to be using the QUiLoader in their own code, so I’m curious why no one else has run into this yet. Does everyone else just happen to have a system install of Qt 4.6 and not something older or newer? Am I missing something really obvious here? Thanks, -Nathan ------------------------------------------------------------------------------ _______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python -- This message was scanned by Fuel's spambox and is believed to be clean. Click here to report this message as spam. -------------------------------------------------------------------------------- _______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
