(→Getting the source code) |
(→Getting the source code) |
||
| Line 35: | Line 35: | ||
kbuildsycoca4 | kbuildsycoca4 | ||
| − | Call it for example | + | Call it for example kde-devel-env and source it: |
| − | source | + | source kde-devel-env |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Now we want to have a build directory at the same level as the source directory to keep everything neat. | Now we want to have a build directory at the same level as the source directory to keep everything neat. | ||
Contents |
This tutorial aims to make it easy to get the source code of an application, build and install it in your home directory without interfering with your system.
Make sure to set up git URL renaming properly, so that you can use commands below.
Git Configuration and URL Renaming
You should also configure your git user name and email as mentioned on the git configuration page.
If you don't know the project name of the application you want to build, check out projects.kde.org to find it.
Let's assume you want to build Parley from KDE Education and found that it's project name is simply parley. Most project names are actually that simple.
Once you have the project name, create a directory which you will use for development. We'll use /home/username/devel/src for our source code.
mkdir -p ~/devel/src cd ~/devel/src
And check out the application there:
git clone kde:parley
Let's create a script that you can source to set up your development environment.
KDE_DEVELOPMENT_PATH=~/devel/install export PATH=$KDE_DEVELOPMENT_PATH/bin:$PATH export LD_LIBRARY_PATH=$KDE_DEVELOPMENT_PATH/lib/kde4:$LD_LIBRARY_PATH export KDEDIR=$KDE_DEVELOPMENT_PATH export KDEDIRS=$KDE_DEVELOPMENT_PATH export KDEHOME=~/devel/kdehome # Configuration settings end up here export KDETMP=/tmp/kde-git-$USER export KDEVARTMP=/var/tmp/kde-git-$USER mkdir -p $KDETMP mkdir -p $KDEVARTMP kbuildsycoca4
Call it for example kde-devel-env and source it:
source kde-devel-env
Now we want to have a build directory at the same level as the source directory to keep everything neat. From there we run cmake to create makefiles that allow us to run make to build the application.
mkdir -p ~/devel/build/parley cd ~/devel/build/parley cmake ../../src/parley -DCMAKE_INSTALL_PREFIX=$PARLEY_PATH -DCMAKE_BUILD_TYPE=debugfull
Make sure that cmake tells you that everything is all right at this point. If all went well, you're good to go, run make:
make
(Or to make use of all your cpu cores make -j8 for 8 cores...) And if make finished, install.
make install
Now you should have the application actually installed in /home/username/devel/install. To let kde applications find all their plugins it might be necessary to run kbuildsycoca4 again at this time.
If you find that you later want to also change libkdeedu which is used by Parley, this setup is just right.
cd ~/devel/src git clone kde:libkdeedu cd ../build/ mkdir libkdeedu cd libkdeedu/ cmake ../../src/libkdeedu/ -DCMAKE_INSTALL_PREFIX=$PARLEY_PATH make make install
Most of the time your distribution will provide you with most dependencies for your project. For Debian/Kubuntu run:
apt-get build-dep parley
On openSuse:
zypper source-install parley
(Fetches the source package and installs dependencies. You can then safely remove the source package.)