Difference between revisions of "Getting Started/Build/KDE4 (fi)"

Jump to: navigation, search
m (Text replace - "</code>" to "</syntaxhighlight>")
Line 1: Line 1:
{{Template:I18n/Language Navigation Bar|Getting_Started/Build/KDE4}}

Latest revision as of 13:54, 18 July 2012


[edit] Yhteenveto

Tämä kurssi esittää yhden tavan hakea KDE-versionhallinnan trunk-haara suoritettavaksi Linux/BSD-järjestelmissä. On olemassa myös kursseja FreeBSD:lle, Windowsille, Mac OS X:lle and 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 KDE 4 trunk-version asettamisesta virtuaalikoneeseen.

Throughout the tutorial the bash shell is used.

Expect a higher risk of build failure on Mondays when most kdelibs changes are committed. Dashboard reports unexpected breakages. You are encouraged to fix failing modules.

[edit] Luo käyttäjätili KDE4-kehitykseen

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 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 .bashrc, put them in a separate file that you source to switch to the KDE 4 environment.

[edit] Vaihtoehto 1: Komentorivi

On some systems a new user is configured by default to use /bin/sh. Using /bin/sh can be very inconvenient to work with and you may want to change it to /bin/bash or another shell. On Ark Linux and Fedora, you can skip the -s /bin/bash switch - /bin/sh is bash.
useradd -m kde-devel -s /bin/bash
passwd kde-devel

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).

[edit] 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.

[edit] Ympäristön asettaminen

Copy the ~/.bashrc from your normal user account to the new kde-devel account. Next, copy and paste the contents of the example .bashrc into ~kde-devel/.bashrc. Be sure to comment out the line alias make=makeobj if you do not have the makeobj 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 this). To make it run, you have to open a new bash or to execute

source ~/.bashrc

This will provide access to commands such as cmakekde 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.

[edit] Vaihdetaan uuteen käyttäjään

Switch to the user kde-devel:

ssh -X kde-devel@localhost
If the ssh command fails, check out the Launching KDE 4 apps section of the KDE4 development guide.

[edit] Jakeluversiostasi vaaditut pakkaukset

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

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

[edit] 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 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.

[edit] 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:

Building KDE4.x

[edit] Hyödyllisiä subversion-säätöjä

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:

[edit] Esimerkki

cs # '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
cs trunk
svn up --depth empty KDE
svn up KDE/kdelibs && cd KDE/kdelibs
cs trunk
svn up KDE/kdepimlibs

[edit] 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 # 'cs' is a bash function, click here to learn more
svn up

[edit] kdelibs

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

[edit] Valmistusohje

cs # '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

[edit] 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 ~/kde/src/KDE/kdelibs directory (line 5), and commence the build (line 6). This will leave us in the kdelibs build directory after the build is completed.

There might be missing dependencies on your system! They are easily overlooked in the output of cmakekde. You might want to do a cmake $KDE_SRC/KDE/MODULE_NAME prior to compiling any kde modules (like kdelibs, kdepimlibs etc.)

[edit] Lisää KDE-kohtaista CMake-taitotietoutta

There are additional CMake modules in 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

[edit] Virheidenjäljitys

For troubleshooting information, see the kdelibs troubleshooting section.

[edit] 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.

[edit] 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

[edit] Valmistusohje

cs KDE # 'cs' is a bash function, click here to learn more
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs
cd kdepimlibs

[edit] 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 ~/kde/src/KDE/kdepimlibs directory (line 3). We then commence the build (line 4). This will leave us in the kdepimlibs build directory after the build is completed.

[edit] Virheidenjäljitys

For troubleshooting information, see the kdepimlibs troubleshooting section.

[edit] 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
cd kdebase
cd kdebase/runtime
in the recipe below.

[edit] Valmistusohje

cs KDE # 'cs' is a bash function, click here to learn more
svn checkout svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase
cd kdebase

[edit] Virheidenjäljitys

For troubleshooting information, see the kdebase troubleshooting section.

[edit] 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:

[edit] Valmistusohje

cs KDE # '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>

[edit] KDE 4-ohjelmien suorittaminen

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

ssh -X kde-devel@localhost

[edit] Virheidenjäljitys

For troubleshooting issues see troubleshooting running programs.

[edit] Paikallisten API-dokumenttien luominen

See the generating apidox page.

[edit] 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 svn up and make.

For example:

cs kdesupport # cs is not a typo
svn up
cb # cb is not a typo
make install

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

[edit] 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 kdegames CMakeLists.txt file lists:


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:

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

[edit] 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 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: Sending Patches

This page was last modified on 18 July 2012, at 13:54. This page has been accessed 5,656 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal