It's something I had a bit of a moan about a few pages back on this thread, I reached out to Bob Duffy from Intel about it and asked zehjotkah to check with Maemo developers around the MeeGo conference to see how they are handling it. I reached out to Bob Duffy as I noticed he was mentioned as an Intel "Developer Community Manager & Social Media Strategist", so I felt he would be in a good position to help assist our developer community transition to MeeGo but unfortunately his social media strategy in this case was not to respond to my tweet for help with this

The 'official' reply, via zehjotkah, is that there will be a new version of the MeeGo sdk with plugin support, however Im not sure how that will help our problem. Honestly I've been raising this issue up since 2010's MeeGo conference, and I still don't think anyone is aware or even cares about this problem - even though it surely is harming MeeGo application development.

So what to do.. well if you figure out the solution then let us know Or, unless you hear otherwise, my suggestion is to draw a line in your mind that there is no smooth update path for the Qt SDK on your machine to target both platforms, and hope to be pleasantly surprised on the next MeeGo SDK update. In the meantime if you happen to have two machines capable of developing on then choose to target Maemo on one and MeeGo on the other. Otherwise you may have to decide will you focus on Maemo development or MeeGo development on your development machine.