KSystemLog – system log viewer tool
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.4KB

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