QMake: generated vcproj file contains incorrect rc file path (regression)

In Qt 4.4.2, the "RelativePath" in a vcproj that qmake generates for an .rc file is in fact absolute.

This appears to only happen for a recursive qmake.

This bug has been verified to also occur in Qt 4.5.2 by another user:

When creating a Visual Studio project file having multiple qt-project files that are processed recursively via "qmake -r -tp vc -spec win32-msvc2008 <central-qtproject.pro>", the RC_FILE-entry in a .vcproj-file is written as "RelativePath" but in fact is an absolute path (e.g. '<File RelativePath="f:\buildenvs\x64\src\gui\project\qt\gui.rc"/>').

If qmake is called directly from the directory where the sub-project file is located, it writes a correct "RelativePath" entry to the generated .vcproj while the rest of that file is identical (according to "diff -uwd" (GNU-diff)).

This situation does not hurt as long as one sticks to MSVC, since Visual Studio loads the generated solution with all its sub-projects without complaining.
Nevertheless, this behaviour definitely breaks Intel's converter that switches a solution/project to use the Intel C++ Compiler (no matter if the converter is called from the commandline or from Visual Studio). After converting, Visual Studio complains about the solution or one of its subprojects being in a zombie state and thus cannot be loaded (project is unavailable then).