Revision as of 03:20, 6 August 2010 by AaronPeterson (talk | contribs) (→Determine Your Needs: still awkward, but less unneeded verbage)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) Contents 1 Getting_Started 2 Determine Your Needs 2.1 Choose Version 2.2 Location 2.2.1 Source and Build Directories 2.2.2 Installation Directory 2.3 Method 3 Gather Prerequisites 4 Build it 5 Getting the Source 6 Troubleshooting the build 7 Using your KDE 8 Set up Development Tools 9 Contribution Getting_Started 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 | Українська | 简体中文 | 繁體中文 Determine Your Needs KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, Each branch has different prerequisites. You will need to know what version you want, how often you will use the development environment (more work upfront may be justified if you intend to use it more), Choose Version Synchronized with distribution Distributions with KDE may provide KDE Dev and SDK for 3rd party development Latest Features for production branch (stable / beta) Core Development trunk other Supported Platforms Including information for building on non-linux systems Incl KDE3 Older Versions To See which versions/branches of KDE are available go to: http://websvn.kde.org/branches/KDE/ Location Choose where you want to put the KDE installation, and keep source and build directories. ( QCA plugin may have to be installed as root if using system Qt)) Source and Build Directories suggested: ~/kde/src and ~/kde/build (where ~ is the user which runs KDE) possibly /usr/src/ if building as root Installation Directory Casual Curiosity development user home if you do not want to mess up your production KDE your home directory if you are willing to use environment variables to keep versions seporate( using scripts) or have no other access to the machine As root Not advised unless you have a dedicated machine Application Developer development user home same as for curious user as root will be more useful to simulate environment of customers your home directory may simplify your development Distribution Manager To test KDM, you may want to install as root and or use a virtual machine so you do not damage a production system. Method Read up on steps below. CMake may also be of interest. Fully Manual -- to learn how things work Distribution Specific Augmented (Recommended) most common method, set environment variables and use scripts. KDEsrc-build Useful for automated builds, may be tough to set up Gather Prerequisites Your build will fail if you are missing one of them, and the list changes. There are some options, however the make system can often find optional packages even if you do not intend to use them, so you may need to pass disable options. Getting_Started/Build/KDE4/Prerequisites build requirements by distribution Build it Most used method, augmented with bash functions. Getting_Started/Increased_Productivity_in_KDE4_with_Scripts Manual Steps KDE 4 (Development version, TRUNK) KDE 4.x (Stable version or 4.x SVN BRANCH) Upgrade KDE-4.4.x release version or KDE-4.4 SVN BRANCH) Other versions and FAQ Including information for building on non-linux systems distribution specific There may be pre-made builds for your distribution, For example, in Kubuntu, Project Neon, aims to provide a recent trunk build environment, and PPA's provide latest branch versions. kdesrc-build This script will do most of the downloading and compiling for you. It can be configured to build most versions, by default it builds Trunk. There full-process instructions at http://kdesrc-build.kde.org and more here kdesrc-build, and here is a list of working configuration files. This will compile qt for you, or you can configure it to use system QT When you choose a branch edit your .kdesrc-buildrc set your branch you will have to tweak the kdeSupport module description, and maybe the qt-copy. For the kdesupport module: module-base-path tags/kdesupport-for-4.5 Getting the Source Anonymous SVN Quickstart Guide Using Subversion with KDE A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches. Amarok Git Tutorial Amarok has moved to Git (with the rest of KDE to follow), so it requires different steps to check out and develop. Daily Snapshots Browse code online, or search the code Troubleshooting the build Troubleshooting Troubleshooting information is similar between branches as well. 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, Build/KDE4/Errors and IRC channel, and mailing lists. Build/Stories Using your KDE After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks: Environment Variables Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries. Increased Productivity in KDE4 with Scripts Set up KDE 4 for development Set up Development Tools You may need to set up or use, you will likely want to use a stable package from your distribution. it is unclear if the kde-devel user or your normal user will be running the development tools. Please Help For most development topics, and documentation, see Development Opening and creating KDE project files eclipse kdevelop qtdesigner This is a stub, please help. Contribution You may not need the latest bleeding-edge KDE to develop with, Much code will be similiar between versions and your patch might work, however Trunk is where major changes are introduced, and branches are mostly maintenance/bug fix. Contribute Send Patches Bugsquad Using Project Neon to contribute to KDE Retrieved from "https://techbase.kde.org/index.php?title=Getting_Started&oldid=53223" Category: Build KDE Content is available under Creative Commons License SA 4.0 unless otherwise noted.