Difference between revisions of "Getting Started/Build/Environment"

Jump to: navigation, search
(Installation Configuration)
(Home Path)
Line 42: Line 42:
 
  /home/myuser/kde/inst/4.6/kdelibs
 
  /home/myuser/kde/inst/4.6/kdelibs
  
== Home Path ==
+
=== Home Path ===
 
The $KDEHOME path environment variable defines wat directory KDE will treat as your home folder, i.e. for stroing data writing config files to.
 
The $KDEHOME path environment variable defines wat directory KDE will treat as your home folder, i.e. for stroing data writing config files to.
  

Revision as of 19:22, 3 March 2011

Contents

Introduction

Git Configuration

Path Configuration

Source Path

The $KDE_SRC path environment variable defines where the KDE Build System can find the source files.

Build Path

The $KDE_BUILD path environment variable defines where the KDE Build System will create the build files.

The KDE build system requires that your source and build files be in different directories (aka out-of-source builds). This keeps your source directories clean and simplifies management of your different build files. While for some simple build scenarios you could just create a "build" directory inside your 'source' directory (e.g. "kde/src/kdelibs/build"), this does not scale well when managing a full KDE build. Instead clearly separate paths are recommended. For example for kdelibs:

/home/myuser/kde/src/kdelibs
/home/myuser/kde/build/kdelibs

If you plan to build multiple branches of KDE such as stable and unstable in parallel then you will need to add an extra level to the build directory:

/home/myuser/kde/src/kdelibs
/home/myuser/kde/build/master/kdelibs
/home/myuser/kde/build/4.6/kdelibs

Install Path

The $KDEDIR path environment variable defines where the KDE Build System will install KDE.

It is strongly recommended that you install your development builds into a separate non-system location, i.e. don't install as root. This provides for a number of advantages:

  • Your system installed version of KDE is untouched, meaning your normal desktop and applications remain stable and usable even if your development build breaks
  • You can build and run multiple development versions of KDE at the same time, i.e. a stable branch for bug fixes and an unstable branch for new features
  • Doing "make" and "make install" as the same user is a lot quicker

That said, the build instructions provided are completely generic and will work for building a system install if you configure your environment to do so, i.e. for Linux from Scratch or doing a root install in a virtual machine for testing or packaging purposes.

For the kdelibs example given above we would then have:

/home/myuser/kde/src/kdelibs
/home/myuser/kde/build/master/kdelibs
/home/myuser/kde/build/4.6/kdelibs
/home/myuser/kde/inst/master/kdelibs
/home/myuser/kde/inst/4.6/kdelibs

Home Path

The $KDEHOME path environment variable defines wat directory KDE will treat as your home folder, i.e. for stroing data writing config files to.

For the same reason as the Install Path, it is strongly recommended that you set your KDE Home Path to be different from your normal home folder.

For the kdelibs example given above we would then have:

/home/myuser/kde/src/kdelibs
/home/myuser/kde/build/master/kdelibs
/home/myuser/kde/build/4.6/kdelibs
/home/myuser/kde/inst/master/kdelibs
/home/myuser/kde/inst/4.6/kdelibs
/home/myuser/kde/home/master/kdelibs
/home/myuser/kde/home/4.6/kdelibs

Environment Configuration

Useful Scripts


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal