Difference between revisions of "Getting Started"

Jump to: navigation, search
(Contribution)
m (Reverted edits by Ipodsoft (talk) to last revision by AnneW)
(82 intermediate revisions by 15 users not shown)
Line 1: Line 1:
{{Template:I18n/Language Navigation Bar|Getting_Started}}
+
<languages />
 +
<translate>
  
== Determine Your Needs==
+
<!--T:1-->
KDE versions are split into branches off of the Trunk. The steps to build most branches are very similar. However, each branch has different [[Getting_Started/Build/KDE4/Prerequisites|prerequisites]].  
+
{{Warning|These pages are currently being completely re-written to reflect the new KDE infrastructure and may not be in a consistent state. Information and commands on some page may no longer be valid and should be used with care.}}
  
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).
+
== Introduction == <!--T:3-->
  
Our content is generally written with KDE4 and Linux in mind. For Windows, BSD, and KDE3 look at the [[Getting_Started/Build|other Supported Platforms]] page.
+
<!--T:4-->
 +
There are many different ways to become involved in the KDE Community, ranging all the way from a simply using our software through to being a core platform developer.
  
== [[Choose Version]] ==
+
<!--T:5-->
; Distribution synchronized
+
You can find more general information on getting involved in KDE at the following links:
: To ease finding dependencies, See [[Distributions with KDE]], or you may have a requirement to support a version supplied by a vendor.
+
* [http://kde.org/community/getinvolved/ Getting Involved in KDE]
; Latest Features for production
+
* [[Special:myLanguage/Contribute|Contribute to KDE]]
: [[branch]] (stable / beta)
+
; Core Development
+
: [[trunk]] Where new features grow (may have build problems on Mondays)
+
  
;Browse availability:
+
<!--T:6-->
:http://websvn.kde.org/branches/KDE/
+
This section of KDE TechBase is designed to help get you started in participating in the technical side of the KDE community. It will explain to you how KDE Software is structured and built, and how you can participate by building KDE for yourself.
  
== Choose Location ==
+
<!--T:7-->
Choose where you want to put the KDE installation, and keep source and build directories.
+
{{Note|'''Quickstart:''' If you are impatient to get started without understanding what you are doing then you can skip straight to using a [[Special:myLanguage/Getting_Started/Build#Scripted_Builds|Build Script]], but it is strongly recommended you read this documentation first.}}
(The [[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 home directory of the user who runs KDE)
+
: possibly /usr/src/  if [[building as root]].
+
  
===Installation Directory===
+
== Using KDE Software == <!--T:8-->
;[[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 separate (using [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|scripts]]) or have no other access to the machine
+
: [[As root]] not advised unless you have a dedicated machine
+
  
; [[Application Developer]]
+
<!--T:9-->
: [[development user home]] same as for curious user
+
If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself.  You should instead use the software installer provided by your Linux distribution to install KDE package.
: [[as root]] will be more useful to simulate environment of customers
+
: [[your home directory]] may simplify your development
+
  
; [[Distribution Manager]]
+
<!--T:10-->
: To test KDM, you may want to install [[as root]] and/or on a [[Getting_Started/Build/KDE4/on_virtual_machines|virtual machine]] so you do not damage a production system.
+
The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
 +
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
 +
* [[Special:myLanguage/Getting_Started/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
 +
* [[Special:myLanguage/Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
 +
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]
  
; [[Contributor]]
+
== Getting Help == <!--T:11-->
: keeping your system similar to other developers will help make troubleshooting easier, see [[Developer Setups]]
+
  
== Gather Prerequisites ==
+
<!--T:12-->
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.
+
If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].  
  
* [[Getting_Started/Build/KDE4/Prerequisites]]
+
<!--T:13-->
* [[build requirements]] by distribution
+
If you have any questions or problems with building or developing KDE Software please feel free to [[Special:myLanguage/Development/Getting_Help|ask for help]].  However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you.  Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.
  
===Qt ===
+
== Browsing the code == <!--T:28-->
; System Qt
+
The KDE project is all free and open source. You can view its source code and make changes.
: Often the easiest way to go, because most people have it already, you may have to install the QCA plugin as root though.
+
  
; KDE-Qt
+
<!--T:29-->
:Previously known as qt-copy -- This is the minimum version of Qt any of your users are expected to have. Some bugs may be fixed in new Qt, so you may have to work-around bugs in lower versions, including this one.
+
http://projects.kde.org hosts the source for many KDE-related initiatives, including [https://projects.kde.org/projects/kde KDE itself].  Choose a piece of KDE such as KDE Libraries, then click Repository to browse its source. [[Getting_Started/Sources]] explains the organization of KDE source code.
  
; Main Qt
+
<!--T:30-->
: Get it straight from Nokia, experience the latest cool features, but note that many people will be using older distributions with older Qt.
+
There are other utilities to browse the source code:
  
==Getting the Source==
+
<!--T:31-->
We are migrating from SVN to git.  We have extensive infrastructure that is being converted, but please know that this is a much anticipated, complex, and popular change. http://www.omat.nl/2010/07/07/move-to-git-the-progress-so-far/
+
* http://lxr.kde.org/search lets you search the code ''(may be out of date?)''
 +
* http://api.kde.org lets you browse API documentation generated from the code. You can search for class names, but not filenames.
  
[[Image:Action_down.svg|right|32px]]
+
== Building and Running KDE Software From Source == <!--T:14-->
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]
+
* [[Getting_Started/Sources/Using Subversion with KDE|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.''
+
* [[Getting_Started/Sources/Amarok Git Tutorial|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.''
+
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]
+
* [http://websvn.kde.org/ Browse code online], or [http://lxr.kde.org/search search the code]
+
  
== Build it ==
+
<!--T:15-->
 +
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.  In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so.  You can read more about this on the [[Special:myLanguage/Getting_Started/Build/Methods|Build Methods page]].
  
 +
<!--T:33-->
 +
If you simply want to build one application, the simple tutorial [[Development/Tutorials/Building_An_Existing_Application|Building an Existing Application]] might be enough already.
  
; Manual Steps
+
<!--T:32-->
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]
+
<!-- what about https://launchpad.net/project-neon that used to be linked here in 2010, does that still apply? - User:Skierpage -->
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Stable version or 4.x SVN BRANCH)]]
+
* [[Getting_Started/Build/KDE4.x Upgrade|Upgrade KDE-4.x.y release version or KDE-4.x SVN BRANCH)]]
+
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''
+
  
; augmented with bash functions.
+
<!--T:16-->
:[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts]]
+
The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:
:Specific examples:[[Build KDE4.6 on Kubuntu]]
+
  
; distribution specific
+
<!--T:17-->
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.
+
* [[Special:myLanguage/Getting_Started/Sources|How the KDE Source Code is structured]]
 +
* [[Special:myLanguage/Getting_Started/Build|How to Build and Install the software]]
 +
* [[Special:myLanguage/Getting_Started/Run/Nested_Session|How to Run a nested session of KDE]]
 +
* [[Special:myLanguage/Getting_Started/Run/Full_Session|How to Run a full session of KDE]]
  
; kdesrc-build
+
== Development Model == <!--T:18-->
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 [[Getting_Started/Build/kdesrc-build|kdesrc-build]], and here is a list of [[kdesrc-build/workingrclist|working configuration files]].
+
  
=== Troubleshooting the build ===
+
<!--T:19-->
* [[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]]
+
TODO: General introduction to the dev model, release cycles, etc.
  
[[Getting_Started/Build/KDE4/Troubleshooting|Troubleshooting]] information is similar between branches as well.
+
<!--T:20-->
 +
* [[Special:myLanguage/Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
 +
* [[Special:myLanguage/Development/Software_Engineering_Framework|The KDE Software Engineering Framework]]
 +
* [[Special:myLanguage/Policies|KDE Development Policies and Procedures to follow]]
 +
* [[Special:myLanguage/Policies/Application_Lifecycle|The development lifecycle for a new application]]
  
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. 
+
== Development Tools == <!--T:21-->
  
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. [[Build/Stories]]
+
<!--T:22-->
 +
There are a number of [[Special:myLanguage/Development/Tools|Development Tools]] that are either required or helpful when building KDE Software.  For these you will usually want to use the stable packages provided by your distribution.
  
==Using your KDE==
+
<!--T:23-->
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:
+
You may want to use a graphical IDE for your development work:
=== Environment Variables ===
+
* [[Special:myLanguage/Development/Tutorials/Using_Qt_Creator|Qt Creator]]
Your system won't know to use your new KDE until you tell it how to find the KDE applications and libraries.
+
* [http://www.kdevelop.org/ KDevelop 4]
[[Image:Action_pen.svg|right|32px]]
+
* [[Special:myLanguage/Development/Tools/Eclipse|Eclipse]]
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]
+
* [[Special:myLanguage/Getting_Started/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]
+
  
===Set up Development Tools===
+
== Contributing To KDE == <!--T:24-->
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
+
<!--T:25-->
 
+
Once you have a copy of KDE built you can then start contributing back to KDEThe pages below will help you find out how you can help make KDE even better.
For most development topics, and documentation, see [[Development]]
+
 
+
; Opening and creating KDE project files
+
* [[eclipse]]
+
* [[kdevelop]]
+
* [[Development/Tutorials/Using_Qt_Designer|qtdesigner]]
+
 
+
+
This is a stub, please help.
+
 
+
===Contribution===
+
You may not need the latest bleeding-edge version of KDE with which to developMuch of the code will be similar between versions and your patch might work.  However, Trunk is where major changes are introduced, and branches are mostly for maintenance/bug fixes.
+
  
 +
<!--T:26-->
 
[[Image:Action_tool.svg|right|32px]]
 
[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
+
* [[Special:myLanguage/Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
+
* [[Special:myLanguage/Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]
+
* [[Special:myLanguage/Contribute/Bugsquad|Bugsquad]]
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]
+
* [[Getting_Started/EasyStartDevelopmentOnDebian | Build, change and run packaged KDE applications on Debian]]
+
  
 +
<!--T:27-->
 
[[Category:Build_KDE]]
 
[[Category:Build_KDE]]
 +
</translate>

Revision as of 18:12, 4 November 2012

Other languages:Greek 62% • ‎English 100% • ‎Finnish 62% • ‎French 98% • ‎Japanese 76% • ‎Korean 86% • ‎Dutch 78% • ‎Brazilian Portuguese 100% • ‎Russian 73% • ‎Turkish 46% • ‎Chinese (China) 47%
noframe
 
Warning
These pages are currently being completely re-written to reflect the new KDE infrastructure and may not be in a consistent state. Information and commands on some page may no longer be valid and should be used with care.


Contents

Introduction

There are many different ways to become involved in the KDE Community, ranging all the way from a simply using our software through to being a core platform developer.

You can find more general information on getting involved in KDE at the following links:

This section of KDE TechBase is designed to help get you started in participating in the technical side of the KDE community. It will explain to you how KDE Software is structured and built, and how you can participate by building KDE for yourself.

noframe
 
Note
Quickstart: If you are impatient to get started without understanding what you are doing then you can skip straight to using a Build Script, but it is strongly recommended you read this documentation first.

Using KDE Software

If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself. You should instead use the software installer provided by your Linux distribution to install KDE package.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:

Getting Help

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the KDE UserBase.

If you have any questions or problems with building or developing KDE Software please feel free to ask for help. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it all for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

Browsing the code

The KDE project is all free and open source. You can view its source code and make changes.

http://projects.kde.org hosts the source for many KDE-related initiatives, including KDE itself. Choose a piece of KDE such as KDE Libraries, then click Repository to browse its source. Getting_Started/Sources explains the organization of KDE source code.

There are other utilities to browse the source code:

Building and Running KDE Software From Source

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. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the Build Methods page.

If you simply want to build one application, the simple tutorial Building an Existing Application might be enough already.


The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

Development Model

TODO: General introduction to the dev model, release cycles, etc.

Development Tools

There are a number of Development Tools that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:

Contributing To KDE

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

Action tool.svg

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal