trassdon
01-06-2002, 04:49 PM
Installation and configuration SEQ for Mandrake 8.1
1. With the installation of Mandrake 8.1 to check the following package:
- Workstation & Network Component
- Development
2. After the installation of MDK 8.1 to control the following package, with
Mandrake Update:
*** necessary bookshops ***
qt 2.3.2 (ATTENTION must be to compile with - thread)
qt-devel 2.3.2 (ATTENTION must be to compile with - thread)
libpcap 0.62
gdbm 1.8.0
*** bookshops Optional ***
db3 3.2.9 3.3
*** C++ Compiler ***
glibc 2.2 2.2.4
libstdc++ 3.0 3.0.2
GCC 3.0 3.0.2
*** Tools Gnu ***
libtool 1.3.4-3 Or more recent...
autoconf 2.13-1 Or more recent...
automake 1.4-6 Or more recent...
3. Downloading of the bookshops:
QT 2.3.2:
ftp://ftp.trolltech.com/qt/source/qt-x11-2.3.2.tar.gz
LibEQ.a:
ftp://azriel.trifocus.net/pub/libeq/i386/linux/libEQ.a
ftp://smurfette.trifocus.net/pub/li... 6/linux/libEQ.a
ShowEQ:
cvs - d:pserver:[email protected]:/cvsroot/seq login
cvs - z3 - d:pserver:[email protected]:/cvsroot/seq Co showeq
It is advised of placed all these files in an easy place
not to have to type line of command too much in the event of
displacement in the system. Midnight To control and very useful
in this kind of case, hesitated not to install it. The command of
launching is: mc
3. Script for QT:
On a portable with a CPU Pentium III 366, this compilation with
taken approximately 1h20, it is thus advised not to have X launched of
manner with leaves the maximum of resource CPU to the compiler,
to discharge X, type in line of command " CTRL+ALT+F1 "
init 3 (init 3 discharge X but guard despite everything the active system
so as to be able to serve your network or other, not to forget not
to pass in init 5 at the end of all compilation).
For avoided having to modify things in the system, which
could cause problems thereafter, we will make
a small script to explain to the system or is QT and
how y to reach.
Take a text editor EMACS for example then to manufacture one
file named " useqt232 " added the lines following to the file.
QTDIR=/usr/local/qt-2.3.2 export
PATH=$QTDIR/bin:$PATH export
MANPATH=$QTDIR/doc/man:$MANPATH export
LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH export
echo " QTDIR=$QTDIR "
echo " gcc"' wich gcc3 '
export C=GCC3
export XCX=g++3
to save script in the file " useqt232 " in your repertory
root.
To modify the CHMOD of the file " useqt232 " into 744 so as to
what it is executable with the following command:
chmod 744 useqt232
Then launched " useqt232 "
/useqt232
Once this finished stage, placed you in the répèrtoire
/ usr/bin then launched these two commands (this one allows
created link symbolic system for compiler GCC 3.0)
ln -- symbolic GCC-3.0.1 gcc3
ln -- symbolic g++-3.0.1 g++3
4. Decompression of QT:
Place you in the repertory or is your package QT
qt-x11-2.3.2.tar.gz then launched the following command for
décompresser.
tar - xzvf qt-x11-2.3.2.tar.gz
One your package QT décompresser to move it in
repertory / usr/local/qt by means of the following command:
mv qt-2.3.2 / usr/local/qt
5. Compilation of QT:
To check to have well to carry out script " useqt232 " and to be
quite sour to have the rights root for launched compilation.
Placed you in the repertory / usr/local/qt
Then launched the following command:
/configure - thread
Then:
make
ATTENTION this stage takes easily more than 60 minutes.
6. Compilation of ShowEQ:
Once the stage of correctly achieved QT, there is 80% of
chance that your ShowEQ is compilable, personally I
am taken again to me there with 4 times before succeeding in compiling ShowEQ without
error.
The stages of compilation are the following ones:
make - F Makefile.dist
/configure
make
make install
If no error slipped into your compilation until there
it is that ShowEQ functions.
It is significant to know that ShowEQ does not go on
switch, but only on HUB.
7. Configuration of ShowEQ.
The files of execution of ShowEQ is in / usr/local/bin,
the files of configuration of ShowEQ is in
/ usr/local/share/showeq
You must copy the files:
showeq.conf.dist in showeq.conf
and
filters.conf.dist in filters.conf
To publish the file showeq.conf then to add address IP of
machine on laquel turns Everquest.
8. Launching of ShowEQ.
You can created an icon of launching of ShowEQ on your
office KDE or Gnome, not to forget not activated launching in
a console, that makes it possible to follow possible Erreur which
could occur thereafter in the event of evolution of Everquest.
Good luck!
1. With the installation of Mandrake 8.1 to check the following package:
- Workstation & Network Component
- Development
2. After the installation of MDK 8.1 to control the following package, with
Mandrake Update:
*** necessary bookshops ***
qt 2.3.2 (ATTENTION must be to compile with - thread)
qt-devel 2.3.2 (ATTENTION must be to compile with - thread)
libpcap 0.62
gdbm 1.8.0
*** bookshops Optional ***
db3 3.2.9 3.3
*** C++ Compiler ***
glibc 2.2 2.2.4
libstdc++ 3.0 3.0.2
GCC 3.0 3.0.2
*** Tools Gnu ***
libtool 1.3.4-3 Or more recent...
autoconf 2.13-1 Or more recent...
automake 1.4-6 Or more recent...
3. Downloading of the bookshops:
QT 2.3.2:
ftp://ftp.trolltech.com/qt/source/qt-x11-2.3.2.tar.gz
LibEQ.a:
ftp://azriel.trifocus.net/pub/libeq/i386/linux/libEQ.a
ftp://smurfette.trifocus.net/pub/li... 6/linux/libEQ.a
ShowEQ:
cvs - d:pserver:[email protected]:/cvsroot/seq login
cvs - z3 - d:pserver:[email protected]:/cvsroot/seq Co showeq
It is advised of placed all these files in an easy place
not to have to type line of command too much in the event of
displacement in the system. Midnight To control and very useful
in this kind of case, hesitated not to install it. The command of
launching is: mc
3. Script for QT:
On a portable with a CPU Pentium III 366, this compilation with
taken approximately 1h20, it is thus advised not to have X launched of
manner with leaves the maximum of resource CPU to the compiler,
to discharge X, type in line of command " CTRL+ALT+F1 "
init 3 (init 3 discharge X but guard despite everything the active system
so as to be able to serve your network or other, not to forget not
to pass in init 5 at the end of all compilation).
For avoided having to modify things in the system, which
could cause problems thereafter, we will make
a small script to explain to the system or is QT and
how y to reach.
Take a text editor EMACS for example then to manufacture one
file named " useqt232 " added the lines following to the file.
QTDIR=/usr/local/qt-2.3.2 export
PATH=$QTDIR/bin:$PATH export
MANPATH=$QTDIR/doc/man:$MANPATH export
LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH export
echo " QTDIR=$QTDIR "
echo " gcc"' wich gcc3 '
export C=GCC3
export XCX=g++3
to save script in the file " useqt232 " in your repertory
root.
To modify the CHMOD of the file " useqt232 " into 744 so as to
what it is executable with the following command:
chmod 744 useqt232
Then launched " useqt232 "
/useqt232
Once this finished stage, placed you in the répèrtoire
/ usr/bin then launched these two commands (this one allows
created link symbolic system for compiler GCC 3.0)
ln -- symbolic GCC-3.0.1 gcc3
ln -- symbolic g++-3.0.1 g++3
4. Decompression of QT:
Place you in the repertory or is your package QT
qt-x11-2.3.2.tar.gz then launched the following command for
décompresser.
tar - xzvf qt-x11-2.3.2.tar.gz
One your package QT décompresser to move it in
repertory / usr/local/qt by means of the following command:
mv qt-2.3.2 / usr/local/qt
5. Compilation of QT:
To check to have well to carry out script " useqt232 " and to be
quite sour to have the rights root for launched compilation.
Placed you in the repertory / usr/local/qt
Then launched the following command:
/configure - thread
Then:
make
ATTENTION this stage takes easily more than 60 minutes.
6. Compilation of ShowEQ:
Once the stage of correctly achieved QT, there is 80% of
chance that your ShowEQ is compilable, personally I
am taken again to me there with 4 times before succeeding in compiling ShowEQ without
error.
The stages of compilation are the following ones:
make - F Makefile.dist
/configure
make
make install
If no error slipped into your compilation until there
it is that ShowEQ functions.
It is significant to know that ShowEQ does not go on
switch, but only on HUB.
7. Configuration of ShowEQ.
The files of execution of ShowEQ is in / usr/local/bin,
the files of configuration of ShowEQ is in
/ usr/local/share/showeq
You must copy the files:
showeq.conf.dist in showeq.conf
and
filters.conf.dist in filters.conf
To publish the file showeq.conf then to add address IP of
machine on laquel turns Everquest.
8. Launching of ShowEQ.
You can created an icon of launching of ShowEQ on your
office KDE or Gnome, not to forget not activated launching in
a console, that makes it possible to follow possible Erreur which
could occur thereafter in the event of evolution of Everquest.
Good luck!