On 11/28/06, Kevin Kofler <kevin.kofler(a)chello.at> wrote:
There are several reasons this isn't going to work that way:
* a .desktop is not a shell script, you can't have export statements there
* $/opt/kde4/lib/ in your LD_LIBRARY_PATH has a $ too many
* startkde isn't designed to be run like that!
Ah ha, ok, ill make the changes tonight.
KDEDIR=/opt/kde4 and KDEHOME=~/.kde4 shouldn't be needed, by the
way. Look at
* KDE 4 with the patches looks at KDE4DIR and KDE4HOME, not KDEDIR and KDEHOME,
so you're setting the wrong environment variables. You're actually changing the
paths for KDE 3, which is a bad idea.
* The default paths for KDE4DIR and KDE4HOME are exactly the ones you're
Ok, ill remove them
There are 2 options to run KDE 4:
* Run a KDE 4 desktop from the console. You need to telinit into runlevel 3,
from the terminal. But you can't do this from a running desktop, so a .desktop
file is the wrong place to put that.
* Run only individual KDE 4 apps in a KDE 3 or GNOME desktop. My patches are
designed to allow exactly that. Try for example:
(Note that Konqueror 4 was pretty badly broken when I snapshotted it. I don't
know how much of that has been fixed in 3.80.2 or current SVN.)
So what's the best solution to make it work out of the box when we
installed kdebase4 ?
As for why the LD_LIBRARY_PATH is needed in the first place, this is
effect of disabling the rpath mechanism (-DCMAKE_SKIP_RPATH=TRUE). With the
rpath, it finds the libraries. (In fact, this is exactly what the rpath is for.
Rpaths are only bad when they refer to a standard path like /usr/lib
or /usr/lib64.) I don't know why it didn't build for you without this option
because it built just fine for me with the rpaths enabled.
But in my case, rpmbuild for kdebase4 fails without -DCMAKE_SKIP_RPATH=TRUE.