qt -> tqt conversion:

QTDIR -> TQTDIR
QTDOC -> TQTDOC
INCDIR_QT -> INCDIR_TQT
LIBDIR_QT -> LIBDIR_TQT
QT_INC -> TQT_INC
QT_LIB -> TQT_LIB

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 10 insertions, 10 deletions

diff --git a/INSTALL b/INSTALL
index 03dff504..2f2823ea 100644
--- a/INSTALL
+++ b/INSTALL
@@ -49,7 +49,7 @@ General notes for the installation of the 3.4.0 release of KVIrc
     If you're compiling the svn version of KVirc run ./autogen.sh
     (You NEED automake >= 1.5 for autogen.sh to run).
 
-    # export QTDIR="your tqtlibrary path"
+    # export TQTDIR="your tqtlibrary path"
 
     eventually:
 
@@ -259,16 +259,16 @@ General notes for the installation of the 3.4.0 release of KVIrc
         script tries to be smart , but in some cases it will fail.
 
         So before running the script make sure that the enviroinement
-        variable $QTDIR points to the right location. This will help
+        variable $TQTDIR points to the right location. This will help
         in finding the correct version of Qt.
         You might eventually set it with the command:
 
-        # export QTDIR="your qt dir"
+        # export TQTDIR="your qt dir"
 
         On my system qt is installed in /usr/local/kde/qt
         so I actually execute
 
-        # export QTDIR="/usr/local/kde/qt"
+        # export TQTDIR="/usr/local/kde/qt"
 
         If you want to compile the KDE support you might want to do the same
         with TDEDIR
@@ -303,7 +303,7 @@ General notes for the installation of the 3.4.0 release of KVIrc
             Look for the qt library in <DIR>.
             You might want to use this if the configure script has trouble
             in finding the qt library.
-            You should have no problems if you use export QTDIR="<DIR>"
+            You should have no problems if you use export TQTDIR="<DIR>"
             before launching the configure script, but it might help you
             if you have a non standard Qt installation.
         
@@ -311,15 +311,15 @@ General notes for the installation of the 3.4.0 release of KVIrc
             Look for the qt headers in <DIR>.
             You might want to use this if the configure script has trouble
             in finding the qt headers. It may especially help if your headers
-            are in a place different than $QTDIR/include (and thus you have
+            are in a place different than $TQTDIR/include (and thus you have
             a non standard installation)
          
         --with-qt-moc=<PATH>
             Use the qt meta-object compiler found in <PATH>
-            The path is usually $QTDIR/bin/moc , and the
+            The path is usually $TQTDIR/bin/moc , and the
             configure script will find it if you have a standard
-            Qt installation and $QTDIR points to the right directory.
-            Thus should have no problems if you use export QTDIR="<DIR>"
+            Qt installation and $TQTDIR points to the right directory.
+            Thus should have no problems if you use export TQTDIR="<DIR>"
             before launching the configure script, but it might help you
             if you have a non standard Qt installation.
             This will also help if you have the moc compiler renamed
@@ -709,7 +709,7 @@ General notes for the installation of the 3.4.0 release of KVIrc
 
     6. switch to a console
 
-    7. export QTDIR=[path] On Debian is '/usr'
+    7. export TQTDIR=[path] On Debian is '/usr'
 
     8. Read http://doc.trolltech.com/3.0/envvars.html and configure your
        environment vars until kvirc3-emb loads (it will give you an error