phonon installs a broken /usr/share/qt4/mkspecs/modules/qt_phonon.pri When qmake reads that file, it prints the following error: /usr/share/qt4/mkspecs/modules/qt_phonon.pri:8: Unknown test function: !contains It seems qmake doesn't like the backslashes used to escape the newlines. Indeed if the file content is changed to: if(!exists($$_QMAKE_CACHE_)|!contains($$list($$fromfile($$_QMAKE_CACHE_, CONFIG)), QTDIR_build)) { QT_CONFIG += phonon } (where the two conditions are both on the same line), qmake no longer throws the above error.
Oswald, would you mind having a quick look at this please? (In reply to comment #0) > phonon installs a broken /usr/share/qt4/mkspecs/modules/qt_phonon.pri > When qmake reads that file, it prints the following error: > > /usr/share/qt4/mkspecs/modules/qt_phonon.pri:8: Unknown test function: > !contains > > It seems qmake doesn't like the backslashes used to escape the newlines. Indeed > if the file content is changed to: > > if(!exists($$_QMAKE_CACHE_)|!contains($$list($$fromfile($$_QMAKE_CACHE_, > CONFIG)), QTDIR_build)) { > QT_CONFIG += phonon > } > > (where the two conditions are both on the same line), qmake no longer throws > the above error.
https://bugreports.qt.nokia.com/browse/QTBUG-22443
Davide, I've added a workaround in phonon-4.5.0-r2 and phonon-4.5.1-r1. Could you please verify if that helps? Anyway, seems this is a qt-core bug (thanks Oswald for identifying this!!!)
(In reply to comment #3) > Davide, I've added a workaround in phonon-4.5.0-r2 and phonon-4.5.1-r1. > Could you please verify if that helps? > Yes, the workaround works. Thanks! I'll keep this bug open until qmake is properly fixed though.
(In reply to comment #4) > Yes, the workaround works. Thanks! > I'll keep this bug open until qmake is properly fixed though. According to the upstream bug report, this is fixed in 5.0.0 RC 1. Do you still want to track this bug for 4.x (I don't know what the possibility of backporting is?)
(In reply to comment #5) > (In reply to comment #4) > > Yes, the workaround works. Thanks! > > I'll keep this bug open until qmake is properly fixed though. > > According to the upstream bug report, this is fixed in 5.0.0 RC 1. Do you > still want to track this bug for 4.x (I don't know what the possibility of > backporting is?) Right. I don't think this will ever be fixed in qt4.