There are several possible ways to build and install KDE and the method you choose depends on what you want to do with KDE once it is built. The table below provides some guidance in making this decision, but before you start please read the rest of the page for more detailed information on Getting Started.

+

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software once it is built. In particular, you may only need to build parts of the KDE SC. The table below provides some guidance in making this decision, but before you start please read the rest of the page for more detailed information on Getting Started.

<table border="1" width="100%" cellpadding="5">

<table border="1" width="100%" cellpadding="5">

Line 37:

Line 37:

== Source Repositories and Revision Control ==

== Source Repositories and Revision Control ==

+

TODO: Short intro to the subject, why's and where's, link to other pages.

+

Currently, KDE SC source code is for the most part, accessed using git. For those modules that are still in svn, consult: [[Getting_Started/Sources/Anonymous_SVN]].

Currently, KDE SC source code is for the most part, accessed using git. For those modules that are still in svn, consult: [[Getting_Started/Sources/Anonymous_SVN]].

For instructions on installing KDE SC on Windows, BSD, or Mac OS X, or instructions for installing KDE3, please see the [[Getting_Started/Build|other supported platforms]] page. There are also [[Getting_Started/Build/KDE4.x_Upgrade|upgrade instructions from a branch to trunk]].

+

KDE can also be built on platforms other than Linux. For more details please see the relevant page.

+

+

[[Getting_Started/Build|other supported platforms]]

+

+

* Windows

+

* Mac OSX

+

* BSD

+

+

=== KDE 3 ===

+

KDE3 is no longer supported, but some documentation on building it still exists.

This page is yet to be reviewed for changes required by the migration to Git. Information and commands on this page may no longer be valid and should be used with care. Please see the KDE Git hub page for more details.

Introduction

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software once it is built. In particular, you may only need to build parts of the KDE SC. The table below provides some guidance in making this decision, but before you start please read the rest of the page for more detailed information on Getting Started.

Official Release

Nightly Build

Stable from Source

Master (Recommended)

For the casual user, or a developer who is working on applications outside of KDE SC

For application developers or package managers who are not modifying the core of KDE SC

For KDE SC and applications developers that want to spend less time setting up a build system

For developers working on core KDE SC functionality, and desire/need up-to-the-minute changes. Recommended for very active developers.

1. Use a Distribution with KDE to set up a fully functional KDE system in one step. Also install the "developer packages" if you want to compile KDE software

Getting Help

If you have any questions or issues related to building and developing KDE feel free to ask us. However, be patient and do expect to be attempting to work through the issue as well (we aren't just going to do it all for you).

Source Repositories and Revision Control

TODO: Short intro to the subject, why's and where's, link to other pages.

Amarok has already migrated to Git, as well as many other modules modules (phonon, parts of kdesupport, kdelibs, kdebase, kdeplasma-addons). Until we are fully migrated at least, it is recommended to use kdesrc-build if you can, as it takes care of all of this for you.

Development Tools

You will likely want to use a stable package from your distribution instead of the ones of the KDE version you are working on.