On Tuesday 14 June 2011 00:56:08 you wrote: > On 13 Jun 2011, at 22:30, Ville M. Vainio wrote: > > We all know and love Q_WS_MAEMO_5 and Q_OS_SYMBIAN for getting work done. > > > > However, as everybody ends up seeing,, there is no equivalent for meego. > > What do you want it for? MeeGo is Linux, it isn't an operating system.
It doesn't matter if it's an OS or not. Whatever it is, it has *compliancy specifications*. It means that stuff HAS to be done in a certain way. No amount of feature-detection will tell you the required naming schemes, dependency rules and such. In fact, fancy target-agnostic feature detection will/can actually HURT you, because maybe your package could have been MeeGo API compliant, but you detected some lower level libs in there and included non- essential functionality that downgraded you to Platform API compliance. Therefore, when a package (or even executable !) is built is -HAS- to know that the target is MeeGo (OS, platform, kingdom, you name it) so that it could abide by the rules and create a proper package with the desired level of compliancy. Sure, I can prefix/inject a DEFINE in my qmake, but then what's the point in a multiplatform build system if I need to wrap in a multiplatform wrapper script. Best regards, Attila Csipa _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
