the right home for Phonon

Alexander Neundorf neundorf at
Thu May 15 22:27:20 BST 2008

On Thursday 15 May 2008, Matthias Kretz wrote:
> On Thursday 15 May 2008, Alexander Neundorf wrote:
> > One generic comment, i.e. not only for phonon: if we do a release, we tag
> > all of KDE/, but not kdesupport/ (AFAIK).
> > This makes it later on sometimes quite hard to get a matching kdesupport
> > for some old KDE release. I'd suggest to also tag kdesupport when KDE/ is
> > tagged.
> kdesupport does not have any release policy or such. It's just for the
> convenience of KDE developers.
> Releases of software in kdesupport should copy to tags/<name>. They're
> always releases independent of KDE releases.

Yes, I know.
It's just, let's say for some reason I need KDE 3.1.1 today, so I can get 
the "real" KDE modules without problem, but in order to make it build I need 
a matching kdesupport. Having this tagged too would make that easier.

> > Any special questions ?
> > You can also copy it already earlier so there is more time to get it
> > working and then enable/make it mandatory later.
> > (next week I won't be online a lot)
> There's a lot of macros in kdelibs/cmake/modules. I don't know how much of
> that I need. There are the unit test macros, a lot of path variables,
> extras for Win and Mac that I don't understand...

You don't need much from that.
You just release a library, not a development framework for hundreds of 
developers, this makes things much easier :-)
(i.e. it is no bigger problem if you have to do some more manual work in 
phonon, because this doesn't force hundreds of developers to do the same). 
You can also have a look in akonadi.
What to watch out for:
-you'll need some install paths
-you need to set up RPATH (keep the defaults + set the target property 
-for unit tests you can just use ADD_TEST()
-automoc, well, you know best yourself :-)

> So I have a phonon subdir ready for kdesupport. I'll commit it and won't
> enable the subdir in kdesupport/CMakeLists.txt for now. I tested standalone
> compilation of it (i.e. without the kdesupport stuff) and it works for me
> so far.

Yes, cool. I'll have a look.


More information about the kde-core-devel mailing list