Baghira widget style for TDE
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 6.8KB

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