Warning, /utilities/krename/INSTALL is written in an unsupported language. File is not indexed.
0001 0002 0003 To install KRename run the following commands: 0004 0005 > mkdir build 0006 > cd build 0007 > cmake 0008 > make 0009 > sudo make install 0010 0011 All common CMake options should also work for KRename. 0012 After KRename was installed, you can run a selftest using krename --test 0013 0014 The instructions below are outdated. KRename uses CMake now! 0015 0016 Basic Installation 0017 ================== 0018 0019 These are generic installation instructions. 0020 0021 The `configure' shell script attempts to guess correct values for 0022 various system-dependent variables used during compilation. It uses 0023 those values to create a `Makefile' in each directory of the package. 0024 It may also create one or more `.h' files containing system-dependent 0025 definitions. Finally, it creates a shell script `config.status' that 0026 you can run in the future to recreate the current configuration, a file 0027 `config.cache' that saves the results of its tests to speed up 0028 reconfiguring, and a file `config.log' containing compiler output 0029 (useful mainly for debugging `configure'). 0030 0031 If you need to do unusual things to compile the package, please try 0032 to figure out how `configure' could check whether to do them, and mail 0033 diffs or instructions to the address given in the `README' so they can 0034 be considered for the next release. If at some point `config.cache' 0035 contains results you don't want to keep, you may remove or edit it. 0036 0037 The file `configure.in' is used to create `configure' by a program 0038 called `autoconf'. You only need `configure.in' if you want to change 0039 it or regenerate `configure' using a newer version of `autoconf'. 0040 0041 The simplest way to compile this package is: 0042 0043 1. `cd' to the directory containing the package's source code and type 0044 `./configure' to configure the package for your system. If you're 0045 using `csh' on an old version of System V, you might need to type 0046 `sh ./configure' instead to prevent `csh' from trying to execute 0047 `configure' itself. 0048 0049 Running `configure' takes a while. While running, it prints some 0050 messages telling which features it is checking for. 0051 0052 2. Type `make' to compile the package. 0053 0054 3. Type `make install' to install the programs and any data files and 0055 documentation. 0056 0057 4. You can remove the program binaries and object files from the 0058 source code directory by typing `make clean'. 0059 0060 Compilers and Options 0061 ===================== 0062 0063 Some systems require unusual options for compilation or linking that 0064 the `configure' script does not know about. You can give `configure' 0065 initial values for variables by setting them in the environment. Using 0066 a Bourne-compatible shell, you can do that on the command line like 0067 this: 0068 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure 0069 0070 Or on systems that have the `env' program, you can do it like this: 0071 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure 0072 0073 Compiling For Multiple Architectures 0074 ==================================== 0075 0076 You can compile the package for more than one kind of computer at the 0077 same time, by placing the object files for each architecture in their 0078 own directory. To do this, you must use a version of `make' that 0079 supports the `VPATH' variable, such as GNU `make'. `cd' to the 0080 directory where you want the object files and executables to go and run 0081 the `configure' script. `configure' automatically checks for the 0082 source code in the directory that `configure' is in and in `..'. 0083 0084 If you have to use a `make' that does not supports the `VPATH' 0085 variable, you have to compile the package for one architecture at a time 0086 in the source code directory. After you have installed the package for 0087 one architecture, use `make distclean' before reconfiguring for another 0088 architecture. 0089 0090 Installation Names 0091 ================== 0092 0093 By default, `make install' will install the package's files in 0094 `/usr/local/bin', `/usr/local/man', etc. You can specify an 0095 installation prefix other than `/usr/local' by giving `configure' the 0096 option `--prefix=PATH'. 0097 0098 You can specify separate installation prefixes for 0099 architecture-specific files and architecture-independent files. If you 0100 give `configure' the option `--exec-prefix=PATH', the package will use 0101 PATH as the prefix for installing programs and libraries. 0102 Documentation and other data files will still use the regular prefix. 0103 0104 If the package supports it, you can cause programs to be installed 0105 with an extra prefix or suffix on their names by giving `configure' the 0106 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 0107 0108 Optional Features 0109 ================= 0110 0111 Some packages pay attention to `--enable-FEATURE' options to 0112 `configure', where FEATURE indicates an optional part of the package. 0113 They may also pay attention to `--with-PACKAGE' options, where PACKAGE 0114 is something like `gnu-as' or `x' (for the X Window System). The 0115 `README' should mention any `--enable-' and `--with-' options that the 0116 package recognizes. 0117 0118 For packages that use the X Window System, `configure' can usually 0119 find the X include and library files automatically, but if it doesn't, 0120 you can use the `configure' options `--x-includes=DIR' and 0121 `--x-libraries=DIR' to specify their locations. 0122 0123 Specifying the System Type 0124 ========================== 0125 0126 There may be some features `configure' can not figure out 0127 automatically, but needs to determine by the type of host the package 0128 will run on. Usually `configure' can figure that out, but if it prints 0129 a message saying it can not guess the host type, give it the 0130 `--host=TYPE' option. TYPE can either be a short name for the system 0131 type, such as `sun4', or a canonical name with three fields: 0132 CPU-COMPANY-SYSTEM 0133 0134 See the file `config.sub' for the possible values of each field. If 0135 `config.sub' isn't included in this package, then this package doesn't 0136 need to know the host type. 0137 0138 If you are building compiler tools for cross-compiling, you can also 0139 use the `--target=TYPE' option to select the type of system they will 0140 produce code for and the `--build=TYPE' option to select the type of 0141 system on which you are compiling the package. 0142 0143 Sharing Defaults 0144 ================ 0145 0146 If you want to set default values for `configure' scripts to share, 0147 you can create a site shell script called `config.site' that gives 0148 default values for variables like `CC', `cache_file', and `prefix'. 0149 `configure' looks for `PREFIX/share/config.site' if it exists, then 0150 `PREFIX/etc/config.site' if it exists. Or, you can set the 0151 `CONFIG_SITE' environment variable to the location of the site script. 0152 A warning: not all `configure' scripts look for a site script. 0153 0154 Operation Controls 0155 ================== 0156 0157 `configure' recognizes the following options to control how it 0158 operates. 0159 0160 `--cache-file=FILE' 0161 Use and save the results of the tests in FILE instead of 0162 `./config.cache'. Set FILE to `/dev/null' to disable caching, for 0163 debugging `configure'. 0164 0165 `--help' 0166 Print a summary of the options to `configure', and exit. 0167 0168 `--quiet' 0169 `--silent' 0170 `-q' 0171 Do not print messages saying which checks are being made. 0172 0173 `--srcdir=DIR' 0174 Look for the package's source code in directory DIR. Usually 0175 `configure' can determine that directory automatically. 0176 0177 `--version' 0178 Print the version of Autoconf used to generate the `configure' 0179 script, and exit. 0180 0181 `configure' also accepts some other, not widely useful, options. 0182