Revision as of 06:52, 13 July 2010 by AaronPeterson (talk | contribs) (→Troubleshooting the build)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) Contents 1 Getting_Started 2 Determine Your Needs 2.1 Version 2.2 Location 2.3 Method 3 Getting the Source 4 Troubleshooting the build 5 Using your KDE 6 Set up Development Tools 7 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. Version For production use, we recommend using a stable version of KDE. You may be able to do just fine with your distribution packages. If you need to build it yourself You will probably want the latest stable version for which you have the ,prerequisites or build requirementsfor your distribtion. For developers, The TRUNK is the main branch where new features (and prerequisites) are added, however it can be difficult to keep up with. Other versions and FAQ Including information for building on non-linux systems Incl KDE3 To See which versions/branches of KDE are available go to: http://websvn.kde.org/branches/KDE/ Location It is possible to install KDE in a variety of ways. Instructions should be listed with each build method, however much is common between methods and reading all may be requied. development user home This is a common way to do it so that it does not interefere with the rest of your system. A common user name is kde-devel. This is recommended for most testers and developers. your home directory Useful on development machines, or if you have no other access to the machine, however it can be confusing to set environment variables, however there are other advantages. and some scripts to help you use it. system-wide on development builds, do it to test KDM and other system level KDE functionality. Obviously desired for production use. If you are just testing KDM, you may want to use a virtual machine so you do not damage a production system. Method Regardless of method chosen, reading up on the manual steps below will be very helpful. CMake may also be of interest. distribution specific If you use Kubuntu, consider Project Neon, where you may be able to download recent-enough Trunk Kubuntu packages and build enviornment. kdesrc-build This script will do most of the downloading and compiling for you. There are good instructions at http://kdesrc-build.kde.org You can configure kdesrc-build to build most versions. 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 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 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=52563" Category: Build KDE Content is available under Creative Commons License SA 4.0 unless otherwise noted.