Amarok/Development/KF5port: Difference between revisions

From KDE Community Wiki
m (Added some more components)
mNo edit summary
Line 13: Line 13:


==New Dependencies ==
==New Dependencies ==
If you would like to build it then you have to install the following packages (apart from the existing dependencies like Taglib, zlib, googlemock, etc ) containing the following components for your respective system :
If you would like to build it then you have to install the following development packages (apart from the existing dependencies like Taglib, zlib, googlemock, etc ) containing the following components for your respective system :


Qt5::Core
Qt5::Core

Revision as of 11:03, 23 June 2015

This page is meant as a guide to port Amarok to Qt5/Frameworks5 and Plasma5.

Stages of port

The broad plan involves the porting of the code-base to compile by using KF5::KDELibs4Support. After this the plan involves porting Amarok away from KF5::KDELibs4Support. We are still in the first part now i.e the current aim is to let Amarok compile by using KF5::KDELibs4Support(with LOTS and LOTS of depreciated warnings).

  1. Restoring build on Qt5/KF5: Port of cmake files and all code, so everything builds at least again by using KF5::KDELibs4Support. In this part the primary focus is on building it back again. INCOMPLETE
  2. All tests should pass after the above has been done. TODO
  3. Porting away from KF5::KDELibs4Support. TODO

General

The commits containing the ongoing port of Amarok to Qt5/KF5 are present in this personal repository.

New Dependencies

If you would like to build it then you have to install the following development packages (apart from the existing dependencies like Taglib, zlib, googlemock, etc ) containing the following components for your respective system :

Qt5::Core

Qt5::DBus

Qt5::Widgets

Qt5::Test

Qt5::Gui

Qt5::Svg

Qt5::Script

Qt5::Xml

Phonon4Qt5

KF5::CoreAddons

KF5::Solid

KF5::Codecs

KF5::I18n

KF5::ThreadWeaver

KF5::KDELibs4Support

KF5::Plasma

KF5::KCMUtils

KF5::NewStuff

This list has been kept dynamic to avoid pulling unwanted dependencies which means more components will be added when the need arises.


Extra

Some references: