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.
 
 
 
 
 
 

238 lines
9.4 KiB

  1. See file README for libisoburn and xorriso specific installation instructions.
  2. This file here is rather a manual for advanced usage of ./configure
  3. -------------------------------------------------------------------
  4. Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
  5. 2006 Free Software Foundation, Inc.
  6. This file is free documentation; the Free Software Foundation gives
  7. unlimited permission to copy, distribute and modify it.
  8. Basic Installation
  9. ==================
  10. Briefly, the shell commands `./configure; make; make install' should
  11. configure, build, and install this package. The following
  12. more-detailed instructions are generic; see the `README' file for
  13. instructions specific to this package.
  14. The `configure' shell script attempts to guess correct values for
  15. various system-dependent variables used during compilation. It uses
  16. those values to create a `Makefile' in each directory of the package.
  17. It may also create one or more `.h' files containing system-dependent
  18. definitions. Finally, it creates a shell script `config.status' that
  19. you can run in the future to recreate the current configuration, and a
  20. file `config.log' containing compiler output (useful mainly for
  21. debugging `configure').
  22. It can also use an optional file (typically called `config.cache'
  23. and enabled with `--cache-file=config.cache' or simply `-C') that saves
  24. the results of its tests to speed up reconfiguring. Caching is
  25. disabled by default to prevent problems with accidental use of stale
  26. cache files.
  27. If you need to do unusual things to compile the package, please try
  28. to figure out how `configure' could check whether to do them, and mail
  29. diffs or instructions to the address given in the `README' so they can
  30. be considered for the next release. If you are using the cache, and at
  31. some point `config.cache' contains results you don't want to keep, you
  32. may remove or edit it.
  33. The file `configure.ac' (or `configure.in') is used to create
  34. `configure' by a program called `autoconf'. You need `configure.ac' if
  35. you want to change it or regenerate `configure' using a newer version
  36. of `autoconf'.
  37. The simplest way to compile this package is:
  38. 1. `cd' to the directory containing the package's source code and type
  39. `./configure' to configure the package for your system.
  40. Running `configure' might take a while. While running, it prints
  41. some messages telling which features it is checking for.
  42. 2. Type `make' to compile the package.
  43. 3. Optionally, type `make check' to run any self-tests that come with
  44. the package.
  45. 4. Type `make install' to install the programs and any data files and
  46. documentation.
  47. 5. You can remove the program binaries and object files from the
  48. source code directory by typing `make clean'. To also remove the
  49. files that `configure' created (so you can compile the package for
  50. a different kind of computer), type `make distclean'. There is
  51. also a `make maintainer-clean' target, but that is intended mainly
  52. for the package's developers. If you use it, you may have to get
  53. all sorts of other programs in order to regenerate files that came
  54. with the distribution.
  55. Compilers and Options
  56. =====================
  57. Some systems require unusual options for compilation or linking that the
  58. `configure' script does not know about. Run `./configure --help' for
  59. details on some of the pertinent environment variables.
  60. You can give `configure' initial values for configuration parameters
  61. by setting variables in the command line or in the environment. Here
  62. is an example:
  63. ./configure CC=c99 CFLAGS=-g LIBS=-lposix
  64. *Note Defining Variables::, for more details.
  65. Compiling For Multiple Architectures
  66. ====================================
  67. You can compile the package for more than one kind of computer at the
  68. same time, by placing the object files for each architecture in their
  69. own directory. To do this, you can use 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. With a non-GNU `make', it is safer to compile the package for one
  74. architecture at a time in the source code directory. After you have
  75. installed the package for one architecture, use `make distclean' before
  76. reconfiguring for another architecture.
  77. Installation Names
  78. ==================
  79. By default, `make install' installs the package's commands under
  80. `/usr/local/bin', include files under `/usr/local/include', etc. You
  81. can specify an installation prefix other than `/usr/local' by giving
  82. `configure' the option `--prefix=PREFIX'.
  83. You can specify separate installation prefixes for
  84. architecture-specific files and architecture-independent files. If you
  85. pass the option `--exec-prefix=PREFIX' to `configure', the package uses
  86. PREFIX as the prefix for installing programs and libraries.
  87. Documentation and other data files still use the regular prefix.
  88. In addition, if you use an unusual directory layout you can give
  89. options like `--bindir=DIR' to specify different values for particular
  90. kinds of files. Run `configure --help' for a list of the directories
  91. you can set and what kinds of files go in them.
  92. If the package supports it, you can cause programs to be installed
  93. with an extra prefix or suffix on their names by giving `configure' the
  94. option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  95. Optional Features
  96. =================
  97. Some packages pay attention to `--enable-FEATURE' options to
  98. `configure', where FEATURE indicates an optional part of the package.
  99. They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  100. is something like `gnu-as' or `x' (for the X Window System). The
  101. `README' should mention any `--enable-' and `--with-' options that the
  102. package recognizes.
  103. For packages that use the X Window System, `configure' can usually
  104. find the X include and library files automatically, but if it doesn't,
  105. you can use the `configure' options `--x-includes=DIR' and
  106. `--x-libraries=DIR' to specify their locations.
  107. Specifying the System Type
  108. ==========================
  109. There may be some features `configure' cannot figure out automatically,
  110. but needs to determine by the type of machine the package will run on.
  111. Usually, assuming the package is built to be run on the _same_
  112. architectures, `configure' can figure that out, but if it prints a
  113. message saying it cannot guess the machine type, give it the
  114. `--build=TYPE' option. TYPE can either be a short name for the system
  115. type, such as `sun4', or a canonical name which has the form:
  116. CPU-COMPANY-SYSTEM
  117. where SYSTEM can have one of these forms:
  118. OS KERNEL-OS
  119. See the file `config.sub' for the possible values of each field. If
  120. `config.sub' isn't included in this package, then this package doesn't
  121. need to know the machine type.
  122. If you are _building_ compiler tools for cross-compiling, you should
  123. use the option `--target=TYPE' to select the type of system they will
  124. produce code for.
  125. If you want to _use_ a cross compiler, that generates code for a
  126. platform different from the build platform, you should specify the
  127. "host" platform (i.e., that on which the generated programs will
  128. eventually be run) with `--host=TYPE'.
  129. Sharing Defaults
  130. ================
  131. If you want to set default values for `configure' scripts to share, you
  132. can create a site shell script called `config.site' that gives default
  133. values for variables like `CC', `cache_file', and `prefix'.
  134. `configure' looks for `PREFIX/share/config.site' if it exists, then
  135. `PREFIX/etc/config.site' if it exists. Or, you can set the
  136. `CONFIG_SITE' environment variable to the location of the site script.
  137. A warning: not all `configure' scripts look for a site script.
  138. Defining Variables
  139. ==================
  140. Variables not defined in a site shell script can be set in the
  141. environment passed to `configure'. However, some packages may run
  142. configure again during the build, and the customized values of these
  143. variables may be lost. In order to avoid this problem, you should set
  144. them in the `configure' command line, using `VAR=value'. For example:
  145. ./configure CC=/usr/local2/bin/gcc
  146. causes the specified `gcc' to be used as the C compiler (unless it is
  147. overridden in the site shell script).
  148. Unfortunately, this technique does not work for `CONFIG_SHELL' due to
  149. an Autoconf bug. Until the bug is fixed you can use this workaround:
  150. CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
  151. `configure' Invocation
  152. ======================
  153. `configure' recognizes the following options to control how it operates.
  154. `--help'
  155. `-h'
  156. Print a summary of the options to `configure', and exit.
  157. `--version'
  158. `-V'
  159. Print the version of Autoconf used to generate the `configure'
  160. script, and exit.
  161. `--cache-file=FILE'
  162. Enable the cache: use and save the results of the tests in FILE,
  163. traditionally `config.cache'. FILE defaults to `/dev/null' to
  164. disable caching.
  165. `--config-cache'
  166. `-C'
  167. Alias for `--cache-file=config.cache'.
  168. `--quiet'
  169. `--silent'
  170. `-q'
  171. Do not print messages saying which checks are being made. To
  172. suppress all normal output, redirect it to `/dev/null' (any error
  173. messages will still be shown).
  174. `--srcdir=DIR'
  175. Look for the package's source code in directory DIR. Usually
  176. `configure' can determine that directory automatically.
  177. `configure' also accepts some other, not widely useful, options. Run
  178. `configure --help' for more details.