Rename KDEHOME and KDEDIR

1 files changed, 18 insertions, 18 deletions

diff --git a/doc/tdevelop/tdevelop-install.docbook b/doc/tdevelop/tdevelop-install.docbook
index 62123433..94b42ac0 100644
--- a/doc/tdevelop/tdevelop-install.docbook
+++ b/doc/tdevelop/tdevelop-install.docbook
@@ -319,7 +319,7 @@ In order to successfully compile and use &tdevelop;, you need the following prog
     </para>
     <informalexample><simplelist>
       <member><prompt>(your-tdevelop-directory)&gt; </prompt>
-      <userinput>ln -s $KDEDIR/share/apps/tdelibs/admin admin</userinput></member>
+      <userinput>ln -s $TDEDIR/share/apps/tdelibs/admin admin</userinput></member>
     </simplelist></informalexample>
     <para>
     at the console. This causes &tdevelop; to use the standard settings in the &kde; <filename class="directory">admin</filename> directory instead.
@@ -369,7 +369,7 @@ Once all requirements are met, you are ready to compile and install &tdevelop;.
   <primary>preliminaries</primary>
   <secondary>&tdevelop; installation</secondary></indexterm>
 <indexterm zone="compile-and-install-preliminaries">
-  <primary>KDEDIR</primary></indexterm>
+  <primary>TDEDIR</primary></indexterm>
 <indexterm zone="compile-and-install-preliminaries">
   <primary>QTDIR</primary></indexterm>
 <indexterm zone="compile-and-install-preliminaries">
@@ -395,11 +395,11 @@ If you use the bash shell add the following lines:
 </para>
 
 <informalexample><simplelist>
-  <member><userinput>export KDEDIR=</userinput>(path to your KDE installation)</member>
+  <member><userinput>export TDEDIR=</userinput>(path to your KDE installation)</member>
   <member><userinput>export QTDIR=</userinput>(path to your Qt library)</member>
-  <member><userinput>export LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib:$LD_LIBRARY_PATH</userinput></member>
-  <member><userinput>export LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib:$LIBRARY_PATH</userinput></member>
-  <member><userinput>export PATH=$QTDIR/bin:$KDEDIR/bin:$PATH</userinput></member>
+  <member><userinput>export LD_LIBRARY_PATH=$QTDIR/lib:$TDEDIR/lib:$LD_LIBRARY_PATH</userinput></member>
+  <member><userinput>export LIBRARY_PATH=$QTDIR/lib:$TDEDIR/lib:$LIBRARY_PATH</userinput></member>
+  <member><userinput>export PATH=$QTDIR/bin:$TDEDIR/bin:$PATH</userinput></member>
 </simplelist></informalexample>
 <para></para>
 
@@ -413,11 +413,11 @@ If you use the tcsh shell add the following lines:
 </para>
 <para>
 <informalexample><simplelist>
-  <member><userinput>setenv KDEDIR </userinput>(path to your KDE installation)</member>
+  <member><userinput>setenv TDEDIR </userinput>(path to your KDE installation)</member>
   <member><userinput>setenv QTDIR </userinput>(path to your Qt library)</member>
-  <member><userinput>setenv LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib:$LD_LIBRARY_PATH</userinput></member>
-  <member><userinput>setenv LIBRARY_PATH $QTDIR/lib:$KDEDIR/lib:$LIBRARY_PATH</userinput></member>
-  <member><userinput>setenv PATH $QTDIR/bin:$KDEDIR/bin:$PATH</userinput></member>
+  <member><userinput>setenv LD_LIBRARY_PATH=$QTDIR/lib:$TDEDIR/lib:$LD_LIBRARY_PATH</userinput></member>
+  <member><userinput>setenv LIBRARY_PATH $QTDIR/lib:$TDEDIR/lib:$LIBRARY_PATH</userinput></member>
+  <member><userinput>setenv PATH $QTDIR/bin:$TDEDIR/bin:$PATH</userinput></member>
 </simplelist></informalexample>
 </para>
 
@@ -539,7 +539,7 @@ If you want to build your own <link linkend="make-api">API documentation</link>
 </para>
 <informalexample><simplelist>
   <member><prompt>~/trinitysrc/tdevelop&gt; </prompt>
-  <userinput>./configure --</userinput>(options-as-above) <userinput>\</userinput></member> <member><userinput>--with-tdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/tdelibs-apidocs</userinput></member>
+  <userinput>./configure --</userinput>(options-as-above) <userinput>\</userinput></member> <member><userinput>--with-tdelibsdoxy-dir=$TDEDIR/share/doc/HTML/en/tdelibs-apidocs</userinput></member>
 </simplelist></informalexample>
 </note>
 </listitem>
