kvirc
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

INSTALL 31KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753
  1. Szymon Stefanek Mon Mar 04 2008
  2. ###############################################################################
  3. General notes for the installation of the 3.4.0 release of KVIrc
  4. ###############################################################################
  5. This document contains the procedures to compile and install
  6. the version 3.4.0 of KVIrc.
  7. ###############################################################################
  8. # 0. Table of contents
  9. ###############################################################################
  10. 1. Introduction
  11. 2. Guru-level installation
  12. 3. Hacker-level installation
  13. 4. Human (detailed) installation instructions
  14. 5. How to compile KVIrc with Qt-embedded
  15. 6. Compiling KVIrc on Mac OS X
  16. 7. A note about Windows 95/98/ME
  17. ###############################################################################
  18. # 1. Introduction
  19. ###############################################################################
  20. This document contains the procedures to compile and install
  21. the version 3.4.0 of KVIrc.
  22. If you have found this document in a binary distribution then
  23. KVIrc has been probably already installed by your favorite package
  24. manager and maybe something is not working as expected. In this case
  25. this document and the accompanying FAQ can help you in guessing
  26. what's wrong.
  27. If you have found this document in a source distribution or you
  28. have downloaded it by using the svn then well...
  29. this is a standard INSTALL file :)
  30. ###############################################################################
  31. # 2. Guru installation:
  32. ###############################################################################
  33. # ./configure
  34. # make install
  35. ###############################################################################
  36. # 3. Hacker installation:
  37. ###############################################################################
  38. If you're compiling the svn version of KVirc run ./autogen.sh
  39. (You NEED automake >= 1.5 for autogen.sh to run).
  40. # export TQTDIR="your tqtlibrary path"
  41. eventually:
  42. # export TDEDIR="your kde library path"
  43. We're using GNU tools here.
  44. # ./configure --help
  45. # ./configure [your options]
  46. # make
  47. # make install
  48. ###############################################################################
  49. # 4. Human (detailed) installation:
  50. ###############################################################################
  51. If you're not a guru, or have problems with the installation
  52. read these instructions carefully.
  53. ###
  54. ### Step 0 (ONLY FOR THE SVN VERSION)
  55. ###
  56. If (*** AND ONLY IF ***) you're compiling the svn version of kvirc
  57. you need to generate the configure script. If you're compiling
  58. a downloaded tar.gz (or tar.bz2) package or you don't know what
  59. svn is then jump directly to step 1!
  60. You need a recent automake and autoconf installed on your system.
  61. It is also reccomended to have a recent (matching) libtool installed
  62. (libtool is not strictly necessary since KVIrc has a bundled one,
  63. but a libtool matching your automake/autoconf versions will probably
  64. run better on your system).
  65. Anyway, run:
  66. # ./autogen.sh
  67. If it runs without any error (it will tell you "Done") then
  68. you may skip to step 1, otherwise read on.
  69. First of all check your auomake version.
  70. You need automake >= 1.5: older versions will NOT WORK.
  71. You can check the automake version with the command
  72. # automake --version
  73. If your automake version is lower than 1.5 upgrade it.
  74. You can find it at http://www.gnu.org/software/automake/ (source)
  75. or on your favorite distribution site as auto-installing package.
  76. Automake installation tip: automake installs in /usr/local/
  77. by default. If you have an older automake installation that
  78. resides in /usr/ it's better to remove it or (better) overwrite it
  79. with the new installation.
  80. If you choose to overwrite the old installation with the new
  81. one then just use "./configure --prefix=/usr" as the automake's
  82. configure command.
  83. If you choose to remove the old version then the files to be
  84. removed are /usr/bin/automake /usr/bin/aclocal /usr/share/automake
  85. /usr/share/aclocal. If you feel unsure about removing it, rename it.
  86. If the script fails to run then you might try
  87. # ./autogen.sh --bundled-libtool
  88. to force the usage of the bundled libtool version.
  89. If you later have unexplicable problems with the compilation tools
  90. you might also try the bundled libtool.
  91. ###
  92. ### Step 1 : Matching the requirements
  93. ###
  94. - You NEED a fully working C++ compiler.
  95. Most linux distributions have it pre-installed and if you have
  96. already compiled other programs before then you're probably ok,
  97. so actually skip this check and go ahead. If anything fails
  98. in the following steps then this is the very first thing to verify.
  99. A broken compiler installation usually manifests itself
  100. in failed ./configure tests (dlopen capabilities).
  101. Try
  102. # gcc -v
  103. # g++ -v
  104. on the commandline. If it says something about "command not found"
  105. then you miss some gcc related package. Install it from the distro cd.
  106. - You NEED the Qt library.
  107. You can download the latest version from ftp://ftp.trolltech.com.
  108. The main Qt www site is http://www.trolltech.com.
  109. Note for the GPL maniacs: Qt IS GPL.
  110. The minimum required version is 3.1.2 (older versions *might* work)
  111. Download and install it by following the rules
  112. explained in the excellent documentation that comes with the library.
  113. - You need a decent pthread implementation.
  114. This is usually included in your distribution and is probably
  115. already installed. The library is called libpthread.so.
  116. You can look for it with the "find" command:
  117. # find / -name libpthread.so
  118. On my system the output is:
  119. # /usr/lib/libpthread.so
  120. If you don't have it (the configure script will tell you)
  121. you can download it from your favorite GNU mirror.
  122. On Solaris you can use the native libthread.so library instead
  123. but you will have to pass the specific option to configure (see below).
  124. FreeBSD has a native implementation of pthreads in libc_r and
  125. the gcc compiler has a special -pthread flag to link to it.
  126. If you're on FreeBSD, use the --with-freebsd-pthread configure
  127. option and make sure that you don't have other pthread wrappers
  128. installed (that might collide with the native header files).
  129. The configure script will also fail if the library is
  130. hidden somewhere on your system (eg. not in /lib , /usr/lib or
  131. /usr/local/lib): you should probably move it.
  132. - You need the dynamic linker interface library libdl.so.
  133. This is usually installed on your system , so don't care until
  134. configure complatins about it. Some system have the interface
  135. builtin in libc. The configure script can detect it.
  136. - (Optional) If you want to compile the KDE integration support
  137. you obviousy need KDE. The tdelibs package should suffice.
  138. - (Optional) If you want the translations to non-english languages to work
  139. then you need the GNU gettext package. In particular KVIrc uses
  140. the msgfmt program.
  141. This is usually included in your distribution and is probably
  142. already installed. You can check it by running
  143. # msgfmt --version
  144. KVIrc will not complain if the command above is missing: it will
  145. just skip the creation of the translation files.
  146. If the command above fails then you need to install the gettext package
  147. if you want any language other than english.
  148. - (Optional) If you want DCC VOICE to support the gsm codec,
  149. you need a recent copy of libgsm. This is not strictly required
  150. at compile time since KVIrc will look for the library at run-time,
  151. and only if the DCC VOICE with the gsm codec is requested.
  152. You can check for libgsm using the 'find' command.
  153. # find / -name libgsm*
  154. The output should be sometihg like
  155. # /usr/lib/libgsm.so
  156. This library is included in most distributions. Some distros ship
  157. only the static version of the library "libgsm.a": if the previous
  158. find returned only something similar to "/usr/lib/libgsm.a" , you might
  159. create manually the shared archive by running:
  160. # cd /usr/lib
  161. # ld --whole-archive -shared -o libgsm.so.1 libgsm.a
  162. # ln -s libgsm.so.1 libgsm.so
  163. # ldconfig
  164. If you don't have it installed at all, you might have a look in your
  165. distribution CD, or download it from the web.
  166. - (Optional) If you want the /snd plugin to play various audio formats
  167. you either need a running artsd, a running esd or a reasonably recent
  168. audiofile library. Without these KVIrc will be only able to play *.au
  169. files.
  170. - (Optional) If you want to generate the on-line documentation
  171. you also need perl: any version will do (I guess).
  172. - (Optional) If you want the secure socket layer support to be compiled
  173. you need the OpenSSL library and headers. (libssl.so and openssl/ssl.h)
  174. - (Optional) If you want perl scripting support to be compiled
  175. you need a working perl installation. Your libperl.so MUST be compiled
  176. with the MULTIPLICITY option. (You can check it with perl -V).
  177. ###
  178. ### Step 2 : Running the configure script (mandatory)
  179. ###
  180. First of all you must run the configure script that will guess some
  181. info about your system and prepare the compilation.
  182. You may try to "simply run" it and check if it works...the configure
  183. script tries to be smart , but in some cases it will fail.
  184. So before running the script make sure that the enviroinement
  185. variable $TQTDIR points to the right location. This will help
  186. in finding the correct version of Qt.
  187. You might eventually set it with the command:
  188. # export TQTDIR="your qt dir"
  189. On my system qt is installed in /usr/local/kde/qt
  190. so I actually execute
  191. # export TQTDIR="/usr/local/kde/qt"
  192. If you want to compile the KDE support you might want to do the same
  193. with TDEDIR
  194. # export TDEDIR="your kde dir"
  195. In my case KDE is installed in /usr/local/kde so I use
  196. # export TDEDIR="/usr/local/kde"
  197. The configure script has a lot of options that can be listed by using
  198. # ./configure --help
  199. Here's a list with explainations (the most common are at the top):
  200. --enable-debug
  201. This is for debugging and reporting problems.
  202. It sets the compiler options in order to leave the debugging
  203. informations into the kvirc executable and the libraries.
  204. In this way you will be able to produce a gdb backtrace
  205. in case of a crash.
  206. YOU NEED THIS OPTION IF YOU WANT TO REPORT A PROGRAM CRASH.
  207. --enable-pipes
  208. Asks the compiler to use pipes instead of files for the
  209. compilation stage. The pipes will help in reducing disk usage and
  210. will probably shorten the compilation a bit. Use this option if
  211. your platform supports it.
  212. --with-qt-library-dir=<DIR>
  213. Look for the qt library in <DIR>.
  214. You might want to use this if the configure script has trouble
  215. in finding the qt library.
  216. You should have no problems if you use export TQTDIR="<DIR>"
  217. before launching the configure script, but it might help you
  218. if you have a non standard Qt installation.
  219. --with-qt-include-dir=<DIR>
  220. Look for the qt headers in <DIR>.
  221. You might want to use this if the configure script has trouble
  222. in finding the qt headers. It may especially help if your headers
  223. are in a place different than $TQTDIR/include (and thus you have
  224. a non standard installation)
  225. --with-qt-moc=<PATH>
  226. Use the qt meta-object compiler found in <PATH>
  227. The path is usually $TQTDIR/bin/moc , and the
  228. configure script will find it if you have a standard
  229. Qt installation and $TQTDIR points to the right directory.
  230. Thus should have no problems if you use export TQTDIR="<DIR>"
  231. before launching the configure script, but it might help you
  232. if you have a non standard Qt installation.
  233. This will also help if you have the moc compiler renamed
  234. in some way: like "moc2" or sth...
  235. <PATH> in this case is a FULL path: directory/program_name!
  236. --disable-qt-check
  237. This disables Qt checking at compilation time.
  238. If this is the only way to compile and run
  239. the kvirc executable , then there is something
  240. wrong with the configure script.
  241. --without-kde-support
  242. The configure script will look for the KDE headers and libraries
  243. and if found it will enable the KDE support. If you don't want
  244. the KDE support even if KDE is detected, just use this switch.
  245. --with-kde-library-dir=<DIR>
  246. Look for the KDE libraries in <DIR>
  247. If $TDEDIR points to the right place, you shouldn't need this.
  248. --with-kde-include-dir=<DIR>
  249. Look for the KDE headers in <DIR>
  250. If $TDEDIR points to the right place, you shouldn't need this.
  251. --with-kde-services-dir=<DIR>
  252. Install the kde service protocol files in <DIR>
  253. If $TDEDIR points to the right place, you shouldn't need this.
  254. This is also non-critical for kvirc: if the configure script
  255. can't find this directory, you will only looose the support for
  256. irc:// urls in konqueror
  257. --without-kde-check
  258. Similar to --without-qt-check but for KDE.
  259. --enable-optimisation=<NUMBER>
  260. Enables the compiler optimisation flag -o<NUMBER>.
  261. Possible values are 0 , 1, 2 and 3 (but if you compiler supports
  262. more optimisation levels , you might use other numbers here).
  263. Increases compilation time but may produce a slightly faster
  264. executable.
  265. --with-other-libs=<libraries>
  266. Explicitly link to the specified libraries.
  267. Example: --with-other-libs="-lmylib -lstrangesystemsupport"
  268. --with-other-ldirs=<paths>
  269. Explicitly add the specified library search paths
  270. Example: --with-other-ldirs="-L/home/pippo/lib/ -L/my/library/"
  271. --with-other-idirs
  272. Explicitly add the specified include search path
  273. Example: --with-other-idirs="-I/home/pippo/include/ -I/tmp/inc/"
  274. --enable-objprelink
  275. This is an experimental support for object prelinking that improves
  276. significantly the executable startup time. In order to use it you
  277. need to have the "objprelink" program in the PATH. The objprelink
  278. program is included in the distribution in the admin directory.
  279. In order to use it, you will need to:
  280. # cd admin
  281. # make objprelink
  282. # cp objprelink /somewhere_on_your_path
  283. All this AFTER running ./configure and BEFORE running make.
  284. --with-no-pthread-check
  285. Do not check if the pthread stuff works.
  286. If configure fails in the pthread library check , you might want to
  287. try this...(but then you will have really to "pray" that
  288. the check has been broken by some "unusual" conditions and the
  289. compilation will succeed).
  290. --x-includes=DIR
  291. Specifies explicitly the path to the X header files.
  292. You might want to use this if the configure script
  293. has trouble in finding it.
  294. --x-libraries=DIR
  295. Specifies explicitly the path to the X libraries.
  296. You might want to use this if the configure script
  297. has trouble in finding it.
  298. --with-qt-name=<NAME>
  299. Use <NAME> instead of "qt" as the Qt library name.
  300. This is useful on systems where Qt has been installed with
  301. a name different than the default "qt".
  302. It happens often that to allow multiple copies of qt to work
  303. the newest have the version name appended to it.
  304. For example, on FreeBSD I have found "qt" being Qt1.* and
  305. "qt2" being Qt 2.*. Since you need Qt 2.* for kvirc to work,
  306. you will need to use --with-qt-name=qt2.
  307. If you use this option, you will probably also need to remap
  308. the moc compiler path/name with --with-qt-moc.
  309. --disable-qt-mt
  310. Disable checking for the multithreaded version of Qt.
  311. By default , KVIrc will try to link to the multithreaded version
  312. if found on the system.
  313. NOTE: if you enable the KDE support , KVIrc MUST be linked to the
  314. qt library that KDE is linked to.
  315. --with-ix86-asm
  316. KVIrc contains some ix86 assembly routines that *could*
  317. performs some things faster (this is not always true, depends
  318. on the compiler). You might want to try it if your kvirc seems to
  319. be really slow...
  320. --without-ipv6-support
  321. The IPV6 support is compiled by default on the platforms that
  322. support it: this option disables it.
  323. Even if you have a plain IPV4-only connection, you might want to
  324. keep the IPV6 support: you will be able to lookup IPV6 hostnames.
  325. --without-system-memmove
  326. This will disable the use of the system memmove() memcpy() and
  327. memset() functions and enable the bundled implementations. Use
  328. it if you have undefined references to these functions while
  329. compiling.
  330. --with-ignore-sigalarm
  331. This is a hack mainly for Solaris.
  332. Use this option if kvirc exits with no apparent reason and
  333. the system prints a message related to an "Alarm" :)
  334. This is a mail that suggests an explaination for the SIGALARM fault.
  335. If you experience the problem please drop me a mail at pragma at kvirc dot net
  336. and we'll try to look for a solution.
  337. From: "Andre Stechert" (astechert at email dot com)
  338. Date: 26/7/2005 09:36
  339. Hi,
  340.         I noticed in your readme that you were having problems with sigalarm
  341. in your solaris port and you weren't sure why.  I quickly scanned your
  342. source code and noticed that you use usleep and threads.  That's the problem,
  343. if you haven't already figured it out. On Solaris, usleep is implemented with
  344. SIGALARM. So is threading. So if you the active thread changes while
  345. a usleep is in progress, bang, the process is dead.
  346. --without-crypt-support
  347. Disables the cryptographic engines and the whole
  348. cryptography/text-transformation support. Produces a slightly
  349. smaller executable. Anyway, if you don't know what the
  350. ctryptography/text-transformation
  351. support is ,I suggest you to avoid using this option.
  352. --enable-new-kvs
  353. Developers only!
  354. This enables the compilation of the new KVS parser, currently
  355. under heavy development. This will produce a bigger and possibly
  356. unstable executable: do not use if you don't know what you're doing.
  357. --enable-new-kvs-only
  358. Developers only!
  359. This hardwires the new KVS parser to be used as the main scripting
  360. engine in KVIrc. Be aware that the new KVS engine is NOT YET 100% COMPLETE
  361. so some scripts will simply fail.
  362. --without-transparency
  363. This option disables pseudo-transparency support.
  364. The pseudo transparency support makes the KVirc windows
  365. look like semi-transparent (this is NOT real transparency: this is
  366. just a nice-looking hack).
  367. If KDE support is enabled, KVirc will have an option that
  368. makes all windows use a faded KDE desktop background image
  369. as background. Without KDE support you will be able to choose
  370. a fake background image and use it as background. (You can still
  371. choose your desktop wallpaper: this will (more-or-less) work in
  372. all the window managers).
  373. It is cool-looking but usually eats some memory when enabled.
  374. It also eats some executable size.
  375. So this option allows to disable the pseudo-transparency.
  376. --with-solaris-lthread
  377. If you're on Solaris and don't have the pthread library (A wrapper
  378. I guess) you might try this option: it attempts to use the native
  379. Solaris threading support.
  380. --with-freebsd-pthread
  381. If you're on FreeBSD, you NEED this option. This enables the usage
  382. of the native FreeBSD pthread implementation found in libc_r.
  383. This requires you to use the native gcc compiler: it has a special
  384. -pthread flag that enables the linkage to libc_r instead
  385. of plain libc.
  386. --with-libresolv
  387. Link to libresolv. I guess that this is required for Solaris
  388. --with-libsocket
  389. Link to libsocket. I guess that this is required for Solaris
  390. --with-libnsl
  391. Link to libnsl. I guess that this is required for Solaris
  392. --with-libcompat
  393. Link to libcompat. This might be required for some systems...
  394. but I have no idea which ones. If you find it useful: mail me.
  395. --enable-fno-rtti
  396. Disables compiler runtime type information generation.
  397. This is probably needed only with qt-embedded.
  398. DON'T use it if you don't exactly know what it does.
  399. Actually this may even make KVIrc crash in some situations.
  400. For example the KDE sources use __dynamic_cast...
  401. --disable-x-support
  402. Disables completely the X Windows support.
  403. This is useful in environments where X is not needed to compile KVIrc
  404. such as Qt-Mac on MacOSX, QtEmbedded or Windows.
  405. This switch implies also --without-x-bell
  406. --without-x-bell
  407. Disables the usage of the XBell function (needed if you want to
  408. compile KVIrc with qt-embedded (no X at all))
  409. This is implied by --disable-x-support
  410. --with-qt-embedded
  411. You need this to compile KVIrc with qt-embedded
  412. --without-ipc
  413. Disables support for inter-process communication.
  414. You will be not able to send remote commands to running
  415. kvirc sessions: this basically means that every time you run
  416. the kvirc executable , a new session will be started.
  417. If you don't use this switch, a new session will be started
  418. only if no session is running on the same display or
  419. "new session" has been forced by a commandline switch.
  420. If a session is already running, the commandline will be
  421. passed to that session via IPC (X-event-based communication).
  422. This option saves some KB of the KVIrc executable,
  423. so if you're really short in memory , you might use it,
  424. otherwise, IPC is a nice feature.
  425. --without-dyn-labels
  426. You should not need this option.
  427. It disables compilation of code that relies on a particular
  428. compiler feature (jumping to a dynamic label with a goto).
  429. Not all compilers support this , but configure shoud detect
  430. it automatically. Anyway , if you get compilation errors on
  431. kvi_ircview.cpp, you may try this option...
  432. This may also help if the configure script seems to hang
  433. when checking for the "compiler dynamic label support".
  434. --without-splash-screen
  435. Do not compile the splash screen code.
  436. This will remove you that nice "banner" image that pops up
  437. while kvirc is starting up. It will maybe help in making an
  438. executable smaller by a couple of KB and save a couple
  439. of extra milliseconds during the startup. Use it if you're
  440. tring to build a performance critical executable and you're
  441. short both in memory and CPU time :)
  442. --without-gsm
  443. Explicitly disable the usage of the GSM library. This will
  444. disable the DCC VOICE gsm codec but might help when the
  445. compilation stops complaining of something related to GSM :)
  446. --without-dcc-sound
  447. Explicitly disable the DCC VOICE sound support. This might help
  448. if you have problems in compilation of src/modules/dcc/voice.cpp.
  449. It will disable the sound support
  450. (and thus make DCC VOICE not usable).
  451. --disable-ssl
  452. Disables the secure socket layer support. The SSL support is
  453. automatically enabled if OpenSSL is detected at ./configure time.
  454. This option forces it to be left out.
  455. --with-memory-profile
  456. Debug stuff...enables memory allocation profiling (don't use it :)
  457. --with-memory-checks
  458. Enables malloc() memory checks. This will print a nice message
  459. if your system goes out of memory...
  460. It can't save you from buying new RAM,
  461. but at least you will know that your system went out of memory
  462. and it is not a proper kvirc fault. Actually you probably have
  463. no reason in using it.
  464. --with-big-channels
  465. Minor hash table optimisations: higher memory usage but
  466. faster user lookups. Use it if you often stay in channels with
  467. a lot of users. (this is not critical anyway)
  468. --enable-profiling
  469. Asks the compiler/linker to include profiling informations in the
  470. executable. This is useful only if you want to profile KVIrc by
  471. using the gprof program. Note that this will generate a bigger
  472. and slower executable.
  473. --disable-perl
  474. Forcibly disable perl support.
  475. So finally you have to run
  476. # ./configure <your options>
  477. For example , my common options are:
  478. # ./configure --enable-pipes --enable-debug
  479. On FreeBSD I have found useful this command line:
  480. # ./configure --with-qt-name=qt2 --with-qt-moc=/<PATH_HERE>/moc2 \
  481. --with-freebsd-pthread
  482. Once the configure script ran succesfully you can go to the next step.
  483. ###
  484. ### Step 3 : Compiling (mandatory)
  485. ###
  486. This step is easy:
  487. Cross your fingers and run
  488. # make kvirc
  489. If your make is not a GNU make (this happens on FreeBSD for example)
  490. you should use "gmake" instead.
  491. The compilation process will take from 6-7 minutes to several hours
  492. depending on the machine capabilities and load.
  493. If you have a slow cpu but have a couple of computers in a lan you
  494. might consider using distcc to distribute the compilation.
  495. Once the compilation has been succesfull, run
  496. # make install
  497. Same as above: use "gmake install" if your make is not GNU make.
  498. This will install the executable in /usr/local/bin
  499. (if you don't have specified a different --prefix option in
  500. the configure script) , the libraries in /usr/local/lib
  501. and the shared data in /usr/local/share/kvirc.
  502. If you had a previous kvirc installation , the default prefix
  503. will be referring to the directory where the old kvirc
  504. executable was found.
  505. Make sure that /usr/local/lib is in your /etc/ld.so.conf ,
  506. if it isn't there , put it there and run
  507. # ldconfig
  508. If you have decided to use the KDE support the installation
  509. might have placed all these files in your $TDEDIR tree
  510. instead of /usr/local. In this case you should be OK since
  511. KDE requires its library dir to be in /etc/ld.so.conf
  512. ###
  513. ### Step 4: Having fun
  514. ###
  515. # kvirc &
  516. That's all folks.
  517. ###############################################################################
  518. # 5. Compiling KVIrc on qt-embedded
  519. ###############################################################################
  520. Do you want KVIrc 3 on your hand computer ?
  521. On your Nokia 9999910 ?
  522. On your LINUX CONSOLE?
  523. Well, for the third it's really easy, just follow carefully those steps:
  524. 1. Install qt-embedded libraries (including the development files).
  525. This can be as easy as: apt-get install libtqt-emb-dev on Debian.
  526. 2. cd to the KVIrc3 source directory
  527. 3. run configure with the following parameters:
  528. # ./configure --with-qt-name=qte --with-fno-rtti --without-x-calls
  529. --without-ipc --without-splash-screen --without-transparency
  530. --with-qt-embedded --without-x-bell
  531. then run make and make install as usual
  532. 4. Try to have a life for the next minutes while kvirc3 compiles
  533. 5. You need your kernel with framebuffer support (it's under 'Console')
  534. so if your kernel don't have it reconfigure and recompile your kernel.
  535. 6. switch to a console
  536. 7. export TQTDIR=[path] On Debian is '/usr'
  537. 8. Read http://doc.trolltech.com/3.0/envvars.html and configure your
  538. environment vars until kvirc3-emb loads (it will give you an error
  539. indicating what went wrong else). Pay especial attention to
  540. QWS_MOUSE_PROTO, QWS_CARD_SLOT and QWS_DISPLAY
  541. 9. Enjoy :)
  542. ###############################################################################
  543. # 6. Compiling KVIrc on MacOSX
  544. ###############################################################################
  545. There is a detailed compilation and installation HOWTO for MacOSX systems
  546. located in the doc dorectory.
  547. ###############################################################################
  548. # 7. A note about Windows 95/98/ME
  549. ###############################################################################
  550. On Windows versions prior to 2000 the KVIrc binary may refuse to start
  551. because of an incompatible msvcrt.dll included in the distribution.
  552. If this happens to you then you may try the following tricks:
  553. - Find msvcrt.dll in your C:\Windows directory. It may also be
  554. in C:\Windows\System or C:\Windows\System32
  555. Copy it to the KVIrc installation folder overwriting the existing
  556. msvcrt.dll shipped with kvirc.
  557. - Find msvcrt.dll somewhere on the net. An url hint might be:
  558. http://www.dll-files.com/dllindex/dll-files.shtml?msvcrt
  559. Download the file and copy it to the KVIrc installation folder
  560. overwriting the existing msvcrt.dll shipped with kvirc.
  561. If none of the two steps work for you please write a mail to
  562. pragma at kvirc dot net reporting your exact Windows version and build
  563. and including the exact messages that the system reports when trying
  564. to run the KVIrc executable.
  565. Thanx to Dusan Hokuv for reporting this and suggesting the fixes.