Pip install PySide does not validate QtCore Framework (OS X)

Question

Error

When I run pip install PySide - whether in a virtual environment or not - the build fails with the following error:

 ... [lots of build info, including a few warnings but no errors, for shiboken] Linking CXX executable shiboken ld: framework not found QtCore clang: error: linker command failed with exit code 1 (use -v to see invocation) 

Having seen that QtCore is installed and the framework is present (see below), I am not sure why this should be.

Setup Information

Software version

• OS X 10.8.2
• Qt 4.8.4 from a developer distributed binaries
• Python 3.3 installed and working fine
• Xcode 4.6
• Apple LLVM version 4.2 (clang-425.0.24) (based on LLVM 3.2svn) Target: x86_64-apple-darwin12.2.1
• Creating a virtual environment with pyvenv (with and without --no-site-packages )

Another configuration done

• Python 2.7 installed and working fine
• Virtual environment generated by mkvirtualenv (with and without --no-site-packages )
  • virtualenv 1.8.4
  • mkvirtualenv 3.6

system configuration

I confirmed that QtCore is actually installed correctly: ls /Library/Frameworks shows a number of frames, including QtCore.Framework .

/Library/Frameworks/QtCore.framework and /Library/Frameworks/QtCore.Framework/Versions/4 are currently included in my path, the first of which has a symbolic link to the component in the last place. I even tried it with /Library/Frameworks , although for obvious reasons I did not expect this to help, and it is not.

Other notes

I tried the same with easy_install and attempted from the Git repository and built manually using setup.py . As expected, they all return the same results.

Things I've already read

• PyPi Walkthrough Installation
• Communication error: QtCore.framework / Versions / 4 / QtCore for the x86_64 architecture (stack overflow) - but it looks like the linker is already requesting a framework based on the error message I get.
• Mac OS X: attempt to bind (ld) to the framework (stack overflow) - general information about binding to the Framework; again, I seem to have embraced it.
• The confusion of installing OSX for 2.8.10 (the CMake mailing list) seems like a very similar error, but I don't have direct control of the -isysroot flag using pip (or easy_install or even python setup.py ) for one and the other, the installation structure, by seems to have changed significantly between OS X 10.6 and 10.8. For example, /Developer no longer has the SDKs directory in it.
• CMake 0013765 error report - this one looks exactly the same, but it seems to have been fixed, so I'm not sure why it will still cause me a problem.

Settings

I currently do not use a package manager such as Homebrew or MacPorts, and I would prefer not to, as I need to get as close as possible to the installation procedure on an agnostic platform for this (we, I'm looking at cross-platform development , eventually I will be guided by Windows applications, but I have to make sure that it works on my Mac development machine outside the virtual machine).

It should be able to work with customizing the Python 3 virtual environment ( pyvenv ) as our preferred tool to highlight our specific requirements.