View Single Post
Posts: 196 | Thanked: 141 times | Joined on Aug 2007
#6
Originally Posted by smurfy View Post
Hi,

if you only use QT base packages and not the maemo5 qt package the app should be binary compatible.

but as noobmonkey already said. meego uses rpm not deb (at least the reference platform)

i heard somewhere that nokias brand of meego uses deb, but i don't know if this is fact or just rumors, neverless for meego reference you need to create a rpm package.
You're confusing several things:

1) Meego on the N900. Uses rpm files. Uses code to generate it's look and feel completely separate from Maemo5. Not ready for primetime.

2) Harmattan formerly called Maemo6 now actually called Meego-Harmattan to everyone's confusion). Uses deb files, is a continuation of Maemo5 code, with bug fixes, new features, using the same code meego uses for it's look&feel (although the actual look and feel may be different from Meego). Will NOT run on the N900 but rather on some future device. Closed development but there is significant communication with the meego team.

3) Harmattan- community edition. Non-existant vaporware that will take bits from Harmattan (where possible) and meego (where necessary) to deliver an OS that is as close to Harmattan as possible yet still runnable on the N900. Will use deb files. Will use the same look and feel code as Meego and Harmattan.

None of these versions are likely to be binary compatible with each other. However Nokia is pushing for everyone to use the same look and feel code (officially called Meego Handset UX) based on qt. Ideally the only thing you'll need to do is repackage it twice to get your application into Harmattan extras and meego extras (if such a thing exists)
 

The Following 3 Users Say Thank You to jcharpak For This Useful Post: