An utility designed to convert polychromatic images to monochromatic images, creating shades of grey through an optical illusion.
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 15KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370
  1. Installation Instructions
  2. *************************
  3. Copyright (C) 1994-1996, 1999-2002, 2004-2013 Free Software Foundation,
  4. Inc.
  5. Copying and distribution of this file, with or without modification,
  6. are permitted in any medium without royalty provided the copyright
  7. notice and this notice are preserved. This file is offered as-is,
  8. without warranty of any kind.
  9. Basic Installation
  10. ==================
  11. Briefly, the shell command `./configure && make && make install'
  12. should configure, build, and install this package. The following
  13. more-detailed instructions are generic; see the `README' file for
  14. instructions specific to this package. Some packages provide this
  15. `INSTALL' file but do not implement all of the features documented
  16. below. The lack of an optional feature in a given package is not
  17. necessarily a bug. More recommendations for GNU packages can be found
  18. in *note Makefile Conventions: (standards)Makefile Conventions.
  19. The `configure' shell script attempts to guess correct values for
  20. various system-dependent variables used during compilation. It uses
  21. those values to create a `Makefile' in each directory of the package.
  22. It may also create one or more `.h' files containing system-dependent
  23. definitions. Finally, it creates a shell script `config.status' that
  24. you can run in the future to recreate the current configuration, and a
  25. file `config.log' containing compiler output (useful mainly for
  26. debugging `configure').
  27. It can also use an optional file (typically called `config.cache'
  28. and enabled with `--cache-file=config.cache' or simply `-C') that saves
  29. the results of its tests to speed up reconfiguring. Caching is
  30. disabled by default to prevent problems with accidental use of stale
  31. cache files.
  32. If you need to do unusual things to compile the package, please try
  33. to figure out how `configure' could check whether to do them, and mail
  34. diffs or instructions to the address given in the `README' so they can
  35. be considered for the next release. If you are using the cache, and at
  36. some point `config.cache' contains results you don't want to keep, you
  37. may remove or edit it.
  38. The file `configure.ac' (or `configure.in') is used to create
  39. `configure' by a program called `autoconf'. You need `configure.ac' if
  40. you want to change it or regenerate `configure' using a newer version
  41. of `autoconf'.
  42. The simplest way to compile this package is:
  43. 1. `cd' to the directory containing the package's source code and type
  44. `./configure' to configure the package for your system.
  45. Running `configure' might take a while. While running, it prints
  46. some messages telling which features it is checking for.
  47. 2. Type `make' to compile the package.
  48. 3. Optionally, type `make check' to run any self-tests that come with
  49. the package, generally using the just-built uninstalled binaries.
  50. 4. Type `make install' to install the programs and any data files and
  51. documentation. When installing into a prefix owned by root, it is
  52. recommended that the package be configured and built as a regular
  53. user, and only the `make install' phase executed with root
  54. privileges.
  55. 5. Optionally, type `make installcheck' to repeat any self-tests, but
  56. this time using the binaries in their final installed location.
  57. This target does not install anything. Running this target as a
  58. regular user, particularly if the prior `make install' required
  59. root privileges, verifies that the installation completed
  60. correctly.
  61. 6. You can remove the program binaries and object files from the
  62. source code directory by typing `make clean'. To also remove the
  63. files that `configure' created (so you can compile the package for
  64. a different kind of computer), type `make distclean'. There is
  65. also a `make maintainer-clean' target, but that is intended mainly
  66. for the package's developers. If you use it, you may have to get
  67. all sorts of other programs in order to regenerate files that came
  68. with the distribution.
  69. 7. Often, you can also type `make uninstall' to remove the installed
  70. files again. In practice, not all packages have tested that
  71. uninstallation works correctly, even though it is required by the
  72. GNU Coding Standards.
  73. 8. Some packages, particularly those that use Automake, provide `make
  74. distcheck', which can by used by developers to test that all other
  75. targets like `make install' and `make uninstall' work correctly.
  76. This target is generally not run by end users.
  77. Compilers and Options
  78. =====================
  79. Some systems require unusual options for compilation or linking that
  80. the `configure' script does not know about. Run `./configure --help'
  81. for details on some of the pertinent environment variables.
  82. You can give `configure' initial values for configuration parameters
  83. by setting variables in the command line or in the environment. Here
  84. is an example:
  85. ./configure CC=c99 CFLAGS=-g LIBS=-lposix
  86. *Note Defining Variables::, for more details.
  87. Compiling For Multiple Architectures
  88. ====================================
  89. You can compile the package for more than one kind of computer at the
  90. same time, by placing the object files for each architecture in their
  91. own directory. To do this, you can use GNU `make'. `cd' to the
  92. directory where you want the object files and executables to go and run
  93. the `configure' script. `configure' automatically checks for the
  94. source code in the directory that `configure' is in and in `..'. This
  95. is known as a "VPATH" build.
  96. With a non-GNU `make', it is safer to compile the package for one
  97. architecture at a time in the source code directory. After you have
  98. installed the package for one architecture, use `make distclean' before
  99. reconfiguring for another architecture.
  100. On MacOS X 10.5 and later systems, you can create libraries and
  101. executables that work on multiple system types--known as "fat" or
  102. "universal" binaries--by specifying multiple `-arch' options to the
  103. compiler but only a single `-arch' option to the preprocessor. Like
  104. this:
  105. ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
  106. CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
  107. CPP="gcc -E" CXXCPP="g++ -E"
  108. This is not guaranteed to produce working output in all cases, you
  109. may have to build one architecture at a time and combine the results
  110. using the `lipo' tool if you have problems.
  111. Installation Names
  112. ==================
  113. By default, `make install' installs the package's commands under
  114. `/usr/local/bin', include files under `/usr/local/include', etc. You
  115. can specify an installation prefix other than `/usr/local' by giving
  116. `configure' the option `--prefix=PREFIX', where PREFIX must be an
  117. absolute file name.
  118. You can specify separate installation prefixes for
  119. architecture-specific files and architecture-independent files. If you
  120. pass the option `--exec-prefix=PREFIX' to `configure', the package uses
  121. PREFIX as the prefix for installing programs and libraries.
  122. Documentation and other data files still use the regular prefix.
  123. In addition, if you use an unusual directory layout you can give
  124. options like `--bindir=DIR' to specify different values for particular
  125. kinds of files. Run `configure --help' for a list of the directories
  126. you can set and what kinds of files go in them. In general, the
  127. default for these options is expressed in terms of `${prefix}', so that
  128. specifying just `--prefix' will affect all of the other directory
  129. specifications that were not explicitly provided.
  130. The most portable way to affect installation locations is to pass the
  131. correct locations to `configure'; however, many packages provide one or
  132. both of the following shortcuts of passing variable assignments to the
  133. `make install' command line to change installation locations without
  134. having to reconfigure or recompile.
  135. The first method involves providing an override variable for each
  136. affected directory. For example, `make install
  137. prefix=/alternate/directory' will choose an alternate location for all
  138. directory configuration variables that were expressed in terms of
  139. `${prefix}'. Any directories that were specified during `configure',
  140. but not in terms of `${prefix}', must each be overridden at install
  141. time for the entire installation to be relocated. The approach of
  142. makefile variable overrides for each directory variable is required by
  143. the GNU Coding Standards, and ideally causes no recompilation.
  144. However, some platforms have known limitations with the semantics of
  145. shared libraries that end up requiring recompilation when using this
  146. method, particularly noticeable in packages that use GNU Libtool.
  147. The second method involves providing the `DESTDIR' variable. For
  148. example, `make install DESTDIR=/alternate/directory' will prepend
  149. `/alternate/directory' before all installation names. The approach of
  150. `DESTDIR' overrides is not required by the GNU Coding Standards, and
  151. does not work on platforms that have drive letters. On the other hand,
  152. it does better at avoiding recompilation issues, and works well even
  153. when some directory options were not specified in terms of `${prefix}'
  154. at `configure' time.
  155. Optional Features
  156. =================
  157. If the package supports it, you can cause programs to be installed
  158. with an extra prefix or suffix on their names by giving `configure' the
  159. option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  160. Some packages pay attention to `--enable-FEATURE' options to
  161. `configure', where FEATURE indicates an optional part of the package.
  162. They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  163. is something like `gnu-as' or `x' (for the X Window System). The
  164. `README' should mention any `--enable-' and `--with-' options that the
  165. package recognizes.
  166. For packages that use the X Window System, `configure' can usually
  167. find the X include and library files automatically, but if it doesn't,
  168. you can use the `configure' options `--x-includes=DIR' and
  169. `--x-libraries=DIR' to specify their locations.
  170. Some packages offer the ability to configure how verbose the
  171. execution of `make' will be. For these packages, running `./configure
  172. --enable-silent-rules' sets the default to minimal output, which can be
  173. overridden with `make V=1'; while running `./configure
  174. --disable-silent-rules' sets the default to verbose, which can be
  175. overridden with `make V=0'.
  176. Particular systems
  177. ==================
  178. On HP-UX, the default C compiler is not ANSI C compatible. If GNU
  179. CC is not installed, it is recommended to use the following options in
  180. order to use an ANSI C compiler:
  181. ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
  182. and if that doesn't work, install pre-built binaries of GCC for HP-UX.
  183. HP-UX `make' updates targets which have the same time stamps as
  184. their prerequisites, which makes it generally unusable when shipped
  185. generated files such as `configure' are involved. Use GNU `make'
  186. instead.
  187. On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
  188. parse its `<wchar.h>' header file. The option `-nodtk' can be used as
  189. a workaround. If GNU CC is not installed, it is therefore recommended
  190. to try
  191. ./configure CC="cc"
  192. and if that doesn't work, try
  193. ./configure CC="cc -nodtk"
  194. On Solaris, don't put `/usr/ucb' early in your `PATH'. This
  195. directory contains several dysfunctional programs; working variants of
  196. these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
  197. in your `PATH', put it _after_ `/usr/bin'.
  198. On Haiku, software installed for all users goes in `/boot/common',
  199. not `/usr/local'. It is recommended to use the following options:
  200. ./configure --prefix=/boot/common
  201. Specifying the System Type
  202. ==========================
  203. There may be some features `configure' cannot figure out
  204. automatically, but needs to determine by the type of machine the package
  205. will run on. Usually, assuming the package is built to be run on the
  206. _same_ architectures, `configure' can figure that out, but if it prints
  207. a message saying it cannot guess the machine type, give it the
  208. `--build=TYPE' option. TYPE can either be a short name for the system
  209. type, such as `sun4', or a canonical name which has the form:
  210. CPU-COMPANY-SYSTEM
  211. where SYSTEM can have one of these forms:
  212. OS
  213. KERNEL-OS
  214. See the file `config.sub' for the possible values of each field. If
  215. `config.sub' isn't included in this package, then this package doesn't
  216. need to know the machine type.
  217. If you are _building_ compiler tools for cross-compiling, you should
  218. use the option `--target=TYPE' to select the type of system they will
  219. produce code for.
  220. If you want to _use_ a cross compiler, that generates code for a
  221. platform different from the build platform, you should specify the
  222. "host" platform (i.e., that on which the generated programs will
  223. eventually be run) with `--host=TYPE'.
  224. Sharing Defaults
  225. ================
  226. If you want to set default values for `configure' scripts to share,
  227. you can create a site shell script called `config.site' that gives
  228. default values for variables like `CC', `cache_file', and `prefix'.
  229. `configure' looks for `PREFIX/share/config.site' if it exists, then
  230. `PREFIX/etc/config.site' if it exists. Or, you can set the
  231. `CONFIG_SITE' environment variable to the location of the site script.
  232. A warning: not all `configure' scripts look for a site script.
  233. Defining Variables
  234. ==================
  235. Variables not defined in a site shell script can be set in the
  236. environment passed to `configure'. However, some packages may run
  237. configure again during the build, and the customized values of these
  238. variables may be lost. In order to avoid this problem, you should set
  239. them in the `configure' command line, using `VAR=value'. For example:
  240. ./configure CC=/usr/local2/bin/gcc
  241. causes the specified `gcc' to be used as the C compiler (unless it is
  242. overridden in the site shell script).
  243. Unfortunately, this technique does not work for `CONFIG_SHELL' due to
  244. an Autoconf limitation. Until the limitation is lifted, you can use
  245. this workaround:
  246. CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
  247. `configure' Invocation
  248. ======================
  249. `configure' recognizes the following options to control how it
  250. operates.
  251. `--help'
  252. `-h'
  253. Print a summary of all of the options to `configure', and exit.
  254. `--help=short'
  255. `--help=recursive'
  256. Print a summary of the options unique to this package's
  257. `configure', and exit. The `short' variant lists options used
  258. only in the top level, while the `recursive' variant lists options
  259. also present in any nested packages.
  260. `--version'
  261. `-V'
  262. Print the version of Autoconf used to generate the `configure'
  263. script, and exit.
  264. `--cache-file=FILE'
  265. Enable the cache: use and save the results of the tests in FILE,
  266. traditionally `config.cache'. FILE defaults to `/dev/null' to
  267. disable caching.
  268. `--config-cache'
  269. `-C'
  270. Alias for `--cache-file=config.cache'.
  271. `--quiet'
  272. `--silent'
  273. `-q'
  274. Do not print messages saying which checks are being made. To
  275. suppress all normal output, redirect it to `/dev/null' (any error
  276. messages will still be shown).
  277. `--srcdir=DIR'
  278. Look for the package's source code in directory DIR. Usually
  279. `configure' can determine that directory automatically.
  280. `--prefix=DIR'
  281. Use DIR as the installation prefix. *note Installation Names::
  282. for more details, including other options available for fine-tuning
  283. the installation locations.
  284. `--no-create'
  285. `-n'
  286. Run the configure checks, but stop before creating any output
  287. files.
  288. `configure' also accepts some other, not widely useful, options. Run
  289. `configure --help' for more details.