[Qt-mobility-feedback] Qt-mobility 1.1.0 tech preview project changes - are necessary only when upgrading existing Visual Studio project

[Steve Schilz]

Justin McPherson (Nokia) responded to my notes about needing to manually
configure the project when upgrading from Qt Mobility 1.0.1 to 1.1.0.
To be clear, the need for me to manually upgrade the project stems from
my use of Visual Studio.  Had I used QMAKE, most of that pain would have
been avoided.  Detailed responses follow.

> Did you configure && make && make install? You need to do all three
steps.
>
> Then if you have the standard
> CONFIG += mobility
> MOBILITY += multimedia
> 
> You shouldn't need to do the above. 

[Steve Schilz] 
My build steps were as follows: 
	Configure -demos -examples -modules multimedia
	nmake
	nmake install  

 
> > 2) Change Linker additional dependencies from QtMediaD4 to
QtMultimediaKit1 (NOTE 1, not 4!)
>  > 3) Remove #include <QTMediaNamespace> references in the project
> 
> This is from some old project?
>  
> - Justin
 [Steve Schilz] 
This is from an existing Visual Studio project that was generated using
qmake -t vcapp, and previously built against Qt Mobility tech preview
1.0.1.  
So rebuilding the visual studio project from the .PRO file would have
avoided the need to manually make any include file and linker changes. 

Steve