summaryrefslogtreecommitdiffstats
path: root/INSTALL
diff options
context:
space:
mode:
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL86
1 files changed, 41 insertions, 45 deletions
diff --git a/INSTALL b/INSTALL
index 2f2823e..92b8e71 100644
--- a/INSTALL
+++ b/INSTALL
@@ -14,7 +14,7 @@ General notes for the installation of the 3.4.0 release of KVIrc
2. Guru-level installation
3. Hacker-level installation
4. Human (detailed) installation instructions
- 5. How to compile KVIrc with Qt-embedded
+ 5. How to compile KVIrc with TQt-embedded
6. Compiling KVIrc on Mac OS X
7. A note about Windows 95/98/ME
@@ -141,11 +141,10 @@ General notes for the installation of the 3.4.0 release of KVIrc
then you miss some gcc related package. Install it from the distro cd.
- - You NEED the Qt library.
+ - You NEED the TQt library.
- You can download the latest version from ftp://ftp.trolltech.com.
- The main Qt www site is http://www.trolltech.com.
- Note for the GPL maniacs: Qt IS GPL.
+ TQt is maintained by TDE, the main www site is https://trinitydesktop.org.
+ Note for the GPL maniacs: TQt IS GPL.
The minimum required version is 3.1.2 (older versions *might* work)
Download and install it by following the rules
explained in the excellent documentation that comes with the library.
@@ -260,15 +259,15 @@ General notes for the installation of the 3.4.0 release of KVIrc
So before running the script make sure that the enviroinement
variable $TQTDIR points to the right location. This will help
- in finding the correct version of Qt.
+ in finding the correct version of TQt.
You might eventually set it with the command:
- # export TQTDIR="your qt dir"
+ # export TQTDIR="your tqt dir"
- On my system qt is installed in /usr/local/kde/qt
+ On my system tqt is installed in /usr/local/kde/tqt
so I actually execute
- # export TQTDIR="/usr/local/kde/qt"
+ # export TQTDIR="/usr/local/kde/tqt"
If you want to compile the KDE support you might want to do the same
with TDEDIR
@@ -299,35 +298,35 @@ General notes for the installation of the 3.4.0 release of KVIrc
will probably shorten the compilation a bit. Use this option if
your platform supports it.
- --with-qt-library-dir=<DIR>
- Look for the qt library in <DIR>.
+ --with-tqt-library-dir=<DIR>
+ Look for the tqt library in <DIR>.
You might want to use this if the configure script has trouble
- in finding the qt library.
+ in finding the tqt library.
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.
+ if you have a non standard TQt installation.
- --with-qt-include-dir=<DIR>
- Look for the qt headers in <DIR>.
+ --with-tqt-include-dir=<DIR>
+ Look for the tqt 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
+ in finding the tqt headers. It may especially help if your headers
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>
+ --with-tqt-moc=<PATH>
+ Use the tqt meta-object compiler found in <PATH>
The path is usually $TQTDIR/bin/moc , and the
configure script will find it if you have a standard
- Qt installation and $TQTDIR points to the right directory.
+ TQt 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.
+ if you have a non standard TQt installation.
This will also help if you have the moc compiler renamed
in some way: like "moc2" or sth...
<PATH> in this case is a FULL path: directory/program_name!
- --disable-qt-check
- This disables Qt checking at compilation time.
+ --disable-tqt-check
+ This disables TQt checking at compilation time.
If this is the only way to compile and run
the kvirc executable , then there is something
wrong with the configure script.
@@ -353,7 +352,7 @@ General notes for the installation of the 3.4.0 release of KVIrc
irc:// urls in konqueror
--without-kde-check
- Similar to --without-qt-check but for KDE.
+ Similar to --without-tqt-check but for KDE.
--enable-optimisation=<NUMBER>
Enables the compiler optimisation flag -o<NUMBER>.
@@ -404,24 +403,21 @@ General notes for the installation of the 3.4.0 release of KVIrc
You might want to use this if the configure script
has trouble in finding it.
- --with-qt-name=<NAME>
- Use <NAME> instead of "qt" as the Qt library name.
- This is useful on systems where Qt has been installed with
- a name different than the default "qt".
- It happens often that to allow multiple copies of qt to work
+ --with-tqt-name=<NAME>
+ Use <NAME> instead of "tqt" as the TQt library name.
+ This is useful on systems where TQt has been installed with
+ a name different than the default "tqt".
+ It happens often that to allow multiple copies of tqt to work
the newest have the version name appended to it.
- For example, on FreeBSD I have found "qt" being Qt1.* and
- "qt2" being Qt 2.*. Since you need Qt 2.* for kvirc to work,
- you will need to use --with-qt-name=qt2.
If you use this option, you will probably also need to remap
- the moc compiler path/name with --with-qt-moc.
+ the moc compiler path/name with --with-tqt-moc.
- --disable-qt-mt
- Disable checking for the multithreaded version of Qt.
+ --disable-tqt-mt
+ Disable checking for the multithreaded version of TQt.
By default , KVIrc will try to link to the multithreaded version
if found on the system.
NOTE: if you enable the KDE support , KVIrc MUST be linked to the
- qt library that KDE is linked to.
+ tqt library that KDE is linked to.
--with-ix86-asm
KVIrc contains some ix86 assembly routines that *could*
@@ -522,7 +518,7 @@ General notes for the installation of the 3.4.0 release of KVIrc
--enable-fno-rtti
Disables compiler runtime type information generation.
- This is probably needed only with qt-embedded.
+ This is probably needed only with tqt-embedded.
DON'T use it if you don't exactly know what it does.
Actually this may even make KVIrc crash in some situations.
For example the KDE sources use __dynamic_cast...
@@ -530,16 +526,16 @@ General notes for the installation of the 3.4.0 release of KVIrc
--disable-x-support
Disables completely the X Windows support.
This is useful in environments where X is not needed to compile KVIrc
- such as Qt-Mac on MacOSX, QtEmbedded or Windows.
+ such as TQt-Mac on MacOSX, QtEmbedded or Windows.
This switch implies also --without-x-bell
--without-x-bell
Disables the usage of the XBell function (needed if you want to
- compile KVIrc with qt-embedded (no X at all))
+ compile KVIrc with tqt-embedded (no X at all))
This is implied by --disable-x-support
- --with-qt-embedded
- You need this to compile KVIrc with qt-embedded
+ --with-tqt-embedded
+ You need this to compile KVIrc with tqt-embedded
--without-ipc
Disables support for inter-process communication.
@@ -625,7 +621,7 @@ General notes for the installation of the 3.4.0 release of KVIrc
On FreeBSD I have found useful this command line:
- # ./configure --with-qt-name=qt2 --with-qt-moc=/<PATH_HERE>/moc2 \
+ # ./configure --with-tqt-name=qt2 --with-tqt-moc=/<PATH_HERE>/moc2 \
--with-freebsd-pthread
Once the configure script ran succesfully you can go to the next step.
@@ -680,7 +676,7 @@ General notes for the installation of the 3.4.0 release of KVIrc
###############################################################################
-# 5. Compiling KVIrc on qt-embedded
+# 5. Compiling KVIrc on tqt-embedded
###############################################################################
Do you want KVIrc 3 on your hand computer ?
@@ -689,16 +685,16 @@ General notes for the installation of the 3.4.0 release of KVIrc
Well, for the third it's really easy, just follow carefully those steps:
- 1. Install qt-embedded libraries (including the development files).
+ 1. Install tqt-embedded libraries (including the development files).
This can be as easy as: apt-get install libtqt-emb-dev on Debian.
2. cd to the KVIrc3 source directory
3. run configure with the following parameters:
- # ./configure --with-qt-name=qte --with-fno-rtti --without-x-calls
+ # ./configure --with-tqt-name=qte --with-fno-rtti --without-x-calls
--without-ipc --without-splash-screen --without-transparency
- --with-qt-embedded --without-x-bell
+ --with-tqt-embedded --without-x-bell
then run make and make install as usual