Login
Immer anmelden
SSL Login

 
Newsletter
Werbung
Shopping
International Shopping
 
 


Yatego Shopping bei über 10000 Händlern und über
3 Mio. Artikel.


Linux

:

Linux-Bücher

Handy
Shop

  und Computer.

Viele Services

:

Apple iPad Reader,


Ratgeber,

 

Techniktops,

 

Yatego Clicks

  & über 3000

Gutscheine.

 
Mi, 9. Januar 2008, 00:00

KDE 4 selbst installieren

/home/kdedev/rc

#!/bin/bash
export HOME=/home/kdedev
export KDEDIR=$HOME
export KDEHOME=$HOME/.kde4
export KDETMP=/tmp/$USER-kde4
mkdir -p $KDETMP
export KDEVARTMP=/var/tmp/$USER-kde4
mkdir -p $KDEVARTMP
export KDEDIRS=$KDEDIR
export KDE4_ENABLE_TESTS=1
export KDE_NO_IPV6=0
unset KDE_FULL_SESSION
export QTDIR=$KDEDIR
export QT_PLUGIN_PATH=$KDEDIR/lib/kde4/plugins:$QTDIR/plugins
export QT_SYSTEM_DIR=$KDEDIR/share
export PKG_CONFIG_PATH=$KDEDIR/lib/pkgconfig:/usr/lib/pkgconfig:$PKG_CONFIG_PATH
export DBUSDIR=/usr
export WINDOWMANAGER='/usr/bin/dbus-launch --sh-syntax --exit-with-session \
 /home/kdedev/bin/startkde'
export DESKTOP_SESSION=kde4
export PATH=$KDEDIR/bin:$KDEDIR/sbin:/usr/local/bin:/usr/local/sbin:\
 /usr/bin:/usr/sbin:/bin:/sbin:/usr/lib/jvm/jre/bin:/usr/NX/bin
export LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH
export YACC='yacc -d'
export EDITOR=/usr/bin/emacs
export BROWSER=$KDEDIR/bin/konqueror
export UPDATE_TYPE=svn
export MANPATH=$KDEDIR/man:/usr/local/man:/usr/share/man
export JAVA_BINDIR=/usr/lib/jvm/java-1.6.0.u3/jre/bin
export JAVA_HOME=/usr/lib/jvm/java-1.6.0.u3/jre
export JAVA_ROOT=/usr/lib/jvm/java-1.6.0.u3/jre
export CXXFLAGS='-march=athlon64-sse3 -mtune=athlon64-sse3 -mabm -mmmx \
 -m3dnow -msse -msse2 -msse3 -mfpmath=sse,387'
export CFLAGS='-march=athlon64-sse3 -mtune=athlon64-sse3 -mabm -mmmx \
 -m3dnow -msse -msse2 -msse3 -mfpmath=sse,387'
export LDFLAGS='-L/home/kdedev/lib'
export XDG_DATA_DIRS=$KDEDIR/share:/usr/local/share:/usr/share
export XDG_CONFIG_DIRS=$KDEDIR/etc/xdg:/etc/xdg
export TELEPATHY_DATA_PATH==$KDEDIR/share/telepathy/managers
export KDE_BUILD=$KDEDIR/build
export KDE_SRC=$KDEDIR/src
export OBJ_REPLACEMENT="s#$KDE_SRC#$KDE_BUILD#"
alias make='makeobj -j 2'
function cmakekde {
 if test -n "$1"; then
 # srcFolder is defined via command line argument
 srcFolder=$1
 else
 # get srcFolder for current dir
 srcFolder=`pwd | sed -e s,$KDE_BUILD,$KDE_SRC,`
 fi
 # we are in the src folder, change to build directory
 # Alternatively, we could just use makeobj in the commands below...
 if [ "$srcFolder" = `pwd` ]; then
 cb
 fi
 # cmake
 cmake $srcFolder -DCMAKE_INSTALL_PREFIX=$KDEDIR \
 -DCMAKE_BUILD_TYPE=debugfull && \
 make -j 2 VERBOSE=1 && \
 make install;
}
##
# A function to easily change to the build directory.
# Usage: cb KDE/kdebase
# will change to $KDE_BUILD/KDE/kdebase
# Usage: cb
# will simply go to the build folder if you are currently in a src folder
# Example:
# $ pwd
# /home/user/src/KDE/kdebase
# $ cb && pwd
# /home/user/build/KDE/kdebase
#
function cb {
 # Make sure build directory exists.
 mkdir -p $KDE_BUILD
 # command line argument
 if test -n "$1"; then
 cd $KDE_BUILD/$1
 return
 fi
 # substitue src dir with build dir
 dest=`pwd | sed -e s,$KDE_SRC,$KDE_BUILD,`
 if test ! -d $dest; then
 # build directory does not exist, create
 mkdir -p $dest
 fi
 cd $dest
}
##
# Change to the source directory. Same as cb, except this
# switches to $KDE_SRC instead of $KDE_BUILD.
# Usage: cs KDE/kdebase
# will change to $KDE_SRC/KDE/kdebase
# Usage: cs
# will simply go to the source folder if you are currently in a build folder
# Example:
# $ pwd
# /home/user/build/KDE/kdebase
# $ cs && pwd
# /home/user/src/KDE/kdebase
#
function cs {
 # Make sure source directory exists.
 mkdir -p $KDE_SRC
 # command line argument
 if test -n "$1"; then
 cd $KDE_SRC/$1
 else
 # substitue build dir with src dir
 dest=`pwd | sed -e s,$KDE_BUILD,$KDE_SRC,`
 if [ $dest = `pwd` ]; then
 cd $KDE_SRC
 else
 cd $dest
 fi
 fi
}

Ein kleines Alias kde4='cd /home/kdedev; source /home/kdedev/rc' macht die Sache nun schon etwas einfacher. Das folgende Skript /home/kdedev/doit strickt aus dem ganzen Berg an Quellen ein brandneues KDE 4. Um jeglichen Problemen von vornherein aus dem Weg zu gehen, werden die Build-Verzeichnisse jedesmal geleert und auch alle installierten Dateien entfernt. Somit muss auch bei kleinen Ãnderungen stets alles neu compiliert werden. Das zieht die ganze Aktion zwar enorm in die Länge, hat aber den Vorteil, dass man jedesmal eine »saubere« Umgebung erhält.

Kommentare (Insgesamt: 0 || Kommentieren )
Pro-Linux
Newsletter
Neue Nachrichten