@@ -606,7 +606,7 @@ That's all. If you installed &tdevelop; in the default &kde; directory you may n
 <indexterm zone="compile-and-install-options-dir">
   <primary>non-default directory</primary></indexterm>
 <indexterm zone="compile-and-install-options-dir">
-  <primary>KDEDIRS</primary></indexterm>
+  <primary>TDEDIRS</primary></indexterm>
 <indexterm zone="compile-and-install-options-dir">
   <primary>kbuildsycoca</primary></indexterm>
 
@@ -625,13 +625,13 @@ Call up a shell and have the following commands executed before you start &tdeve
 </para>
 
 <note><para>
-  <emphasis>Take care to use the plural:</emphasis> It is <quote><envar>KDEDIRS</envar></quote>, not just <quote><envar>KDEDIR</envar></quote>)
+  <emphasis>Take care to use the plural:</emphasis> It is <quote><envar>TDEDIRS</envar></quote>, not just <quote><envar>TDEDIR</envar></quote>)
 </para></note>
 
 <informalexample><simplelist>
   <member>
     <prompt>~&gt; </prompt>
-    <userinput>export KDEDIRS=/usr/local/kde:/opt/trinity</userinput>
+    <userinput>export TDEDIRS=/usr/local/kde:/opt/trinity</userinput>
   </member>
   <member>
     <prompt>~&gt; </prompt>
@@ -647,7 +647,7 @@ Call up a shell and have the following commands executed before you start &tdeve
 </simplelist></informalexample>
 
 <note><simplelist>
-  <member>The <envar>KDEDIRS</envar> environment variable must be set to the <emphasis>list of active &kde; directories</emphasis> in your system. We use</member>
+  <member>The <envar>TDEDIRS</envar> environment variable must be set to the <emphasis>list of active &kde; directories</emphasis> in your system. We use</member>
   <member><filename class="directory">/usr/local/kde</filename>:<filename class="directory">/opt/trinity</filename></member>
   <member>as an example only.</member>
   <member>The <filename class="directory">/usr/local/kde</filename> directory may for instance contain an incomplete &kde; version you compiled for debug purposes, and the <filename class="directory">/opt/trinity</filename> directory may in addition contain the standard &kde; version from your distribution that is used for everyday work.</member>
@@ -658,7 +658,7 @@ In a tcsh shell you must set the environment variables using:
 </para>
 <informalexample><simplelist><member>
     <prompt>~&gt; </prompt>
-    <userinput>setenv KDEDIRS /usr/local/kde:/opt/trinity</userinput>
+    <userinput>setenv TDEDIRS /usr/local/kde:/opt/trinity</userinput>
 </member></simplelist></informalexample>
 <para>
 The <command>kbuildsycoca</command> command (<quote>build system control cache</quote>) looks around for libraries and caches their location and version, so that &tdevelop; can find them. The caveat is that it takes noticeable time&mdash;and it has to be run any time you call up the shell to start &tdevelop; from a non-default directory. You may want to put the above commands into a shell script to reduce the typing effort.
@@ -711,12 +711,12 @@ Alas, this version is best used read-only over the internet. If you do not alway
     <userinput>./configure --</userinput>(options-as-usual)<userinput> \</userinput>
   </member>
   <member>
-    <userinput>--with-tdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/tdelibs-apidocs</userinput>
+    <userinput>--with-tdelibsdoxy-dir=$TDEDIR/share/doc/HTML/en/tdelibs-apidocs</userinput>
   </member>
 </simplelist></informalexample>
 
 <para>
-(<command>make</command> will replace the global <varname>$KDEDIR</varname> variable with the actual &kde; directory setting recorded therein.) Then issue a <command>make</command> command <link linkend="compile-and-install-make-basic">as usual</link>. After the &tdevelop; IDE has been built you have the option to build the API as well. For this you must issue
+(<command>make</command> will replace the global <varname>$TDEDIR</varname> variable with the actual &kde; directory setting recorded therein.) Then issue a <command>make</command> command <link linkend="compile-and-install-make-basic">as usual</link>. After the &tdevelop; IDE has been built you have the option to build the API as well. For this you must issue
 </para>
 <informalexample><simplelist><member>
   <prompt>~/trinitysrc/tdevelop&gt; </prompt>