Cannot build without QtMobility bindings

[marmistrz]

./configure doesn't recognize the option:

> ./configure -no-mobility
-no-mobility: unknown option
Usage:  configure [-meego] [-config <config>]
    [-make <part>] [-nomake <part>] [-help]

Configure options:

    -meego ................... Build MeeGo Style
    -config (config) ......... Configuration options recognized by qmake
    -make (part) ............. Add part to the list of parts to be built at
                               make time (available parts: demos examples extras tests)
    -nomake (part) ........... Exclude part from the list of parts to be built

Additional options:

 A plus (+) denotes a default value that needs to be evaluated. If the
 evaluation succeeds, the feature is included. Here is a short explanation
 of each option:

    -no-maliit ............... Do not complile Maliit framework support
 +  -maliit .................. Compile Maliit framework support

    -no-contextsubscriber .... Do not compile Context Subscriber support
 +  -contextsubscriber ....... Compile Context Subscriber support

    -no-xdamage .............. Do not compile XDamage support
 +  -xdamage ................. Compile XDamage support

    -no-meegographicssystem .. Do not compile MeeGo graphics system support
    -meegographicssystem ..... Compile MeeGo graphics system support

    -no-mobility ............. Do not compile Qt Mobility support
 +  -mobility ................ Compile Qt Mobility support

[sledges]

thanks for report. please beautufy your paste with https://help.github.com/articles/github-flavored-markdown

why and when are you running into this issue?

[marmistrz]

Built the Qt components with latest git source.
I was trying to build it it for Fremantle, as our current components are borked.

Btw. is it possibly to emulate the status bar without the right system-ui?

[sledges]

have you conmpiled qt5/qtquick2 branch? is the one supported now

[marmistrz]

Nope, I'm using Qt4, as it's the version used by Fremantle.

[sledges]

I see that it didn't follow the HAVE_MOBILITY approach as for other flags, so, yes, it's a bug: https://github.com/nemomobile/qt-components/blob/master/configure#L223

There must have been a reason for it, as it's checking for qtmobility availability via load() macros in .pro/.pri files

qt-components doesn't use much of QtMobility stuffs though (only SystemInfo, and DocumentGalleryModel in one demo)

@rburchell, could you comment more?