aRts audio 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.

INSTALL 7.5KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180
  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 `make' to compile the package.
  33. 3. Optionally, type `make check' to run any self-tests that come with
  34. the package.
  35. 4. Type `make install' to install the programs and any data files and
  36. documentation.
  37. 5. You can remove the program binaries and object files from the
  38. source code directory by typing `make clean'. To also remove the
  39. files that `configure' created (so you can compile the package for
  40. a different kind of computer), type `make distclean'. There is
  41. also a `make maintainer-clean' target, but that is intended mainly
  42. for the package's developers. If you use it, you may have to get
  43. all sorts of other programs in order to regenerate files that came
  44. with the distribution.
  45. Compilers and Options
  46. =====================
  47. Some systems require unusual options for compilation or linking that
  48. the `configure' script does not know about. You can give `configure'
  49. initial values for variables by setting them in the environment. Using
  50. a Bourne-compatible shell, you can do that on the command line like
  51. this:
  52. CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
  53. Or on systems that have the `env' program, you can do it like this:
  54. env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
  55. Compiling For Multiple Architectures
  56. ====================================
  57. You can compile the package for more than one kind of computer at the
  58. same time, by placing the object files for each architecture in their
  59. own directory. To do this, you must use a version of `make' that
  60. supports the `VPATH' variable, such as GNU `make'. `cd' to the
  61. directory where you want the object files and executables to go and run
  62. the `configure' script. `configure' automatically checks for the
  63. source code in the directory that `configure' is in and in `..'.
  64. If you have to use a `make' that does not supports the `VPATH'
  65. variable, you have to compile the package for one architecture at a time
  66. in the source code directory. After you have installed the package for
  67. one architecture, use `make distclean' before reconfiguring for another
  68. architecture.
  69. Installation Names
  70. ==================
  71. By default, `make install' will install the package's files in
  72. `/usr/local/kde/bin', `/usr/local/kde/lib', etc. You can specify an
  73. installation prefix other than `/usr/local/kde' by giving `configure'
  74. the option `--prefix=PATH'.
  75. You can specify separate installation prefixes for
  76. architecture-specific files and architecture-independent files. If you
  77. give `configure' the option `--exec-prefix=PATH', the package will use
  78. PATH as the prefix for installing programs and libraries.
  79. Documentation and other data files will still use the regular prefix.
  80. If the package supports it, you can cause programs to be installed
  81. with an extra prefix or suffix on their names by giving `configure' the
  82. option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  83. Optional Features
  84. =================
  85. Some packages pay attention to `--enable-FEATURE' options to
  86. `configure', where FEATURE indicates an optional part of the package.
  87. They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  88. is something like `gnu-as' or `x' (for the X Window System). The
  89. `README' should mention any `--enable-' and `--with-' options that the
  90. package recognizes.
  91. For packages that use the X Window System, `configure' can usually
  92. find the X include and library files automatically, but if it doesn't,
  93. you can use the `configure' options `--x-includes=DIR' and
  94. `--x-libraries=DIR' to specify their locations.
  95. Specifying the System Type
  96. ==========================
  97. There may be some features `configure' can not figure out
  98. automatically, but needs to determine by the type of host the package
  99. will run on. Usually `configure' can figure that out, but if it prints
  100. a message saying it can not guess the host type, give it the
  101. `--host=TYPE' option. TYPE can either be a short name for the system
  102. type, such as `sun4', or a canonical name with three fields:
  103. CPU-COMPANY-SYSTEM
  104. See the file `config.sub' for the possible values of each field. If
  105. `config.sub' isn't included in this package, then this package doesn't
  106. need to know the host type.
  107. If you are building compiler tools for cross-compiling, you can also
  108. use the `--target=TYPE' option to select the type of system they will
  109. produce code for and the `--build=TYPE' option to select the type of
  110. system on which you are compiling the package.
  111. Sharing Defaults
  112. ================
  113. If you want to set default values for `configure' scripts to share,
  114. you can create a site shell script called `config.site' that gives
  115. default values for variables like `CC', `cache_file', and `prefix'.
  116. `configure' looks for `PREFIX/share/config.site' if it exists, then
  117. `PREFIX/etc/config.site' if it exists. Or, you can set the
  118. `CONFIG_SITE' environment variable to the location of the site script.
  119. A warning: not all `configure' scripts look for a site script.
  120. Operation Controls
  121. ==================
  122. `configure' recognizes the following options to control how it
  123. operates.
  124. `--cache-file=FILE'
  125. Use and save the results of the tests in FILE instead of
  126. `./config.cache'. Set FILE to `/dev/null' to disable caching, for
  127. debugging `configure'.
  128. `--help'
  129. Print a summary of the options to `configure', and exit.
  130. `--quiet'
  131. `--silent'
  132. `-q'
  133. Do not print messages saying which checks are being made.
  134. `--srcdir=DIR'
  135. Look for the package's source code in directory DIR. Usually
  136. `configure' can determine that directory automatically.
  137. `--version'
  138. Print the version of Autoconf used to generate the `configure'
  139. script, and exit.
  140. `configure' also accepts some other, not widely useful, options.