Em Quinta-feira, 11 de Novembro de 2010, às 12:39:22, Teemu Tuominen escreveu: > Ok, thanks for the info. > > Meego target is made by a patch in Meego obs. And several patches are > enabling the Q_WS_MAEMO-features as we speak.
Please remove it then.
Q_WS_MAEMO_6 and Q_WS_MEEGO are not supported features of the Qt API. Having
them present in QtGlobal will only cause issues because people will start
depending on them.
> We (n900 adaptation team) just ran into this while enabling the
> camerabin backend. The def.directories setup is more generic issue and
> I'm not that into Qt. So, are you implying that there's no need to
> change such static def.dirs in upstream/meego, but handle the cases in
> application level ? However, I asked our qt guy to check how it goes
> with QDesktopServices.
No, I'm saying that MeeGo isn't a windowing system, therefore it doesn't get a
macro. X11 is the windowing system.
> > Q_WS_MEEGO doesn't exist. It's only Q_WS_X11.
Applications written for Linux / X11 simply do not know whether they're being
built for MeeGo or another Linux distribution. They also don't know whether
they're being built for Netbook, Handset, IVI or any other (there's in fact
only one build in the OBS for all).
The information on what kind of device the app is running on should come from
the runtime (see Qt Mobility System Information). If applications need data
that isn't exposed, let us know via suggestion / bug report in:
http://bugreports.qt.nokia.com
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
