diff options
author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-12-07 19:10:38 -0600 |
---|---|---|
committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-12-07 19:10:38 -0600 |
commit | 99cc03399059853dd8699cae5752e8122cb715f1 (patch) | |
tree | 825da375ac05fc555e25b2e350504e211d85d2fb /COMPILING | |
parent | d5b3ae721dc072e0c70055313de9b5228b6688a8 (diff) | |
download | tdelibs-99cc03399059853dd8699cae5752e8122cb715f1.tar.gz tdelibs-99cc03399059853dd8699cae5752e8122cb715f1.zip |
Rename KDEHOME and KDEDIR
Diffstat (limited to 'COMPILING')
-rw-r--r-- | COMPILING | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -41,24 +41,24 @@ source. Qt libs then end up in /usr/local/lib/qt3/lib. 2) Where do you want to have KDE installed. A good candidate is /usr/local/kde Make sure you do (if using sh, ksh, or bash): -export KDEDIR=/usr/local/kde +export TDEDIR=/usr/local/kde With csh or tcsh the following is more appropriate: -setenv KDEDIR /usr/local/kde +setenv TDEDIR /usr/local/kde Now you want to make sure that Qt and KDE libraries are picked up correctly. On systems that respond to environment variables something similar to the following is appropriate: -export LD_LIBRARY_PATH=$KDEDIR/lib:$QTDIR/lib +export LD_LIBRARY_PATH=$TDEDIR/lib:$QTDIR/lib On systems whose diety of choice is ldconfig, try: -ldconfig -m $KDEDIR/lib +ldconfig -m $TDEDIR/lib ldconfig -m $QTDIR/lib -You probably also want to add $KDEDIR/bin and $QTDIR/bin to your path. +You probably also want to add $TDEDIR/bin and $QTDIR/bin to your path. See http://www.kde.org/kde2-and-trinity.html for tips about setting up KDE 3.0 next to KDE 2.x. @@ -88,7 +88,7 @@ One of the biggest problems is picking up the correct version of Qt, especially if your system has more version of Qt installed. Be aware that information about library paths gets saved in the "config.cache" file, "Makefile.in" as well as "Makefile" files. So it can be that after -some struggle to get QTDIR/KDEDIR setup correctly your setup is actually +some struggle to get QTDIR/TDEDIR setup correctly your setup is actually correct, but old -incorrect- settings are still lying around. The best thing to do in such a case is to do a "svn-clean" (from tdesdk/scripts). |