Bug 35906 - [Qt] Build on Maemo 5 is broken
Summary: [Qt] Build on Maemo 5 is broken
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other Linux
: P1 Blocker
Assignee: Simon Hausmann
URL:
Keywords: Qt
Depends on:
Blocks: 35784
  Show dependency treegraph
 
Reported: 2010-03-09 00:41 PST by Simon Hausmann
Modified: 2010-03-09 06:40 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Hausmann 2010-03-09 00:41:46 PST
It appears that the trunk needs to be adapted to QAbstractKineticScroller API changes that were done shortly before the release of Qt 4.6 for Maemo 5.

3/8/10 5:13:12 PM CET: ../WebKit/qt/Api/qwebview.cpp:71: warning: direct base 'QObject' inaccessible in 'QWebViewKineticScroller' due to ambiguity
3/8/10 5:13:12 PM CET: ../WebKit/qt/Api/qwebview.cpp: In member function 'void QWebViewKineticScroller::setWidget(QWebView*)':
3/8/10 5:13:12 PM CET: ../WebKit/qt/Api/qwebview.cpp:84: error: 'QObject' is an ambiguous base of 'QWebViewKineticScroller'
3/8/10 5:13:12 PM CET: ../WebKit/qt/Api/qwebview.cpp:91: error: reference to 'setParent' is ambiguous
3/8/10 5:13:12 PM CET: /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtCore/qobject.h:193: error: candidates are: void QObject::setParent(QObject*)
3/8/10 5:13:12 PM CET: /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtCore/qobject.h:193: error:                 void QObject::setParent(QObject*)
3/8/10 5:13:12 PM CET: ../WebKit/qt/Api/qwebview.cpp:91: error: reference to 'setParent' is ambiguous
3/8/10 5:13:12 PM CET: /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtCore/qobject.h:193: error: candidates are: void QObject::setParent(QObject*)
3/8/10 5:13:12 PM CET: /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtCore/qobject.h:193: error:                 void QObject::setParent(QObject*)
3/8/10 5:13:12 PM CET: ../WebKit/qt/Api/qwebview.cpp:98: error: 'QObject' is an ambiguous base of 'QWebViewKineticScroller'
3/8/10 5:13:12 PM CET: ../WebKit/qt/Api/qwebview.cpp: In member function 'virtual bool QWebViewKineticScroller::eventFilter(QObject*, QEvent*)':
3/8/10 5:13:12 PM CET: ../WebKit/qt/Api/qwebview.cpp:106: error: cannot call member function 'virtual bool QObject::eventFilter(QObject*, QEvent*)' without object
3/8/10 5:13:12 PM CET: ../WebKit/qt/Api/qwebview.cpp:121: error: 'handleMouseEvent' was not declared in this scope
3/8/10 5:13:12 PM CET: ../WebKit/qt/Api/qwebview.cpp:126: error: cannot call member function 'virtual bool QObject::eventFilter(QObject*, QEvent*)' without object
3/8/10 5:13:13 PM CET: ../WebKit/qt/Api/qwebview.cpp: In constructor 'QWebView::QWebView(QWidget*)':
3/8/10 5:13:13 PM CET: ../WebKit/qt/Api/qwebview.cpp:306: error: cannot allocate an object of abstract type 'QWebViewKineticScroller'
3/8/10 5:13:13 PM CET: ../WebKit/qt/Api/qwebview.cpp:71: note:   because the following virtual functions are pure within 'QWebViewKineticScroller':
3/8/10 5:13:13 PM CET: /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtGui/qabstractkineticscroller.h:123: note: 	virtual void QAbstractKineticScroller::attachToWidget()
3/8/10 5:13:13 PM CET: /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtGui/qabstractkineticscroller.h:124: note: 	virtual void QAbstractKineticScroller::removeFromWidget()
3/8/10 5:13:13 PM CET: /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtGui/qabstractkineticscroller.h:125: note: 	virtual QRect QAbstractKineticScroller::positionRange() const
3/8/10 5:13:13 PM CET: /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtGui/qabstractkineticscroller.h:127: note: 	virtual QPoint QAbstractKineticScroller::position() const
3/8/10 5:13:13 PM CET: /targets/FREMANTLE_ARMEL/opt/qt4-maemo5/include/QtGui/qabstractkineticscroller.h:128: note: 	virtual void QAbstractKineticScroller::setPosition(const QPoint&, const QPoint&)
Comment 1 Simon Hausmann 2010-03-09 01:09:00 PST
Hrm, this may actually be a CI problem ;(. I'm looking into this now.
Comment 2 Simon Hausmann 2010-03-09 06:40:17 PST
It _was_ a CI problem :( Wrong version of the Qt package installed with the old API. Sorry :(