Getting Started/Build/KDE4 (fi) - Revision history

AnneW at 13:54, 18 July 2012

2012-07-18T13:54:26Z

Neverendingo: Text replace - "" to ""

2011-06-29T20:51:01Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:47:01Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:47, 29 June 2011
			
Line 250:
Line 250:
  Many modules in KDE contain a large number of programs which could take a long time to download and compile. In cases where you want to work only on a particular program or programs in a module, it is possible to download and compile particular folders. In some cases, certain folders are required for any build of the module. This is determined in the CMakeLists.txt file of the module. For example the [http://websvn.kde.org/branches/KDE/4.0/kdegames/CMakeLists.txt?view=markup kdegames CMakeLists.txt file] lists:   Many modules in KDE contain a large number of programs which could take a long time to download and compile. In cases where you want to work only on a particular program or programs in a module, it is possible to download and compile particular folders. In some cases, certain folders are required for any build of the module. This is determined in the CMakeLists.txt file of the module. For example the [http://websvn.kde.org/branches/KDE/4.0/kdegames/CMakeLists.txt?view=markup kdegames CMakeLists.txt file] lists:
    
− <code> + <syntaxhighlight lang="text">
  add_subdirectory(libkdegames)   add_subdirectory(libkdegames)
  add_subdirectory(libkmahjongg)   add_subdirectory(libkmahjongg)



Neverendingo: Text replace - "" to ""

2011-06-29T20:41:03Z
Text replace - "<code bash>" to "<syntaxhighlight lang="bash">"

				
				
				
				
			
			← Older revision
			Revision as of 20:41, 29 June 2011
			
Line 39:
Line 39:
  On Ark Linux and Fedora, you can skip the <tt>-s /bin/bash</tt> switch - {{path|/bin/sh}} is {{path|bash}}.   On Ark Linux and Fedora, you can skip the <tt>-s /bin/bash</tt> switch - {{path|/bin/sh}} is {{path|bash}}.
  }}   }}
− <code bash> + <syntaxhighlight lang="bash">
  useradd -m kde-devel -s /bin/bash   useradd -m kde-devel -s /bin/bash
  passwd kde-devel   passwd kde-devel
