Le 03/08/2012 08:20, Oswald Buddenhagen a écrit :
On Thu, Aug 02, 2012 at 02:48:20PM +0200, Harald Sitter wrote:
The problem is that I always get beaten with a stick whenever I
suggest that Phonon might eventually want to switch to qmake.
well, it's certainly a step back in some ways (dependency tracking being
the most serious one. rm -rf build/ and a working ccache are your
friends).
Generally speaking though we could not replicate our present cmake
magic in qmake, so sacrifices needed to be made there.
you have the master of qmake at your fingertips. ;)
Oh great, maybe you can do the first phonon.pro (on the current trunk)
and kde's member could maintain it.
i can participate if you want but i'm not a specialist like you ;)
We are aware of building on windows not being a particular charm
(hence why I keep bringing up the qmake idea) but at this time we
don't really have a solution. There was however talk of creating
pre-build binaries (something like an SDK you can throw into the Qt
SDK), to easily get an up-to-date Phonon.
i think that misses the point. the crucial point is providing a module
description file for qmake use (the "module pri file"), so using it from
qmake becomes just QT+=phonon like it was with our internal copy.
you already have a qt_phonon.pri, but it's, err, lagging in content
(it's on qt 4 level). see
http://qt-project.org/wiki/Creating-a-new-module-or-tool-for-Qt#58bc93114d2386b74e861888ac36a384
or any of the qt_*.pri files in $$[QT_HOST_DATA]/mkspecs/modules/
(qmake -query QT_HOST_DATA).
in your opinion it represents a lot of work ?
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
