On Monday, September 10, 2012 17:29:10 Dmitry wrote: > 10.09.2012 16:30, Tomaz Canabrava пишет: > > 2012/9/10 Dmitry<dmitry.ashka...@rosalab.ru>: > >> Hello! > >> > >> I've built KDE! The next step is to run KDE. I've found wiki pages: > >> > >> http://techbase.kde.org/Archive:Getting_Started/Run/Nested_Session/en > >> http://techbase.kde.org/Archive:Getting_Started/Run/Full_Session > >> > >> but they are old and they have been removed. I use kdesrc-build to build > >> KDE. How can I run KDE and don't brake my system KDE (configs, etc)? > > > > Did you build your the whole kde? > > The thing I did to run without breaking my system kde settings was to > > copy the kde.desktop file for the KDM/GDM greeters and modifying it a > > bit, there's one line that says 'run=/usr/bin/startkde' , change that > > to 'run=/your/kdesrc-build/installation/startkde' > > Thank you. I've built base KDE libs, Plasma and some KDE applications. > What do you think about KDEHOME environment variable? As I know it > doesn't point to real home directory. But I don't know how to set > KDEHOME in ~/.kdesrc-buildrc and startkde doesn't set it. So, I'm > afraid, that running of startkde without setting of KDEHOME can cause > problems.
There is (old) documentation for starting up a custom-built KDE at http://kdesrc-build.kde.org/documentation/environment.html The basic idea is to figure out what file is used to startup a login session. KDM has an option to let you configure which desktop to login to (usually read from a directory like /usr/share/apps/kdm/sessions). If you have an executable file in your home directory called ".xsession", KDM should give you an option to login to a "Custom" desktop (where "Custom" just means user-defined). .xsession is a regular shell script, where you can set environment variables and then run "startkde" to continue startup. I will probably find a way to automatically install an appropriate setup script at some point. :-/ In the meantime, this file is where you would put the environment variable defines mentioned in the page I listed. Something like: #!/bin/sh # Change these to the install prefix for each (if you modified that) export QTDIR="$HOME/qt4" export KDEDIRS="$HOME/kde" # Execute custom-installed KDE programs by default export PATH="$KDEDIRS/bin:$QTDIR/bin:$PATH" # Link to custom-installed KDE libraries by default export LD_LIBRARY_PATH="$KDEDIRS/lib:$QTDIR/lib:$LD_LIBRARY_PATH" # Tell Qt where to find KDE-installed plugins export QT_PLUGIN_PATH="$KDEDIRS/lib/kde4/plugins:$QT_PLUGIN_PATH" # Might be needed if you try to run 'make' from a kdesrc-build build directory export PKG_CONFIG_PATH="$KDEDIRS/lib/pkgconfig:$QTDIR/lib/pkgconfig: $PKG_CONFIG_PATH" # Act appropriately if LD_LIBRARY_PATH is not already set. if [ -z $LD_LIBRARY_PATH ]; then export LD_LIBRARY_PATH="$KDEDIRS/lib" else export LD_LIBRARY_PATH="$KDEDIRS/lib:$LD_LIBRARY_PATH" fi export KDEHOME="${HOME}/.kde4" # Create it if needed [ ! -e ~/.kde4 ] && mkdir ~/.kde4 # Add XDG-compliant paths, for the K Menu, installed programs, etc. # See http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html export XDG_DATA_DIRS="$KDEDIRS/share/:$XDG_DATA_DIRS" # Startup the rest of KDE exec "$KDEDIRS/bin/startkde" ----------- So, basically you're trying to setup the "environment" to locate the newly- installed libraries, programs, etc., and then you run "startkde" to continue with the rest of the startup sequence. Regards, - Michael Pyne
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
