Needed libphonon enabled in Qt4 compilation/packaging

Bug #253854 reported by Gustavo A. Díaz
38
This bug affects 5 people
Affects Status Importance Assigned to Milestone
qt4-x11 (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Jaunty by Eric Appleman
Nominated for Karmic by Eric Appleman

Bug Description

This is related more to the source package of Qt4 (qt4-x11-4.4.0)

The problem is, I need (and is needed to develop...) the libphonon from the Qt4 package (not the one from kde...).
So, i've tried to download the source package, then i've change the debian rules files, and in configure part replaced -no-phonon for -phonon and the compilation goes great, but fails at the end building the package (using dpkg-buildpackage). For sure i am missing some thing in debian rules to fix this, but i am not a MOTU or expert building packages only i have a base and really I dont need to be a pro here... I only need that lib enabled in Qt4 compilation (and compiling Qt4 in all my workstations for only this, is a hell... it takes so much time...). Cause otherwise is not possible to use it in Qt4 and either in PyQt4 (which is the language i am using to develop an app that needs phonon support).
So i think maintainer of this should enable phonon, or if someone could give a hand of how to do it. I've asked in the IRC channel but i have no responses (and i did it many times)
So i've considered this a "bug" since libphonon from Qt4 is not the same as kde.

The error i have when i try to package is:

http://pastebin.com/m4c954c9d

Revision history for this message
Alex Salt (holy.cheater) wrote :

It should be something like this

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

Perfect, now I've built the package with phonon as well.
Could this change be added? Since When we need to use phonon fro Qt4 and not from KDE, this is needed.

Thanks

Revision history for this message
Alex Salt (holy.cheater) wrote :

I wish that there will be libphonon from the qt package in the repositories too.
As for now, Qt 4.4 is in backports for hardy.. And as I see, libphonon4 from kde now installs in /usr/lib in intrepid, not in /usr/lib/kde4. The issue needs to be investigated by Kubuntu/Qt maintainers.

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

Yes, i think this is important and needs the attention of them.
We developers need this... and is a waste of time to compile Qt4 only to enable Phonon module, since it takes to much time...

Thanks

Revision history for this message
Fathi Boudra (fboudra) wrote :

phonon is shipped in his own packages:
libphonon-dev - development files for the Phonon multimedia framework
libphonon4 - Phonon multimedia framework for Qt 4
phonon - metapackage for Phonon multimedia framework
phonon-backend-gstreamer - Phonon GStreamer 0.10.x backend
phonon-backend-null - Phonon null backend (no real backend)
phonon-dbg - Phonon debugging symbols
phonon-backend-xine - Phonon Xine 1.1.x backend

why not use them ?

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote : Re: [Bug 253854] Re: Needed libphonon enabled in Qt4 compilation/packaging

Cause PyQt will not compile Phonon support even if those separated packages
are installed.

2008/9/19 Fathi Boudra <email address hidden>

> phonon is shipped in his own packages:
> libphonon-dev - development files for the Phonon multimedia framework
> libphonon4 - Phonon multimedia framework for Qt 4
> phonon - metapackage for Phonon multimedia framework
> phonon-backend-gstreamer - Phonon GStreamer 0.10.x backend
> phonon-backend-null - Phonon null backend (no real backend)
> phonon-dbg - Phonon debugging symbols
> phonon-backend-xine - Phonon Xine 1.1.x backend
>
> why not use them ?
>
> --
> Needed libphonon enabled in Qt4 compilation/packaging
> https://bugs.launchpad.net/bugs/253854
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

Guys... this should be fixed please... Actually PyQt does not find Phonon
since is not install in the property dirs (that is, not inside Qt)... Or,
you should include a phonon module in PyQt4.4.x packages...

I am using intrepid and i cant install the libphonon i've created from Qt4,
i've installed the one that comes from the OS, but PyQt does not find it to
compile.

Cheers...

2008/9/19 Gustavo A. Díaz <email address hidden>

> Cause PyQt will not compile Phonon support even if those separated packages
> are installed.
>
> 2008/9/19 Fathi Boudra <email address hidden>
>
> phonon is shipped in his own packages:
>> libphonon-dev - development files for the Phonon multimedia framework
>> libphonon4 - Phonon multimedia framework for Qt 4
>> phonon - metapackage for Phonon multimedia framework
>> phonon-backend-gstreamer - Phonon GStreamer 0.10.x backend
>> phonon-backend-null - Phonon null backend (no real backend)
>> phonon-dbg - Phonon debugging symbols
>> phonon-backend-xine - Phonon Xine 1.1.x backend
>>
>> why not use them ?
>>
>> --
>> Needed libphonon enabled in Qt4 compilation/packaging
>> https://bugs.launchpad.net/bugs/253854
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
>
> --
> Gustavo A. Díaz
> GDNet Projects
> www.gdnet.com.ar
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

Revision history for this message
ironstorm (ironstorm-gmail) wrote :

I also just hit this bug, it breaks portable compiling of Qt4 phonon-based apps...

Is there a way to work around this? Can both versions somehow be installed together?

If not we should probably push this upstream to trolltech, since from what I've read the "official" phonon repos still belong to KDE and this would be a problem to be solved for all distros that ship KDE4.

Revision history for this message
Louai Al-Khanji (slougi) wrote :

I just confirmed the bug. This unfortunately means that Ubuntu is unsuitable as a development environment for me currently.

Changed in qt4-x11:
status: New → Confirmed
Revision history for this message
Mkeeler (mjkeeler7) wrote :

phonon development files need to be changed to be put under /usr/include/qt4/ instead of just under /usr/include. QMake will not work properly otherwise.

In a qt project file, you are supposed to add a line

QT += phonon

To include phonon support for your program. What this does is adds /usr/include/qt4/phonon to the include path. Therefore the standard way of creating QT applications is not supported by the current locations of libphonon-dev. This should definitely be fixed.

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

Not Only for Qt, but cause all they bindings (PyQt, RubyQt, etc) needs it.
The current packaging of Phonon is wrong. And yes, MUST be fixed....

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote :

I am able to run my phonon application doing this:
ln -sf /usr/lib/kde4/plugins/phonon_backend /usr/lib/qt4/plugins/phonon_backend
Still this is a work around and I'm still waiting for a proper solution.

Revision history for this message
hackel (hackel) wrote :

I am guessing this is why the Phonon tab is still grayed out in qt4-qtconfig even after installing the phonon packages in Intrepid? Would be nice to see this fixed for 9.04.

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

Yes... and why devs do not reply about this bug? It is very important to Qt
and related developers, which IS a lot.

2008/12/14 hackel <email address hidden>

> I am guessing this is why the Phonon tab is still grayed out in
> qt4-qtconfig even after installing the phonon packages in Intrepid?
> Would be nice to see this fixed for 9.04.
>
> --
> Needed libphonon enabled in Qt4 compilation/packaging
> https://bugs.launchpad.net/bugs/253854
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Eric Appleman (erappleman) wrote :

So. Is this bug a wontfix for Jaunty or will somebody seriously consider it?

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote : Re: [Bug 253854] Re: Needed libphonon enabled in Qt4 compilation/packaging

I am waiting for that response too.. we need Qt phonon... or a wayt that
apps/bindings of Qt could be compiled with KDE phonon at least... (which i
prefer the first option).

Revision history for this message
Flavio Tordini (zarlino) wrote :

Me too, please give us developers a complete Qt4 build!

Revision history for this message
Jonathan Riddell (jr) wrote :

PyQt has python-qt4-phonon in jaunty.

I am considering switching phonon to being built from Qt but it's a big change for post-feature freeze so I'd be reluctant. Perhaps people can explain more which apps have problems and why they can't just be set to look in /usr/include/KDE for their headers.

Revision history for this message
Flavio Tordini (zarlino) wrote :

Hi Jonathan, it's not about some specific app in Ubuntu that has problems. It is about having a clean and complete Qt4 development environment without having to compile.

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

I' have installed that package in my current Intrepid, which works ok.
But there is problems with which backend to use. For example in my
application i capture video streaming using Phonon, and this does not work
using Xine, which is default backend in KDE. So my chooise is gstreamer...
but this backend has some problems with KDE applications... like, a simple
example: Amarok2 will not reproduce radio streamings URL using gstreamer.
And maybe for sure exist others problems (and i have all gstreamer packages
installed...).
So i think is not the solution. Qt should handle the backends for Qt
applications (and related bindings). To not mix with KDE phonon.

2009/2/24 Jonathan Riddell <email address hidden>

> PyQt has python-qt4-phonon in jaunty.
>
> I am considering switching phonon to being built from Qt but it's a big
> change for post-feature freeze so I'd be reluctant. Perhaps people can
> explain more which apps have problems and why they can't just be set to
> look in /usr/include/KDE for their headers.
>
> --
> Needed libphonon enabled in Qt4 compilation/packaging
> https://bugs.launchpad.net/bugs/253854
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

Yes, True... compiling Qt it takes too long... so... there must be a
solution.... and the one is to have Phonon from Qt separated from KDE. Since
Qt-config has the options to choose Phonon backends as well too.

2009/2/24 Flavio <email address hidden>

> Hi Jonathan, it's not about some specific app in Ubuntu that has
> problems. It is about having a clean and complete Qt4 development
> environment without having to compile.
>
> --
> Needed libphonon enabled in Qt4 compilation/packaging
> https://bugs.launchpad.net/bugs/253854
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

Revision history for this message
Jonathan Riddell (jr) wrote :

We'll switch to building phonon from Qt in the next release. I've not heard any actual problem with how it is done currently though, the library is available for development with. If particular backends have problems with particular apps that isn't going to be solved however libphonon is compiled. It isn't going to help to build two libphonon's, that just won't work.

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

Good news then... Since in my case, I prefer to use the Phonon from Qt than
KDE, since my application/s will be multi-platforms... So, is better to play
with Qt phonon than KDE one...
Yeah, seems there is no problem of how WE use Phonon from KDE, but we depend
of KDE... As I explained before here, whatever backend i choose for KDE is
being used for my Qt application... so that is not right. Since using
Gstreamer of Xine could bring problems to KDE apps or Qt as well.
A common scenario: I need to use Gstreamer in Qt, but in KDE I need to use
Xine (Example in Amarok 2.0, remotes url like radios does not work with
gstreamer, but in 2.0.1 is fixed... so maybe other apps could have problems
as well)

Revision history for this message
Eric Appleman (erappleman) wrote :

Phonon is still greyed out.

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

I wonder when this issue will be fixed... to have a separated phonon Qt and
phonon KDE.....

2009/6/5 Eric Appleman <email address hidden>

> Phonon is still greyed out.
>
> --
> Needed libphonon enabled in Qt4 compilation/packaging
> https://bugs.launchpad.net/bugs/253854
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

Revision history for this message
Flavio Tordini (zarlino) wrote :

Can anyone explain why is there even such a thing like kde-phonon and qt-phonon? Isn't the Phonon project one? Why can't they settle on a clean release process and share the same stable version like everybody else in the world? Please someone enlighten me.

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

For that please read the hole bug thread explaning why.

2009/6/5 Flavio <email address hidden>

> Can anyone explain why is there even such a thing like kde-phonon and
> qt-phonon? Isn't the Phonon project one? Why can't they settle on a
> clean release process and share the same stable version like everybody
> else in the world? Please someone enlighten me.
>
> --
> Needed libphonon enabled in Qt4 compilation/packaging
> https://bugs.launchpad.net/bugs/253854
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

Revision history for this message
Flavio Tordini (zarlino) wrote :

I read it but there's no answer to my question. I'm not talking about the need of having two packages, I'm asking why the two upstreams created this mess in the first place.

Revision history for this message
Eric Appleman (erappleman) wrote :

Any progress?

Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

Seems nobody cares about this... and about Kubuntu at all...

2009/7/19 Eric Appleman <email address hidden>

> Any progress?
>
> --
> Needed libphonon enabled in Qt4 compilation/packaging
> https://bugs.launchpad.net/bugs/253854
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

Revision history for this message
Roderick B. Greening (roderick-greening) wrote :

Fixed in Karmic, once released. And yes we care. Negativity is not warranted :P

Revision history for this message
Roderick B. Greening (roderick-greening) wrote :

Updated status. Fixed in Karmic (9.10) - was actually fixed a while back (alpha 1 probably).

Changed in qt4-x11 (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Gustavo A. Díaz (gdiaz) wrote :

Yeah, but since we replied again with this now the status of this ¨bugs¨ was
updated. :)

2009/7/19 Roderick B. Greening <email address hidden>

> Updated status. Fixed in Karmic (9.10) - was actually fixed a while back
> (alpha 1 probably).
>
> ** Changed in: qt4-x11 (Ubuntu)
> Status: Confirmed => Fix Released
>
> --
> Needed libphonon enabled in Qt4 compilation/packaging
> https://bugs.launchpad.net/bugs/253854
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

Revision history for this message
Eric Appleman (erappleman) wrote :

I don't call this "fixed".

Changed in qt4-x11 (Ubuntu):
status: Fix Released → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We do compile with Phonon support. I guess htat one other bug you commented on is not a duplicate.

Changed in qt4-x11 (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Eric Appleman (erappleman) wrote :

Anything going on with this bug?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.