Difference between revisions of "Getting Started/Build"

Jump to: navigation, search
m (Getting Ready)
(Building From Source)
Line 37: Line 37:
* [[Getting_Started/Build/KDE4|Download and Build KDE SC from Git]]
* [[Getting_Started/Build/KDE4|Download and Build KDE SC from Git]]
* [[Getting_Started/Build/KDE4.x|Build a stable 4.x release]]
* [[Getting_Started/Build/KDE4.x|Build a stable 4.x release]]
* [[Getting_Started/Set_up_KDE_4_for_development|Set up scripts]] to ease KDE development
== Troubleshooting The Build ==
== Troubleshooting The Build ==

Revision as of 18:29, 3 March 2011

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.

Getting Started/Build

Here you will find instructions for compiling and installing KDE from source and suggestions for when compilation doesn't go so smoothly.


Extra Information

The build process described in these pages is kept as simple and generic as possible, but it is generally assumed you are building KDE4 on Linux. Extra information about building KDE under specific platforms or conditions can be found at the following links:

Scripted Builds

The easiest way to build the KDE SC from scratch is to use one of the build scripts that are available. This approach is highly recommended for those new to building KDE SC. The builds remain compatible with the manual methods of building KDE SC so you can change later if you want.

Getting Ready

Manually building KDE Software requires that you first set up the build environment and install the required development tools and libraries.

Building From Source

Troubleshooting The Build

Compile and Linking errors are frequent sources of discouragement. Make careful note of the first occurrence of an error in your build process. It could be as simple as a bad environment variable, an unexpected version of a library or missing prerequisite. Please read the instructions carefully.

Please review your logs and do searches for fixes. If you cannot find a solution, try the Troubleshooting page. If you still cannot resolve the problem then please for help on IRC or a Mailing List. You can post your detailed issue from Build/Stories.

Content is available under Creative Commons License SA 4.0 unless otherwise noted.