(Created page with "== Introduction == 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. ...") |
(→Getting the source code) |
||
| Line 9: | Line 9: | ||
You should also configure your git user name and email as mentioned on the git configuration page. | You should also configure your git user name and email as mentioned on the git configuration page. | ||
| − | If you don't know the | + | If you don't know the project name of the application you want to build, check out [http://projects.kde.org 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 <tt>parley</tt>. | + | Let's assume you want to build Parley from KDE Education and found that it's project name is simply <tt>parley</tt>. 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 <tt>/home/username/devel/src</tt> for our source code. | Once you have the project name, create a directory which you will use for development. We'll use <tt>/home/username/devel/src</tt> for our source code. | ||
| Line 25: | Line 25: | ||
foo bar | foo bar | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| + | |||
| + | Let's create a script that you can source to set up your development environment. | ||
| + | |||
| + | PARLEY_PATH=/home/frederik/devel/install | ||
| + | export PATH=$PARLEY_PATH/bin:$PATH | ||
| + | export LD_LIBRARY_PATH=$PARLEY_PATH/lib/kde4:$PARLEY_PATH/lib64:/home/frederik/dev/qt/qt-4/lib | ||
| + | |||
| + | export KDEDIR=$PARLEY_PATH | ||
| + | export KDEDIRS=$PARLEY_PATH | ||
| + | export QT_PLUGIN_PATH=$KDEDIR/lib/kde4:$KDEDIR/lib64 | ||
| + | |||
| + | kbuildsycoca4 | ||
| + | |||
| + | Call it for example parley-devel-env and source it: | ||
| + | source parley-devel-env | ||
| + | |||
| + | If you run | ||
| + | export | ||
| + | now it should show you the variables that get set in the script. | ||
| + | |||
| + | 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 | ||
| + | |||
| + | Make sure that <tt>cmake</tt> tells you that everything is all right at this point. | ||
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
foo bar
Let's create a script that you can source to set up your development environment.
PARLEY_PATH=/home/frederik/devel/install export PATH=$PARLEY_PATH/bin:$PATH export LD_LIBRARY_PATH=$PARLEY_PATH/lib/kde4:$PARLEY_PATH/lib64:/home/frederik/dev/qt/qt-4/lib
export KDEDIR=$PARLEY_PATH export KDEDIRS=$PARLEY_PATH export QT_PLUGIN_PATH=$KDEDIR/lib/kde4:$KDEDIR/lib64
kbuildsycoca4
Call it for example parley-devel-env and source it:
source parley-devel-env
If you run
export
now it should show you the variables that get set in the script.
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
Make sure that cmake tells you that everything is all right at this point.