Development/Tutorials/Building An Existing Application - Revision history

Archelon: /* Getting the source code */ rm wrong apostrophe

2013-01-15T03:00:15Z

‎Getting the source code: rm wrong apostrophe

2012-05-13T18:58:13Z

‎Library dependencies

2012-05-10T17:44:53Z

‎Getting the source code

2012-05-09T17:06:45Z

Put source path last in CMake command line as CMake docs say

2012-05-08T22:36:57Z

‎Library dependencies

2012-05-08T22:35:48Z

‎Getting the source code

2012-05-08T22:35:36Z

‎Getting the source code

2012-05-08T22:33:45Z

2012-05-08T22:30:34Z

‎Introduction

2012-05-08T22:29:17Z

‎Introduction

@@ Line 15: / Line 15: @@
 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>. Most project names are actually that simple.
+Let's assume you want to build Parley from KDE Education and found that its 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.

@@ Line 80: / Line 80: @@
   mkdir libkdeedu
   cd libkdeedu/
-  cmake -DCMAKE_INSTALL_PREFIX=$PARLEY_PATH ../../src/libkdeedu/
+  cmake -DCMAKE_INSTALL_PREFIX=$KDE_DEVELOPMENT_PATH ../../src/libkdeedu/
   make
   make install

@@ Line 50: / Line 50: @@
   mkdir -p ~/devel/build/parley
   cd ~/devel/build/parley
-  cmake -DCMAKE_INSTALL_PREFIX=$PARLEY_PATH -DCMAKE_BUILD_TYPE=debugfull ../../src/parley
+  cmake -DCMAKE_INSTALL_PREFIX=$KDE_DEVELOPMENT_PATH -DCMAKE_BUILD_TYPE=debugfull ../../src/parley
 Make sure that <tt>cmake</tt> tells you that everything is all right at this point.

@@ Line 50: / Line 50: @@
   mkdir -p ~/devel/build/parley
   cd ~/devel/build/parley
-  cmake ../../src/parley -DCMAKE_INSTALL_PREFIX=$PARLEY_PATH -DCMAKE_BUILD_TYPE=debugfull
+  cmake -DCMAKE_INSTALL_PREFIX=$PARLEY_PATH -DCMAKE_BUILD_TYPE=debugfull ../../src/parley
 Make sure that <tt>cmake</tt> tells you that everything is all right at this point.
@@ Line 80: / Line 80: @@
   mkdir libkdeedu
   cd libkdeedu/
-  cmake ../../src/libkdeedu/ -DCMAKE_INSTALL_PREFIX=$PARLEY_PATH
+  cmake -DCMAKE_INSTALL_PREFIX=$PARLEY_PATH ../../src/libkdeedu/
   make
   make install

@@ Line 74: / Line 74: @@
 == Library dependencies ==
-If you find that you later want to also change libkdeedu which is used by Parley, this setup is just right.
+If you find that you later want to also change libkdeedu which is used by Parley, you are good to go, since the setup above is so that libraries from your build will be found.
   cd ~/devel/src
   git clone kde:libkdeedu

@@ Line 26: / Line 26: @@
 Let's create a script that you can source to set up your development environment.
-If you want to understand more about this script, head over to [[Getting_Started/Build/Environment|Getting Started/Build/Environment]]
+If you want to understand more about this script, head over to [[Getting_Started/Build/Environment|Getting Started/Build/Environment]].
   KDE_DEVELOPMENT_PATH=~/devel/install

@@ Line 26: / Line 26: @@
 Let's create a script that you can source to set up your development environment.
   KDE_DEVELOPMENT_PATH=~/devel/install
@@ Line 35: / Line 36: @@
   export KDETMP=/tmp/kde-git-$USER
   export KDEVARTMP=/var/tmp/kde-git-$USER
   mkdir -p $KDETMP
   mkdir -p $KDEVARTMP

@@ Line 57: / Line 57: @@
 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.
 == Library dependencies ==
@@ Line 68: / Line 79: @@
   make
   make install

← Older revision		Revision as of 22:30, 8 May 2012
Line 3:		Line 3:

	Note that this approach works for applications but most likely not for components that are deep in the system such as kdelibs themselves.		Note that this approach works for applications but most likely not for components that are deep in the system such as kdelibs themselves.
		+
		+	The setup is such that all development happens inside one directory inside your home directory and all settings also get written there. As example we use <tt>~/devel</tt>.

	== Getting the source code ==		== Getting the source code ==

@@ Line 1: / Line 1: @@
 == 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 ==