I have been keeping up with the KDE that has been updated in -current. Recently, phonon seems to have been moved to QT from KDE. I think that KDE needs to be configured with -no-phonon option so that CMake will know to look for it in QT rather than KDE.

I ran into trouble trying to compile the latest amaroK with the build script and the cmake failed saying that phonon* could not be found. It indicated that it was looking for it in /usr/include/ which is the KDE include directory. It seemed odd that I could not compile even the version that I had just installed a short time ago and then I realized that I removed the phonon package and now use the one in QT.

I suspect that I have not explained this very well but I welcome comments.

I am using Slackware 13 -current (with the exception of the packages in /testing) Also I am using amaroK compiled from git.

This change has been reverted the next day. Since i built KDE the next day the change was reversed, i had no problems with phonon whatsoever. & phonon has been readded. QT provides the phonon libs and phonon itself provides the backends.
I use only the xine backend fwiw.

Phonon is working fine. I'm having trouble expressing my question so please bear with me. The trouble doesn't show up until I try to compile something with CMake that requires phonon. CMake will look for the phonon libs and includes in the KDE lib and include directories. It looks like the KDE packages (or one of the packages) needs to be build with -no-phonon option set so that CMake will know to look for the phonon libs and includes in the QT lib and include directories.

If I was more adept at building packages, I would verify this by rebuilding some of the KDE 3.3 stuff and see if it fixes things.

Then name the package so someone else can check it out and either confirm the problem with the package or if you did something wrong.

Try ...

Hi I am having trouble compiling Application XXX in Slackware-current and I get an error YYY, does anyone else have this problem or a solution?

I was hoping that the focus would be on the cause of the problem rather than the application that I was working with. It seems that this is not isolated to amaroK and is a problem with the KDE packages in -current or something related to that. Likely CMake itself is built wrong for -current.

I may have failed to mention that I compiled amaroK successfully before moving to KDE 4.3.3 and could not compile the same source with the same build script after the upgrade. If I remember correctly, I even compiled amaroK after moving to KDE 4.3.3 but before removing the phonon package that was removed in -current.

Everything else works great in KDE and Slackware 13 in general AFAIK.

I made a phonon simlink in the /usr/include directory to the phonon in the /usr/lib/qt/include directory in order to get it to work. I don't remember the exact error but if you need it, I can remove the simlink and run the build script again to get it.

Thank you for your patience...I don't normally have this much trouble expressing things.

If you want to run -current you need to start reading the changelog as it will often contain answers to problems that jump into the system.

In particular this time around the removal of phonon from -current was wrong and it has since been added back in.

You will need to resync yourself with -current and make sure that phonon gets reinstalled.

phonon: phonon (multimedia framework for KDE4)
Thank you for the advice. I have followed the changelog for -current. The amaroK build script worked fine until I removed phonon-4.3.1-i486-1 and installed phonon-4.3.1-i486-2. phonon-4.3.1-i486-1 included all of the includes and libraries for phonon and placed them in the /usr/include/phonon directory. As stated in slack-desc, phonon-4.3.1-i486-2 includes backend but the includes and libs are provided by Qt and are placed in the /usr/lib/qt/phonon directory. This is the problem. CMake is looking for pnononnamespace.h in the KDE includes directory or /usr/include/phonon and the file is found in /usr/lib/q/include/phonon.

I got amaroK to build by putting a phonon symlink in the KDE includes directory pointing to the Qt phonon directory. What I'm hoping to be able to do is drill down what is not working so that CMake can work out where the phonon files are supposed to be. As I understand, this could happen for any application that is built from source that requires any of the phonon files. I can't seem to figure out what it is that tells CMake where to look for phonon...or anything else for that matter.

Just out of curiosity do you have /etc/profile.d/qt4.sh
and is CPLUS_INCLUDE_PATH coming up correctly if you run 'export' from the command line?

No this is all I get:
Where should that have come from? I could add it but I would think that it would have been included already. Do you think this may be the problem?

Should not have that kde3 part but the first part is what mine has and when running cmake on amarok it finds the includes under '/usr/lib/qt/include'

NB lib64 vs lib is 64bit vs 32bit make sure yours matches with the version of Slackware you have

I think the kde3 part is because kde-compat and qt3 are installed originally for k3b3 and now to support quanta3. It doesn't seem like it would matter as long as the correct path is included in the list.
It seems that there is something on my system 'telling' CMake that phonon is still installed with KDE when it has moved to Qt. Somewhere along the way I must have missed a step in the upgrade from kDE 4.3.2 to 4.3.3 and the whole phonon remove and re-add thing. What I can't seem to find is what it is that tells CMake where to look for phonon libs and includes. That has to be where the issue lies. It seems that all of the other dependencies of amarK, whether they be KDE or Qt or otherwise, seem to be found okay so CMake is finding all the other Qt files that it needs. This looks to be specific to phonon and CMake. not really KDE or Qt. I thought it may be a thing with amaroK (CMmakeList.txt) but how would the developers know if a person had phonon support in KDE or in Qt? AmaroK would have to be set up to go either way, I would think.

Is it possible that I need to re-install qt or at least run the install script? I think that having waited to un-install phonon from the earlier setup may be the culprit. There must be something that sets up the environment so that CMake will know where to look.