Amarok/Development/Hacking On Amarok HowTo: Difference between revisions
Appearance
< Amarok | Development
→How to Hack on Amarok's Codebase Using KDevelop: correct wrong link |
→How to become involved: correct link |
||
Line 1: | Line 1: | ||
[[Category:Amarok]] [[Category:Development]] | [[Category:Amarok]] [[Category:Development]] | ||
==How to become involved== | ==How to become involved== | ||
#Most discussion regarding Amarok development happens in IRC. Join us in [irc://irc.freenode. | #Most discussion regarding Amarok development happens in IRC. Join us in [irc://irc.freenode.net/#amarok #amarok] on [irc://irc.freenode.net irc.freenode.net]. | ||
#Join the [https://mail.kde.org/mailman/listinfo/amarok mailing list]. | #Join the [https://mail.kde.org/mailman/listinfo/amarok mailing list]. | ||
#Read everything in the [http://projects.kde.org/projects/amarok/repository/revisions/master/show/HACKING HACKING folder]. It goes over the Amarok coding style and other important information. | #Read everything in the [http://projects.kde.org/projects/amarok/repository/revisions/master/show/HACKING HACKING folder]. It goes over the Amarok coding style and other important information. |
Revision as of 17:08, 15 January 2013
How to become involved
- Most discussion regarding Amarok development happens in IRC. Join us in #amarok on irc.freenode.net.
- Join the mailing list.
- Read everything in the HACKING folder. It goes over the Amarok coding style and other important information.
- Submit your patch. There are several channels to do so:
- Bug Tracker: Search for the problem you are solving on KDE's bugzilla and attach the patch. If there isn't a bug for it yet, create a new bug or wishlist and then attach the patch.
- IRC: IRC has the advantage that a developer might happen to be online and has the time to test your patch, it could be applied immediately or give immediate feedback.
- Mailing lists: Things often get overlooked in the mailing list, so do not rely on it. However it is a good method of bringing up a subject with the development team.
How to Hack on Amarok's Codebase Using KDevelop
- Install the KDevelop IDE (Integrated Development Environment). You should use your distribution's package, or build using Konstruct.
- Fire up KDevelop and from the "Project" menu, select "Open Project...", then choose the amarok.kdevelop file from the extragear/multimedia/amarok/ directory.
- Compile Amarok normally once through the standard means.
- From the "Build" menu select "Build Project" to build Amarok after you have made changes.
- To find the source of a particular feature, a good method is to find an English string associated with the feature and then search for it via "Edit" → "Find in Files".
- For more on setting up KDevelop 4, see Setting up KDevelop
How to Hack on Amarok's Codebase Using Qt Creator
- Fire up Qt Creator, and from the "File" menu select "Open File or Project".
- Navigate to the Amarok source directory and select the file CMakeLists.txt