KShowMail – show mails on a POP3 server
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.

177 lines
7.3KB

  1. Basic Installation
  2. ==================
  3. These are generic installation instructions.
  4. The `configure' shell script attempts to guess correct values for
  5. various system-dependent variables used during compilation. It uses
  6. those values to create a `Makefile' in each directory of the package.
  7. It may also create one or more `.h' files containing system-dependent
  8. definitions. Finally, it creates a shell script `config.status' that
  9. you can run in the future to recreate the current configuration, a file
  10. `config.cache' that saves the results of its tests to speed up
  11. reconfiguring, and a file `config.log' containing compiler output
  12. (useful mainly for debugging `configure').
  13. If you need to do unusual things to compile the package, please try
  14. to figure out how `configure' could check whether to do them, and mail
  15. diffs or instructions to the address given in the `README' so they can
  16. be considered for the next release. If at some point `config.cache'
  17. contains results you don't want to keep, you may remove or edit it.
  18. The file `configure.in' is used to create `configure' by a program
  19. called `autoconf'. You only need `configure.in' if you want to change
  20. it or regenerate `configure' using a newer version of `autoconf'.
  21. It is useful to set the TDEDIR environment variable to the proper location.
  22. For SuSE this is /opt/kde3. Before starting, enter
  23. export TDEDIR=/opt/kde3
  24. The simplest way to compile this package is:
  25. 1. `cd' to the directory containing the package's source code and type
  26. `./configure' to configure the package for your system. If you're
  27. using `csh' on an old version of System V, you might need to type
  28. `sh ./configure' instead to prevent `csh' from trying to execute
  29. `configure' itself.
  30. If TDEDIR is not set, it can be helpful to run configure with the --prefix option:
  31. ./configure --prefix=/opt/kde3
  32. Running `configure' takes a while. While running, it prints some
  33. messages telling which features it is checking for.
  34. 2. Type `make' to compile the package.
  35. 3. Type `make install' to install the programs and any data files and
  36. documentation. Read the output of the install process carefully and
  37. verify the files have been installed in the correct locations. If the
  38. directory is wrong (not a subdirectory of TDEDIR) the icons will not be found.
  39. 4. You can remove the program binaries and object files from the
  40. source code directory by typing `make clean'.
  41. Compilers and Options
  42. =====================
  43. Some systems require unusual options for compilation or linking that
  44. the `configure' script does not know about. You can give `configure'
  45. initial values for variables by setting them in the environment. Using
  46. a Bourne-compatible shell, you can do that on the command line like
  47. this:
  48. CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
  49. Or on systems that have the `env' program, you can do it like this:
  50. env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
  51. Compiling For Multiple Architectures
  52. ====================================
  53. You can compile the package for more than one kind of computer at the
  54. same time, by placing the object files for each architecture in their
  55. own directory. To do this, you must use a version of `make' that
  56. supports the `VPATH' variable, such as GNU `make'. `cd' to the
  57. directory where you want the object files and executables to go and run
  58. the `configure' script. `configure' automatically checks for the
  59. source code in the directory that `configure' is in and in `..'.
  60. If you have to use a `make' that does not supports the `VPATH'
  61. variable, you have to compile the package for one architecture at a time
  62. in the source code directory. After you have installed the package for
  63. one architecture, use `make distclean' before reconfiguring for another
  64. architecture.
  65. Installation Names
  66. ==================
  67. By default, `make install' will install the package's files in
  68. `/usr/local/bin', `/usr/local/man', etc. You can specify an
  69. installation prefix other than `/usr/local' by giving `configure' the
  70. option `--prefix=PATH'.
  71. You can specify separate installation prefixes for
  72. architecture-specific files and architecture-independent files. If you
  73. give `configure' the option `--exec-prefix=PATH', the package will use
  74. PATH as the prefix for installing programs and libraries.
  75. Documentation and other data files will still use the regular prefix.
  76. If the package supports it, you can cause programs to be installed
  77. with an extra prefix or suffix on their names by giving `configure' the
  78. option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  79. Optional Features
  80. =================
  81. Some packages pay attention to `--enable-FEATURE' options to
  82. `configure', where FEATURE indicates an optional part of the package.
  83. They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  84. is something like `gnu-as' or `x' (for the X Window System). The
  85. `README' should mention any `--enable-' and `--with-' options that the
  86. package recognizes.
  87. For packages that use the X Window System, `configure' can usually
  88. find the X include and library files automatically, but if it doesn't,
  89. you can use the `configure' options `--x-includes=DIR' and
  90. `--x-libraries=DIR' to specify their locations.
  91. Specifying the System Type
  92. ==========================
  93. There may be some features `configure' can not figure out
  94. automatically, but needs to determine by the type of host the package
  95. will run on. Usually `configure' can figure that out, but if it prints
  96. a message saying it can not guess the host type, give it the
  97. `--host=TYPE' option. TYPE can either be a short name for the system
  98. type, such as `sun4', or a canonical name with three fields:
  99. CPU-COMPANY-SYSTEM
  100. See the file `config.sub' for the possible values of each field. If
  101. `config.sub' isn't included in this package, then this package doesn't
  102. need to know the host type.
  103. If you are building compiler tools for cross-compiling, you can also
  104. use the `--target=TYPE' option to select the type of system they will
  105. produce code for and the `--build=TYPE' option to select the type of
  106. system on which you are compiling the package.
  107. Sharing Defaults
  108. ================
  109. If you want to set default values for `configure' scripts to share,
  110. you can create a site shell script called `config.site' that gives
  111. default values for variables like `CC', `cache_file', and `prefix'.
  112. `configure' looks for `PREFIX/share/config.site' if it exists, then
  113. `PREFIX/etc/config.site' if it exists. Or, you can set the
  114. `CONFIG_SITE' environment variable to the location of the site script.
  115. A warning: not all `configure' scripts look for a site script.
  116. Operation Controls
  117. ==================
  118. `configure' recognizes the following options to control how it
  119. operates.
  120. `--cache-file=FILE'
  121. Use and save the results of the tests in FILE instead of
  122. `./config.cache'. Set FILE to `/dev/null' to disable caching, for
  123. debugging `configure'.
  124. `--help'
  125. Print a summary of the options to `configure', and exit.
  126. `--quiet'
  127. `--silent'
  128. `-q'
  129. Do not print messages saying which checks are being made.
  130. `--srcdir=DIR'
  131. Look for the package's source code in directory DIR. Usually
  132. `configure' can determine that directory automatically.
  133. `--version'
  134. Print the version of Autoconf used to generate the `configure'
  135. script, and exit.
  136. `configure' also accepts some other, not widely useful, options.