TorK – anonymity manager for TDE
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.

230 lines
8.5 KiB

  1. Before Compiling
  2. ----------------
  3. To compile TorK you will need to have a number of specific packages installed. The
  4. actual name of these packages will vary according to your distribution. These packages
  5. will not only enable you to compile TorK but pretty much any GNU/Linux application
  6. from source.
  7. If you have the disk space, I recommend just installing every package that has either
  8. 'lib' or 'dev' in the title. This will save you no end of bother now and in the future.
  9. If you want to be selective, the list below provides guidance on the keywords to search
  10. for on your installation CD or vendor package repository. The list below is an absolute
  11. minimum. Your vendor may use the term 'devel' or even 'lib' instead of 'dev' in the list
  12. below.
  13. - gcc (c compiler)
  14. - glibc-dev
  15. - gcc-c++ (c++ compiler)
  16. - libstdc++-dev (c++ standard library)
  17. - make (compilation manager)
  18. - automake, autoconf (compilation toolchain)
  19. - libgtk+-dev, libglib-dev (gnome libraries)
  20. - libgr-dev, libungif-dev, libjpeg-dev, libpng-dev, libtiff-dev, libxpm-dev (image libraries)
  21. - XFree86-dev (necessary for graphics programs)
  22. - zlib-dev (compression)
  23. - libtqt or libtqt-dev or qt-dev (QT development libraries)
  24. - openssl
  25. - Any package with kde and dev in the title.
  26. - Any package with kde and lib in the title.
  27. Compiling
  28. ---------
  29. To compile:
  30. ./configure
  31. make
  32. su -c 'make install'
  33. To compile and install from CVS:
  34. cd ~
  35. mkdir torkcvs
  36. cd torkcvs
  37. cvs -z3 co -P tork
  38. cd tork
  39. make -f Makefile.cvs
  40. ./configure
  41. make
  42. su -c 'make install'
  43. ---
  44. Basic Installation
  45. ==================
  46. These are generic installation instructions.
  47. The `configure' shell script attempts to guess correct values for
  48. various system-dependent variables used during compilation. It uses
  49. those values to create a `Makefile' in each directory of the package.
  50. It may also create one or more `.h' files containing system-dependent
  51. definitions. Finally, it creates a shell script `config.status' that
  52. you can run in the future to recreate the current configuration, a file
  53. `config.cache' that saves the results of its tests to speed up
  54. reconfiguring, and a file `config.log' containing compiler output
  55. (useful mainly for debugging `configure').
  56. If you need to do unusual things to compile the package, please try
  57. to figure out how `configure' could check whether to do them, and mail
  58. diffs or instructions to the address given in the `README' so they can
  59. be considered for the next release. If at some point `config.cache'
  60. contains results you don't want to keep, you may remove or edit it.
  61. The file `' is used to create `configure' by a program
  62. called `autoconf'. You only need `' if you want to change
  63. it or regenerate `configure' using a newer version of `autoconf'.
  64. The simplest way to compile this package is:
  65. 1. `cd' to the directory containing the package's source code and type
  66. `./configure' to configure the package for your system. If you're
  67. using `csh' on an old version of System V, you might need to type
  68. `sh ./configure' instead to prevent `csh' from trying to execute
  69. `configure' itself.
  70. Running `configure' takes a while. While running, it prints some
  71. messages telling which features it is checking for.
  72. 2. Type `make' to compile the package.
  73. 3. Type `make install' to install the programs and any data files and
  74. documentation.
  75. 4. You can remove the program binaries and object files from the
  76. source code directory by typing `make clean'.
  77. Compilers and Options
  78. =====================
  79. Some systems require unusual options for compilation or linking that
  80. the `configure' script does not know about. You can give `configure'
  81. initial values for variables by setting them in the environment. Using
  82. a Bourne-compatible shell, you can do that on the command line like
  83. this:
  84. CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
  85. Or on systems that have the `env' program, you can do it like this:
  86. env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
  87. Compiling For Multiple Architectures
  88. ====================================
  89. You can compile the package for more than one kind of computer at the
  90. same time, by placing the object files for each architecture in their
  91. own directory. To do this, you must use a version of `make' that
  92. supports the `VPATH' variable, such as GNU `make'. `cd' to the
  93. directory where you want the object files and executables to go and run
  94. the `configure' script. `configure' automatically checks for the
  95. source code in the directory that `configure' is in and in `..'.
  96. If you have to use a `make' that does not supports the `VPATH'
  97. variable, you have to compile the package for one architecture at a time
  98. in the source code directory. After you have installed the package for
  99. one architecture, use `make distclean' before reconfiguring for another
  100. architecture.
  101. Installation Names
  102. ==================
  103. By default, `make install' will install the package's files in
  104. `/usr/local/bin', `/usr/local/man', etc. You can specify an
  105. installation prefix other than `/usr/local' by giving `configure' the
  106. option `--prefix=PATH'.
  107. You can specify separate installation prefixes for
  108. architecture-specific files and architecture-independent files. If you
  109. give `configure' the option `--exec-prefix=PATH', the package will use
  110. PATH as the prefix for installing programs and libraries.
  111. Documentation and other data files will still use the regular prefix.
  112. If the package supports it, you can cause programs to be installed
  113. with an extra prefix or suffix on their names by giving `configure' the
  114. option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  115. Optional Features
  116. =================
  117. Some packages pay attention to `--enable-FEATURE' options to
  118. `configure', where FEATURE indicates an optional part of the package.
  119. They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  120. is something like `gnu-as' or `x' (for the X Window System). The
  121. `README' should mention any `--enable-' and `--with-' options that the
  122. package recognizes.
  123. For packages that use the X Window System, `configure' can usually
  124. find the X include and library files automatically, but if it doesn't,
  125. you can use the `configure' options `--x-includes=DIR' and
  126. `--x-libraries=DIR' to specify their locations.
  127. Specifying the System Type
  128. ==========================
  129. There may be some features `configure' can not figure out
  130. automatically, but needs to determine by the type of host the package
  131. will run on. Usually `configure' can figure that out, but if it prints
  132. a message saying it can not guess the host type, give it the
  133. `--host=TYPE' option. TYPE can either be a short name for the system
  134. type, such as `sun4', or a canonical name with three fields:
  136. See the file `config.sub' for the possible values of each field. If
  137. `config.sub' isn't included in this package, then this package doesn't
  138. need to know the host type.
  139. If you are building compiler tools for cross-compiling, you can also
  140. use the `--target=TYPE' option to select the type of system they will
  141. produce code for and the `--build=TYPE' option to select the type of
  142. system on which you are compiling the package.
  143. Sharing Defaults
  144. ================
  145. If you want to set default values for `configure' scripts to share,
  146. you can create a site shell script called `' that gives
  147. default values for variables like `CC', `cache_file', and `prefix'.
  148. `configure' looks for `PREFIX/share/' if it exists, then
  149. `PREFIX/etc/' if it exists. Or, you can set the
  150. `CONFIG_SITE' environment variable to the location of the site script.
  151. A warning: not all `configure' scripts look for a site script.
  152. Operation Controls
  153. ==================
  154. `configure' recognizes the following options to control how it
  155. operates.
  156. `--cache-file=FILE'
  157. Use and save the results of the tests in FILE instead of
  158. `./config.cache'. Set FILE to `/dev/null' to disable caching, for
  159. debugging `configure'.
  160. `--help'
  161. Print a summary of the options to `configure', and exit.
  162. `--quiet'
  163. `--silent'
  164. `-q'
  165. Do not print messages saying which checks are being made.
  166. `--srcdir=DIR'
  167. Look for the package's source code in directory DIR. Usually
  168. `configure' can determine that directory automatically.
  169. `--version'
  170. Print the version of Autoconf used to generate the `configure'
  171. script, and exit.
  172. `configure' also accepts some other, not widely useful, options.
  173. cd ~
  174. mkdir torkcvs
  175. cd torkcvs
  176. cvs -z3 co -P tork
  177. cd tork
  178. make -f Makefile.cvs
  179. ./configure
  180. make
  181. su -c 'make install'