> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Rick Kunath > Sent: Saturday, September 18, 2004 11:38 AM > To: [EMAIL PROTECTED] > Subject: Re: [newbie] IRC Client > > On Saturday 18 September 2004 10:34 am, [EMAIL PROTECTED] wrote: > > > > > Rick I am interested in the cvs version, if you can give me > some hints I > > would appreciate it. > > > > Regards, > > Dan Gordon > > > Here are some cheat sheets I made up a while ago... > -------------------------------------------------------------- > ------------------------------------------------ > > To install Kvirc CVS on Mandrake 10.0 - > > Get the latest CVS version: > > After opening the terminal window in the desired source > directory, do the > following... (in other words, decide where you want the Kvirc > CVS folders to > be stored, I usually use my /home directory for this, so open > a terminal in > your home directory). And note that if you decide to place > the kvirc CVS > folders somewhere convenient, make sure that no folder name > has a space in it > or you'll have trouble with recursive errors, for some reason > compiling with > folder names with spaces in the path causes errors on some > systems, better to > avoid it. > > > Enter these into the terminal window followed by enter: > > cvs -d:pserver:[EMAIL PROTECTED]:/cvs login > > (If you have trouble here open the Mandrake Control Center > and install cvs. > Then try again.) > > You will be asked for a password...just hit return. > > Then enter: > > cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvs co kvirccvs > > The files will now be downloaded. > > When finished enter these commands (each followed by enter.): > > cd kvirccvs/kvirc > > ./autogen.sh (this will take a while) > (You'll see errors here, ignore them.) > > (If you have trouble here make sure automake and autoconf are > installed.) > (Autoconf 2.13 and 2.5 are usually installed together.) > > The CVS will be made ready for configuring... > > Once this finishes: > > Open a terminal window in the Kvirc source directory. This will be > the /kvirccvs/kvirc directory and located in the directory > wherever you > opened the first terminal window.. You'll have to change to > this directory > from the previous stuff. > > Paste in the following commands into the terminal (enter after each). > > export QTDIR=/usr/lib/qt3 > export KDEDIR=/usr/local/kde > > Then Paste this command in: ./configure > --with-kde-library-dir=/usr/lib/kde3 > --with-big-channels --enable-debug > > Note that this needs to be all on one line. > > (The debug stuff is needed if you ever have trouble and the > big-channels makes > Kvirc work better on large channels with no effect on smaller ones.) > > After this finishes, check for errors and missing packages. > > Once you're happy (see below for more info on this): > > make (enter) (this will take a while) > > su to root priveliges (in other words, type su and enter, > then the root > password and enter. You should be now in terminal as root) > > make install (enter) > > (note that "make install" won't work as a user, you must su to root.) > > Commands can be copied from here and pasted into konsole. > > Do all of your compiling as a user, and su to root only for > the make install > part. > > Compiling with "make" takes a while, and the first time so > does the "make > install", as the modules are created. After that it is faster > as only the > changed stuff gets re-compiled. > > Fire it up with the command kvirc. Go through the Kvirc setup > and enable > whatever features you need. > -------------------------------------------------------------- > -------------------------------------------------------------- > ------------ > > I have attached the file /kvirccvs/kvirc/config.log from my > compile of this > morning. You can use it to wade through your own file. This > file will be > created as you do the ./configure... command from above. > > Go through the file I sent and make sure yours is similar. > There may be some > differences in kernel level, but if you have package errors I > don't have on > mine, hunt them up and install them. It's easy. Tere will be > some errors > reported that are just differences in *nix operating systems. > Configure will > try to determine what it needs according to the OS you have. > > If you have trouble locating something, let me know (I have them all > squirreled away here.) This should be easy though. > > In general, make sure you have the kernel source and the > devel files for > packages you have installed, and things will go smoothly. > > There is a section in the kvirc install info file that will > describe what to > do to get the compression for the DCC voice chat working. It > only needs to be > done once. You can skip this if you don't care about DCC voice chat. > > -------------------------------------------------------------- > -------------------------------------------------------------- > ------------- > Here's the voice section: > > - (Optional) If you want DCC VOICE to support the gsm codec, > you need a recent copy of libgsm. This is not > strictly required > at compile time since KVIrc will look for the library > at run-time, > and only if the DCC VOICE with the gsm codec is requested. > You can check for libgsm using the 'find' command. > > # find / -name libgsm* > > The output should be sometihg like > > # /usr/lib/libgsm.so > > This library is included in most distributions. Some > distros ship > only the static version of the library "libgsm.a": if > the previous > find returned only something similar to > "/usr/lib/libgsm.a" , you > might > create manually the shared archive by running: > (*You'll need to do > this on Mandrake*) > > # cd /usr/lib > # ld --whole-archive -shared -o libgsm.so.1 libgsm.a > # ln -s libgsm.so.1 libgsm.so > # ldconfig > > If you don't have it installed at all, you might have > a look in your > distribution CD, or download it from the web. > > > - (Optional) If you want the /snd plugin to play > various audio formats > you either need a running artsd, a running esd or a > reasonably recent > audiofile library. Without these KVIrc will be only > able to play *.au > files. > -------------------------------------------------------------- > -------------------------------------------------------------- > ---------- > > Same thing for the package hunt, once you have everything > installed, compiling > new CVS changes will be a 1-2-3 deal. > > I hope this helps you out. It sounds a lot more complicated > than it really is. > > Once you have Kvirc running, head over to www.kvirc.net and > subscribe to the > kvirc-devel email list. Then you'll know when new CVS > releases are done with > features you want, and have a good forum for questions to the > developers. > > The Kvirc team is *really* good. I had one of the developers > telnet into my > machine one time to resolve a weird timing issue for me and a > few others with > DCC sends last year. I can't speak highly enough about them. > > Feel free to share this around to others that might need a > hand installing > Kvirc. I've attached the test file of this email too. >
Great, thanks Rick I will have a look at this when I get home from work Regards, Dan Gordon --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.762 / Virus Database: 510 - Release Date: 9/13/2004
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
