| Line 4: | Line 4: | ||
Here you will find instructions for compiling and installing KDE from source and suggestions for when compilation doesn't go so smoothly. | Here you will find instructions for compiling and installing KDE from source and suggestions for when compilation doesn't go so smoothly. | ||
| − | + | == Introduction == | |
| − | + | ||
| − | == | + | == 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: | ||
| + | |||
| + | * [[../Older_KDE_Versions]Building KDE3 or KDE2] | ||
| + | * [[Getting_Started/Using Project Neon to contribute to KDE|Project Neon on Kubuntu]] | ||
| + | * [[Getting_Started/EasyStartDevelopmentOnDebian|Debian]] | ||
* [[/FreeBSD|FreeBSD]] | * [[/FreeBSD|FreeBSD]] | ||
* [[/Windows|Microsoft Windows]] | * [[/Windows|Microsoft Windows]] | ||
* [[/Mac_OS_X|Apple Mac OS X]] | * [[/Mac_OS_X|Apple Mac OS X]] | ||
| − | + | * [[Getting_Started/Build/KDE4/on_virtual_machines|On a Virtual Machine]]. | |
| − | + | ||
| − | + | ||
| − | * | + | |
| − | + | ||
== Build Environment == | == Build Environment == | ||
The KDE Build System requires certain environment settings before it can build KDE software. There are also further shortcut settings you can configure to make your like easier. You can find the details of these on the [[../Environment|Build Environment]] page. | The KDE Build System requires certain environment settings before it can build KDE software. There are also further shortcut settings you can configure to make your like easier. You can find the details of these on the [[../Environment|Build Environment]] page. | ||
| − | ==Qt== | + | == Build Requirements == |
| + | Building and running KDE software requires a number of supporting tools and libraries to be installed on your system. You can find the details of these on the [[../Requirements|Build Requirements]] page. | ||
| + | |||
| + | == Qt == | ||
''In each installation scenario above, Qt is installed in the most appropriate way.'' For your reference, there are three ways to install it: | ''In each installation scenario above, Qt is installed in the most appropriate way.'' For your reference, there are three ways to install it: | ||
| Line 34: | Line 36: | ||
; Main Qt | ; Main Qt | ||
: Get it straight from Nokia, experience the latest cool features and bugfixes (and regressions!). Bear in mind though, that applications which reside in master can only depend on a certain "highest" Qt version. This is because distributions either lag behind, or it is at an awkward time in the KDE Release Schedule, which could end up granting us a loss in stability. Other applications, like KDevelop, Amarok, and applications in playground, etc. have their own rules. | : Get it straight from Nokia, experience the latest cool features and bugfixes (and regressions!). Bear in mind though, that applications which reside in master can only depend on a certain "highest" Qt version. This is because distributions either lag behind, or it is at an awkward time in the KDE Release Schedule, which could end up granting us a loss in stability. Other applications, like KDevelop, Amarok, and applications in playground, etc. have their own rules. | ||
| − | |||
== Building The Source == | == Building The Source == | ||
| Line 51: | Line 52: | ||
== Troubleshooting the build == | == Troubleshooting the build == | ||
| − | See [[ | + | See [[../Troubleshooting|Troubleshooting]] |
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. | 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. | ||
| Warning |
|---|
| 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. |
Contents |
Languages: عربي | Asturianu | Català | Česky | Kaszëbsczi | Dansk | Deutsch | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | Galego | Italiano | 日本語 | 한국어 | Norwegian | Polski | Português Brasileiro | Română | Русский | Svenska | Slovenčina | Slovenščina | српски | Türkçe | Tiếng Việt | Українська | 简体中文 | 繁體中文
Here you will find instructions for compiling and installing KDE from source and suggestions for when compilation doesn't go so smoothly.
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:
The KDE Build System requires certain environment settings before it can build KDE software. There are also further shortcut settings you can configure to make your like easier. You can find the details of these on the Build Environment page.
Building and running KDE software requires a number of supporting tools and libraries to be installed on your system. You can find the details of these on the Build Requirements page.
In each installation scenario above, Qt is installed in the most appropriate way. For your reference, there are three ways to install it:
See Troubleshooting
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 review your logs and do searches for fixes. If you cannot find a solution, try Build/KDE4/Errors, the IRC channel, and the mailing lists. You can post your detailed issue from Build/Stories.