Build scripts should support creating Debug versions of the PySide wrappers.

Debug version is needed for those developers that often run debug builds of the python interpreter and have some utilities written in PySide.

I have made this work for myself on my machine and for the company I work for. But it would be swell if this was actually supported.

I had to make numerous changes to the build scripts so that they correctly created the debug binaries for the python wrappers on windows.
I added CMAKE properties so that the binaries were created with the correct _d postfix that the debug python interpreter expects to see.
Point it to the correct python library to link against and make sure that the cmake scripts used the correct libraries when setting the build target to debug.

It would also be swell if the post build step would collect the .pdb and correct binaries from Qt when running the debug build. It always fetches the Qt release binaries as is.

A way to set the target to release, debug or relwithdebuginfo would be awesome. Where the debug and relwithdebuginfo would copy the .pdb files also.

Another note is when building the debug version of the libraries to not use the debug version of the Generatorrunner because when it is run under debug the build will be exponentially slower.

I also noticed this on the previous bug site:
http://bugs.pyside.org/show_bug.cgi?id=538#c8

The debug versions of the python interpreter are found by compiling the python library. The source gives you some build scripts that you can use to create the needed development versions. They don´t distribute binary packages of the debug library because those are only used by developers and developers should be able to compile the source. The qt-win-opensource-4.7.4-vs2008.exe did have all the needed debug libraries to successfully compile debug.