Line 57:
Line 57:
  Copy the {{path|~/.bashrc}} from your normal user account to the new kde-devel account. Next, copy and paste the contents of the [[Getting Started/Increased Productivity in KDE4 with Scripts/.bashrc|example .bashrc]] into {{path|~kde-devel/.bashrc}}. Be sure to comment out the line <tt>alias make=makeobj</tt> if you do not have the <tt>[[Getting Started/Build/KDE4#Required Software|makeobj]]</tt> command available. Alternatively, you can download the kde-sdk package (or perform a subversion checkout) and include the kde-sdk/scripts/ directory in your path. You will probably also want to modify the path to make sure it doesn't include your kde3 paths. Also if you want to use KDevelop to develop KDE 4 applications you may pass the ''-GKDevelop3'' flag to the ''cmake'' command (to make CMake generate KDevelop project files, it will help to avoid rebuilding in the future, see [[Getting_Started/Set_up_KDE_4_for_development#Setting_up_the_environment|this]]).      Copy the {{path|~/.bashrc}} from your normal user account to the new kde-devel account. Next, copy and paste the contents of the [[Getting Started/Increased Productivity in KDE4 with Scripts/.bashrc|example .bashrc]] into {{path|~kde-devel/.bashrc}}. Be sure to comment out the line <tt>alias make=makeobj</tt> if you do not have the <tt>[[Getting Started/Build/KDE4#Required Software|makeobj]]</tt> command available. Alternatively, you can download the kde-sdk package (or perform a subversion checkout) and include the kde-sdk/scripts/ directory in your path. You will probably also want to modify the path to make sure it doesn't include your kde3 paths. Also if you want to use KDevelop to develop KDE 4 applications you may pass the ''-GKDevelop3'' flag to the ''cmake'' command (to make CMake generate KDevelop project files, it will help to avoid rebuilding in the future, see [[Getting_Started/Set_up_KDE_4_for_development#Setting_up_the_environment|this]]).   
  To make it run, you have to open a new bash or to execute     To make it run, you have to open a new bash or to execute  
− <code bash> + <syntaxhighlight lang="bash">
  source ~/.bashrc   source ~/.bashrc
  </code>   </code>
Line 67:
Line 67:
  === Vaihdetaan uuteen käyttäjään ===   === Vaihdetaan uuteen käyttäjään ===
  Switch to the user kde-devel:   Switch to the user kde-devel:
− <code bash> + <syntaxhighlight lang="bash">
  ssh -X kde-devel@localhost   ssh -X kde-devel@localhost
  </code>   </code>
Line 192:
Line 192:
  :This contains things specific to the KDE desktop, like Plasma or the window manager. Most stuff here depends on X11. You only need it if you want to build a full KDE desktop.   :This contains things specific to the KDE desktop, like Plasma or the window manager. Most stuff here depends on X11. You only need it if you want to build a full KDE desktop.
    
− You can build all of kdebase at once, which is described in the recipe below. If you only want to build kdebase-runtime, which is the only requirement, you can replace <code bash>cd kdebase</code> with <code bash>cd kdebase/runtime</code> in the recipe below. + You can build all of kdebase at once, which is described in the recipe below. If you only want to build kdebase-runtime, which is the only requirement, you can replace <syntaxhighlight lang="bash">cd kdebase</code> with <syntaxhighlight lang="bash">cd kdebase/runtime</code> in the recipe below.
    
  === Valmistusohje ===   === Valmistusohje ===
Line 237:
Line 237:
    
  For example:   For example:
− <code bash> + <syntaxhighlight lang="bash">
  cs kdesupport # cs is not a typo   cs kdesupport # cs is not a typo
  svn up   svn up
Line 261:
Line 261:
  So, the libkdegames and libkmahjongg directories are required to build any of kdegames. The cmake directory will also usually be required. All the other directories (doc, katomic etc) are optional. They will be built if present on your machine. In this example, we build kmahjongg and kbattleship:   So, the libkdegames and libkmahjongg directories are required to build any of kdegames. The cmake directory will also usually be required. All the other directories (doc, katomic etc) are optional. They will be built if present on your machine. In this example, we build kmahjongg and kbattleship:
    
− <code bash> + <syntaxhighlight lang="bash">
  cs KDE   cs KDE
  svn co -N svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames # The -N switch performs a non-recursive checkout   svn co -N svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames # The -N switch performs a non-recursive checkout



Centerlink: Still translating part of text.
2009-11-03T12:24:44Z
Still translating part of text.

				
				
				
				
			
			← Older revision
			Revision as of 12:24, 3 November 2009
			
Line 7:
Line 7:
  name=Building KDE4 (Development version, TRUNK) From Source|   name=Building KDE4 (Development version, TRUNK) From Source|
    
− pre=[[../../Sources/Anonymous_SVN|Anonyymi SVN-pikaohje]]| + pre=[[../../Sources/Anonymous_SVN_(fi)|Anonyymi SVN-pikaohje]]|
    
  next=[[../../Set_up_KDE_4_for_development|Aseta KDE 4-kehitysympäristö]]|   next=[[../../Set_up_KDE_4_for_development|Aseta KDE 4-kehitysympäristö]]|
Line 16:
Line 16:
  == Yhteenveto ==   == Yhteenveto ==
    
− This tutorial shows one way to get KDE from trunk running on Linux/BSD systems. There are also tutorials for [[Getting_Started/Build/KDE4/FreeBSD|FreeBSD]], [[/Windows|Windows]], [[/Mac OS X|Mac OS X]] and [http://solaris.kde.org/ Solaris]. This tutorial creates a special user, kde-devel, that will run KDE trunk. On the one hand, this allows other users to continue with another KDE version. On the other hand, testing special system-wide code like the KDE display manager is not possible. There is a tutorial to + Tämä kurssi esittää yhden tavan hakea KDE-versionhallinnan trunk-haara suoritettavaksi Linux/BSD-järjestelmissä. On olemassa myös kursseja [[Getting_Started/Build/KDE4/FreeBSD|FreeBSD:lle]], [[/Windows|Windowsille]], [[/Mac OS X|Mac OS X:lle]] and [http://solaris.kde.org/ Solarikselle]. Tämä kurssi luo erikoiskäyttäjän, kde-devel, joka suorittaa KDE-trunk-version. Toisaalta erityisen järjestelmänlaajuisen kuten esimerkiksi KDE-näyttöhallintakoodin testaus ei ole mahdollista. On olemassa myös kurssi [[Getting_Started/Build/KDE4/onVmWare|KDE 4 trunk-version asettamisesta virtuaalikoneeseen]].  
− [[Getting_Started/Build/KDE4/onVmWare|set up KDE 4 trunk on a virtual machine]]. + 
    
  Throughout the tutorial the bash shell is used.   Throughout the tutorial the bash shell is used.



Centerlink: Preliminary and still partly Finnish translation.
2009-11-03T11:26:41Z
Preliminary and still partly Finnish translation.
New page
{{Template:I18n/Language Navigation Bar|Getting_Started/Build/KDE4}}



{{TutorialBrowser|



series=Getting Started|



name=Building KDE4 (Development version, TRUNK) From Source|



pre=[[../../Sources/Anonymous_SVN|Anonyymi SVN-pikaohje]]|



next=[[../../Set_up_KDE_4_for_development|Aseta KDE 4-kehitysympäristö]]|



reading=[[../kdesvn-build|kdesvn-build: The KDE From Subversion Build Tool]]<br>[[Contribute/Send Patches|Sending Patches]]<br>[[../../Increased_Productivity_in_KDE4_with_Scripts|Increased Productivity in KDE4 with Scripts]]<br>[[Development/Tutorials/CMake |Introduction to CMake]]<br>[[../KDE4/FreeBSD|FreeBSD notes]]<br>[[../KDE4/Mac OS X|Instructions for Mac OS X]]<br>[[../KDE4/Windows|Instructions for MS Windows]]|

}}



== Yhteenveto ==



This tutorial shows one way to get KDE from trunk running on Linux/BSD systems. There are also tutorials for [[Getting_Started/Build/KDE4/FreeBSD|FreeBSD]], [[/Windows|Windows]], [[/Mac OS X|Mac OS X]] and [http://solaris.kde.org/ Solaris]. This tutorial creates a special user, kde-devel, that will run KDE trunk. On the one hand, this allows other users to continue with another KDE version. On the other hand, testing special system-wide code like the KDE display manager is not possible. There is a tutorial to

[[Getting_Started/Build/KDE4/onVmWare|set up KDE 4 trunk on a virtual machine]].



Throughout the tutorial the bash shell is used.



{{warning|Expect a higher risk of build failure '''on Mondays''' when most kdelibs changes are committed. [http://developer.kde.org/~dirk/dashboard/ Dashboard] reports unexpected breakages. You are encouraged to fix failing modules.}}



== Luo käyttäjätili KDE4-kehitykseen ==



{{Note|

Some people like to have a separate user account for KDE 4 (for instance an old bug deleted files by mistake), and the instructions below were written with that approach.



However it is much more efficient to do everything with a single user account, see [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts|Increased Productivity in KDE4 with Scripts]]

for more details. 



You can still follow the instructions below, but don't put the environment variables in your <tt>.bashrc</tt>, put them in a separate file that you source to switch to the KDE 4 environment.

}}





=== Vaihtoehto 1: Komentorivi ===

{{Note|

On some systems a new user is configured by default to use {{path|/bin/sh}}. Using {{path|/bin/sh}} can be very inconvenient to work with and you may want to change it to {{path|/bin/bash}} or another shell.

On Ark Linux and Fedora, you can skip the <tt>-s /bin/bash</tt> switch - {{path|/bin/sh}} is {{path|bash}}.

}}

<code bash>

useradd -m kde-devel -s /bin/bash

passwd kde-devel

</code>





{{Warning|

The new kde-devel user will not be added automatically to all the user groups, which will result in not having sound, not being able to sudo, etc. Edit your /etc/groups file to add the kde-devel user to all the groups that you need (probably the groups that your usual username is already assigned to).

}}



=== Vaihtoehto 2: Käytetään KControl-ohjelmaa ===



Instead of using the commands above, you can also use the User module in the KDE Control Center if you already have KDE3 installed.



=== Ympäristön asettaminen ===



Copy the {{path|~/.bashrc}} from your normal user account to the new kde-devel account. Next, copy and paste the contents of the [[Getting Started/Increased Productivity in KDE4 with Scripts/.bashrc|example .bashrc]] into {{path|~kde-devel/.bashrc}}. Be sure to comment out the line <tt>alias make=makeobj</tt> if you do not have the <tt>[[Getting Started/Build/KDE4#Required Software|makeobj]]</tt> command available. Alternatively, you can download the kde-sdk package (or perform a subversion checkout) and include the kde-sdk/scripts/ directory in your path. You will probably also want to modify the path to make sure it doesn't include your kde3 paths. Also if you want to use KDevelop to develop KDE 4 applications you may pass the ''-GKDevelop3'' flag to the ''cmake'' command (to make CMake generate KDevelop project files, it will help to avoid rebuilding in the future, see [[Getting_Started/Set_up_KDE_4_for_development#Setting_up_the_environment|this]]).  

To make it run, you have to open a new bash or to execute 

<code bash>

source ~/.bashrc

</code>



This will provide access to commands such as <tt>cmakekde</tt> that are used in this tutorial as well as ensure that the proper paths are in place for Qt, KDE and CMake binaries.



For more information, please read the [[Getting Started/Increased Productivity in KDE4 with Scripts]] tutorial.



=== Vaihdetaan uuteen käyttäjään ===

Switch to the user kde-devel:

<code bash>

ssh -X kde-devel@localhost

</code>



{{Note|

If the ssh command fails, check out the [[Getting_Started/Set_up_KDE_4_for_development#Launching_KDE_4_apps|Launching KDE 4 apps]] section of the [[Getting_Started/Set_up_KDE_4_for_development|KDE4 development guide]].

}}



== Jakeluversiostasi vaaditut pakkaukset ==

The requirements to build kde4 from source vary from distribution to distribution. Instructions for your distribution are provided below:



* [[Getting_Started/Build/KDE4/Ark Linux|Ark Linux]]

* [[Getting_Started/Build/KDE4/Arch Linux|Arch Linux]]

* [[Getting_Started/Build/KDE4/Fedora|Fedora]]

* [[Getting_Started/Build/KDE4/Kubuntu and Debian|Kubuntu and Debian]]

* [[Getting_Started/Build/KDE4/openSUSE|openSUSE]] Note: there is a [http://en.opensuse.org/KDE/Developing/Guide specific guide for openSUSE]. However be careful because it updates a huge number of your stable packages.

* [[Getting_Started/Build/KDE4/Gentoo|Gentoo]]

* [[Getting_Started/Build/KDE4/LFS|Linux from Scratch]] or to build from source.

* [[Getting_Started/Build/KDE4/Mandriva|Mandriva]]



* [[Getting_Started/Build/KDE4/Generic|any other distro]]



Your next compilation step depends on the packages supplied by your distro.



=== Käännetään kde-qt, jne. ===

If you do not want to use the packages provided by your distro you can compile things like Qt yourself. Instructions for building all dependencies including CMake, Qt4 (kde-qt) and kdesupport are available in [[Getting_Started/Build/KDE4/Prerequisites|the build prerequisites page]].  Note that automoc, phonon, strigi, soprano, and a few other things are part of kdesupport, so if you have errors about these missing, you'll need to get kdesupport.



== KDE:n rakentaminen kehitys- tai stabiiliversiokäyttöön ==



The commands below are used to build the latest unstable version of KDE from trunk. This should not be used in a production environment -- not recommended for daily use.



Stabiilin version rakentamiseksi mene:



[[Getting_Started/Build/KDE4.x|Building KDE4.x]]



=== Hyödyllisiä subversion-säätöjä ===



{{Warning|Do not use this method when you don't know what you are doing or just want to test some trunk feature, seriously! 

You can create a very costly load when you accidentially checkout all of trunk or for example all of "trunk/KDE" just to build single modules. This would generate immense useless load on the svn server.}}



If you check out large parts of svn trunk regularly or if you want to create patches which touch several modules at once, you should try to checkout an empty tree of trunk first and then update only the relevant modules, for example:



==== Esimerkki ====

 cd

 cs # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]

 svn checkout --depth empty svn://anonsvn.kde.org/home/kde/trunk

 cd trunk

 svn up kdesupport && cd kdesupport

 cmakekde

 cs trunk

 svn up --depth empty KDE

 svn up KDE/kdelibs && cd KDE/kdelibs

 cmakekde

 cs trunk

 svn up KDE/kdepimlibs

 ...



==== Miksi haluan tehdä tuon? ====

That way you can move stuff around all over the trunk repository, e.g. from playground to kdereview or to KDE/*. The following examples assume that you only want to test or work on single and few modules of trunk. 



This way updating the whole repository to a (hopefully) consitent state, the same revision, is really easy:



 cs trunk # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]

 svn up



== kdelibs ==



We can now move on to building KDE's base libraries.



=== Valmistusohje ===

 cd   

 cs # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]

 mkdir KDE && cd KDE

 svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs

 cd kdelibs

 cmakekde



=== Mitä tapahtuu ===

We change to the base source directory (line 1) then make and go into the KDE directory (line 3). We download the sources for kdelibs using subversion (line 4), go into the new {{path|~/kde/src/KDE/kdelibs}} directory (line 5), and commence the build (line 6). This will leave us in the <tt>kdelibs</tt> build directory after the build is completed.



{{tip|There might be missing dependencies on your system! They are easily overlooked in the output of <tt>cmakekde</tt>.

You might want to do a <tt>cmake $KDE_SRC/KDE/MODULE_NAME</tt> prior to compiling any kde modules (like kdelibs, kdepimlibs etc.)}}



=== Lisää KDE-kohtaista CMake-taitotietoutta ===



There are additional CMake modules in {{path|kdelibs/cmake/modules/}} that are necessary for building KDE4 applications. These will be installed for you when  kdelibs itself is installed.



To make a non-debug-release (e.g. suppressing all kDebug() messages), use e.g.

 cmake -DCMAKE_BUILD_TYPE=Release . && make && make install



=== Virheidenjäljitys ===



For troubleshooting information, see the [[Getting_Started/Build/KDE4/Troubleshooting#Issues_building_kdelibs|kdelibs troubleshooting section]].



== kdepimlibs ==

Currently kdebase depends on kdepimlibs so it is required to install it first. These libraries are also shared by other packages such as those within kdepim, kdeutils and kdenetwork.



=== libical ===

Download libical from http://sourceforge.net/project/showfiles.php?group_id=16077, compile, link and install it.

 tar xvzf libical-0.41.tar.gz

 cd libical-0.41

 ./configure && make && make install



=== Valmistusohje ===

 cs KDE # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]

 svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs

 cd kdepimlibs

 cmakekde



=== Mitä tapahtuu ===

We go into the KDE source directory (line 1), download the source code for kdepimlibs using subversion (line 2) and then go into the new {{path|~/kde/src/KDE/kdepimlibs}} directory (line 3). We then commence the build (line 4). This will leave us in the <tt>kdepimlibs</tt> build directory after the build is completed.



=== Virheidenjäljitys ===



For troubleshooting information, see the [[Getting_Started/Build/KDE4/Troubleshooting#Issues_building_kdepimlibs|kdepimlibs troubleshooting section]].



== kdebase ==

kdebase is divided into three parts:

* '''apps'''

:This contains applications like Dolphin or KWrite.

* '''runtime'''

:This contains things needed by every application at runtime, like icons. It is a required dependency for each KDE application, so you have to compile and install this.

* '''workspace'''

:This contains things specific to the KDE desktop, like Plasma or the window manager. Most stuff here depends on X11. You only need it if you want to build a full KDE desktop.



You can build all of kdebase at once, which is described in the recipe below. If you only want to build kdebase-runtime, which is the only requirement, you can replace <code bash>cd kdebase</code> with <code bash>cd kdebase/runtime</code> in the recipe below.



=== Valmistusohje ===

 cs KDE # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]

 svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase

 cd kdebase

 cmakekde



=== Virheidenjäljitys ===

For troubleshooting information, see the [[Getting_Started/Build/KDE4/Troubleshooting#Issues_building_kdebase|kdebase troubleshooting section]].



== Paikallistamiset ==



Most KDE users are going to install translations before being able to use their desktop properly. Full information is given in the Localisation tutorial at [[Development/Tutorials/Localization/Building_KDE's_l10n_Module]].

For a single language, the following receipe installs messages and translated documentation:



=== Valmistusohje ===

 cs KDE # [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|'cs' is a bash function, click here to learn more]]

 svn checkout -N svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4

 cd l10n-kde4

 svn checkout scripts <language>

 ./scripts/autogen.sh <language>

 cd <language>

 cmakekde





== KDE 4-ohjelmien suorittaminen ==



Voit nyt suorittaa KDE 4-ohjelmia (esim.: kwrite) kirjoittamalle:

 ssh -X kde-devel@localhost

 kwrite 



=== Virheidenjäljitys ===



For troubleshooting issues see [[Getting_Started/Build/KDE4/Troubleshooting#Running_programs|troubleshooting running programs]].



== Paikallisten API-dokumenttien luominen ==



See the [[Development/Tools/apidox|generating apidox]] page.



== Ajantasalla pysyminen ==



In order to keep the kde4 installation up to date, each of the modules installed should be updated periodically. As Monday is the day for big changes in kdelibs, Tuesday may be the best day to do this. For each module checked out, run <tt>svn up</tt> and <tt>make</tt>.



For example:

<code bash>

cs kdesupport # cs is not a typo

svn up

cb # cb is not a typo

make install

</code>



Note: it is not necessary to run cmakekde for updates.



== Moduulin alijoukon asentaminen ==



Many modules in KDE contain a large number of programs which could take a long time to download and compile. In cases where you want to work only on a particular program or programs in a module, it is possible to download and compile particular folders. In some cases, certain folders are required for any build of the module. This is determined in the CMakeLists.txt file of the module. For example the [http://websvn.kde.org/branches/KDE/4.0/kdegames/CMakeLists.txt?view=markup kdegames CMakeLists.txt file] lists:



<code>

add_subdirectory(libkdegames)

add_subdirectory(libkmahjongg)



macro_optional_add_subdirectory(doc)

macro_optional_add_subdirectory(lskat)

macro_optional_add_subdirectory(katomic)

</code>



So, the libkdegames and libkmahjongg directories are required to build any of kdegames. The cmake directory will also usually be required. All the other directories (doc, katomic etc) are optional. They will be built if present on your machine. In this example, we build kmahjongg and kbattleship:



<code bash>

cs KDE

svn co -N svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames # The -N switch performs a non-recursive checkout

cd kdegames

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/libkdegames # Get required directories

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/libkmahjongg

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/cmake

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/kbattleship # Get optional directories

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdegames/kmahjongg

cmakekde 

</code>



== Onnistui! ==



You are now ready to start building other svn modules in the same fashion as you built kdebase, running and testing KDE4 or writing your own patches and applications.



For further isolation of your development environment change symbolic links, which you will see after executing ls -lh $(kde4-config --localprefix), assuming newly installed kde4-config is called.



See the [[Getting Started/Set up KDE 4 for development|Set up KDE 4 for development]] tutorial for how to start KDE 4 applications and how to use KDevelop to work on them.



For most of what you need to know on patches see: [[Contribute/Send Patches|Sending Patches]]



[[Category:Build KDE]]

[[Category:KDE4]]

← Older revision		Revision as of 13:54, 18 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Getting_Started/Build/KDE4}}~~	+

	{{TutorialBrowser\|		{{TutorialBrowser\|