/src/FreeImage/Source/LibMNG/README.autoconf

https://bitbucket.org/cabalistic/ogredeps/ · Unknown · 213 lines · 163 code · 50 blank · 0 comment · 0 complexity · ffee9cb2655151a437cb7a316cf8835e MD5 · raw file

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