>>> While I'm not sure about the current status (installing as we speak), >>> this will be just another component for Nokia Qt SDK as time goes on. >>> It will essentially add the "Meego 1.1 support" feature to NQS. >> >> There's a long road before it happens. > >What's there to stop this from happening sooner? The fact that MADDE >support is still hardwired it Qt4ProjectManager and does debian >specific stuff?
No, relying on MADDE isn't a problem. Qt4ProjectManager and MADDE are both hardwired to Maemo. That's the issue (planned to be solved and patches are going in that sense). >>> Also, making a distinction with Qt SDK/Qt Creator and NQS will be a >>> bit artificial in the long run, since the biggest difference is the >>> installer and component maintenance tool. Qt Creator is essentially >>> what you get if you install NQS with the online installer and disable >>> the extra components. >> >> Your assumptions are wrong. Qt Creator/MADDE aren't the same. > > Above I meant "distinction between qt creator and nqs is artificial", > not that meego sdk is already using mainline stuff. ok :) >> Indeed, in the long run, we want to have these bits merged. > > There is work done to make Qt Creator 2.2 allow custom targets in > plugins through Qt4TargetFactory. Using that mechanism, the merge will > be less problematic as it doesn't need to touch Qt Creator code. that's the long term solution and the way to go. Our SDK additions should become plugins only on top of Qt Creator mainline. For that, we need Qt Creator 2.2, write our changes as plugins and time :) > Or, have you implemented an independent mechanism of your own to > facilitate all of this already? _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
