[Webkit-unassigned] [Bug 39357] New: [QT] QT_BEARER flag is not enabled on S60 properly

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed May 19 06:45:46 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=39357

           Summary: [QT] QT_BEARER flag is not enabled on S60 properly
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: S60 Hardware
        OS/Version: Other
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: mahesh.kulkarni at nokia.com
                CC: yael.aharon at nokia.com, laszlo.1.gombos at nokia.com


QT_BEARER is right now only enabled for symbian (on 4.6) and enabled for all 4.7 releases. 

There is though one problem with the way the flag has been defined. 


    symbian: {
        exists($${EPOCROOT}epoc32/release/winscw/udeb/QtBearer.lib)| \
        exists($${EPOCROOT}epoc32/release/armv5/lib/QtBearer.lib) {
            DEFINES += ENABLE_QT_BEARER=1
        }

Mobility builds only after Qt is built so the condition above never satisfies. After talking to vihria, ekoppen, tronical and SaMUELnEVALA on IRC, 

exists($$[QMAKE_MKSPECS]/features/mobility.prf) can be used to check if qtmobility is built. QtMobility 1.0.0 (public release) has bearer by default on all platform so no need to check for library either. 


PS: I will attach a patch on the same and may be not with symbian flag as well!

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list