TDE base libraries and programs
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 7.9KB

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