PDA

View Full Version : Newbie guide to getting ShowEQ to work...



Squill
06-10-2004, 10:53 AM
Now I know alot of you already have it up and running, but there are some noobies (like myself) that have alot of problems getting it running. I don't know much about linux but I do know alittle, like I said I'm anoob so this might help out those other noobs out there. Here's what I did.

1st- Go and download redhat linux 9.

2nd- while installing once you get to the Packages screen go to the bottom and select EVERYTHING. This will install all the packages that you need (plus some that you dont)

3rd- Once you finish installing it download the ShowEQ-5.0.0.7_beta7.tar.bz2 file from here (http://sourceforge.net/project/showfiles.php?group_id=10131&package_id=13256)

4th- Save the file to your home directory, and then extract the folder inside the .tar file. If you ever used winzip in Windows then you can do this. It works the same way.

5th- Open up a new terminal and type su
- then type your Root password in
-When you are given the [root@localhost username]# prompt, enter the following code line by line.
[]# cd /seq/showeq/ (or whichever directory you extracted the .tar too)
[]# export CC=gcc3
[]# export CXX=g++3
[]# export QTDIR=/usr/lib/qt-3.1
[]# make -f Makefile.dist
[]# ./configure
[]# make
[]# make install

6th- Not quite done, this version of EQ will most likely not work for you. it didn't work for me. So this is what your gonna have to do. Keep the terminal open but make sure it's out of the way. Now download this file http://home.comcast.net/~squill/zoneopcodes.xml.gz
and extract it to your /showeq/conf/ directory. It'll ask you if you wish to overwrite the file, say yes.

7th- Now we're almost done. Download this file. http://home.comcast.net/~squill/everquest.h.tar.gz
and extract it to your /showeq/src/ directory. Click yes when it asks if you wish to overwrite the file.

8th- Now you should be ready to go. go back to terminal you were working with before.
type this.

[]# make -f Makefile.dist
[]# ./configure
[]# make
[]# make install

once it's done type this to load up ShowEQ.

[]# export QTDIR=/usr/lib/qt-3.2.3
[]# cd /usr/local/bin
[]# ./showeq eth0 --ip-address=(your eq machine's ip here).

and there you go, That's what I had to do to get ShowEQ working for me. If you have any questions feel free to ask. The 2 files provided in this post are not mine. They were found here (http://seq.sourceforge.net/forums/showthread.php?s=&threadid=4855&perpage=15&pagenumber=1). This thread is pretty much all the different threads in the forums that I put together for a newbie to understand. Hope it helps!

~Squill :D

ksmith
06-10-2004, 11:21 AM
I would strongly encourage using CVS (http://seq.sourceforge.net/forums/showthread.php?s=&threadid=4869#post35650) instead of downloading a tarball and patching it piecemeal.

Before I post a new thread, I always ask myself, has anyone else had anything to say on the matter?
http://seq.sourceforge.net/forums/showthread.php?s=&threadid=4828
http://seq.sourceforge.net/forums/showthread.php?s=&threadid=4823

Perhaps you could update the official documentation (http://cvs.sourceforge.net/viewcvs.py/seq/showeq/INSTALL.newbies?rev=1.5.16.1&only_with_tag=pre_5_0_beta&view=auto) and post a diff.

Squill
06-10-2004, 11:41 AM
The only reason I didn't use cvs was because I was having problems connecting to it. And I found this to be the easiest way of doing it. and like I said I'm a noob.

oops
07-02-2004, 12:22 PM
Anyway to get a list of the required elements to install, rather the the click on EVERYTHING. FC2, click everything, get over 6GB installed. That plus SEQ means requiring at least an 8G drive. That is bigger than I have in my laptop.

Also, not installing services like HTTP, Mail, DHCP, DNS, NFS, SMB, etc makes a safer installation. Of course you can set them not to start, even if they are installed.

devilspawn
03-19-2005, 04:46 PM
When I get to the First Make right after ./configure it says "Please Verify that your Devel Install!" this is running on Mandrake 10.1


Please help me lol i am freakin lost fist time trying any thing with linux.

A Noob

purple
03-19-2005, 04:50 PM
Cut and paste more of the error than that please. You're probably missing some packages (qt-devel or pcap maybe).

devilspawn
03-19-2005, 05:03 PM
[chris@localhost showeq-5.0.0.18]$ .
bash: .: filename argument required
.: usage: . filename
[chris@localhost showeq-5.0.0.18]$ ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for doxygen... no
configure: WARNING: doxygen not found - will not generate any doxygen documentation
checking for perl... /usr/bin/perl
checking for gcc3... no
checking for gcc... gcc
checking for g++3... no
checking for g++... g++
checking for supported compiler version... checking for style of include used by make... GNU
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
yes
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for an ANSI C-conforming const... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking for correct ltmain.sh version... yes
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for supported libc version... yes
checking for X... no
checking for IceConnectionNumber in -lICE... no
checking for libXext... no
checking for extra includes... no
checking for extra libs... no
checking for libz... no
checking for libpng... no
checking for Qt... no
>> Unable to locate your Qt includes...
configure: error: Please verify your Qt devel install!
[chris@localhost showeq-5.0.0.18]$ make
make: *** No targets specified and no makefile found. Stop.
[chris@localhost showeq-5.0.0.18]$ MAKE
bash: MAKE: command not found
[chris@localhost showeq-5.0.0.18]$

Looks like i might be missing afew files in Linux libary ? First time using linux thats not on a live CD so i might have missed it on the Install of Linux ?

Alethal
03-19-2005, 05:20 PM
Hey,

Install qt-devel. I am not sure how mandrake works, there is probably an automatic way to do that. Otherwise, just go to trolltech website and download their development libraries.

G'luck, welcome to Linux.

BlueAdept
03-19-2005, 09:29 PM
Why are people bumping a thread that is almost a YEAR OLD?

purple
03-19-2005, 10:13 PM
At least it probably means they searched first!