Rev Author Line No. Line
3297 kaklik 1 Development
2 =================
3  
4 The project is develloped at Ubuntu. Install KDevelop3 verrsion from "deb http://ftp5.gwdg.de/pub/opensuse/repositories/home:/amilcarlucas/xUbuntu_9.04/ ./" repository.
5  
6 This program needs FFTW3 library installed to compile and run.
7  
8 Basic Installation
9 ==================
10  
11 These are generic installation instructions.
12  
13 The `configure' shell script attempts to guess correct values for
14 various system-dependent variables used during compilation. It uses
15 those values to create a `Makefile' in each directory of the package.
16 It may also create one or more `.h' files containing system-dependent
17 definitions. Finally, it creates a shell script `config.status' that
18 you can run in the future to recreate the current configuration, a file
19 `config.cache' that saves the results of its tests to speed up
20 reconfiguring, and a file `config.log' containing compiler output
21 (useful mainly for debugging `configure').
22  
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  
29 The file `configure.in' is used to create `configure' by a program
30 called `autoconf'. You only need `configure.in' if you want to change
31 it or regenerate `configure' using a newer version of `autoconf'.
32  
33 The simplest way to compile this package is:
34  
35 1. `cd' to the directory containing the package's source code and type
36 `./configure' to configure the package for your system. If you're
37 using `csh' on an old version of System V, you might need to type
38 `sh ./configure' instead to prevent `csh' from trying to execute
39 `configure' itself.
40  
41 Running `configure' takes a while. While running, it prints some
42 messages telling which features it is checking for.
43  
44 2. Type `make' to compile the package.
45  
46 3. Type `make install' to install the programs and any data files and
47 documentation.
48  
49 4. You can remove the program binaries and object files from the
50 source code directory by typing `make clean'.
51  
52 Compilers and Options
53 =====================
54  
55 Some systems require unusual options for compilation or linking that
56 the `configure' script does not know about. You can give `configure'
57 initial values for variables by setting them in the environment. Using
58 a Bourne-compatible shell, you can do that on the command line like
59 this:
60 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
61  
62 Or on systems that have the `env' program, you can do it like this:
63 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
64  
65 Compiling For Multiple Architectures
66 ====================================
67  
68 You can compile the package for more than one kind of computer at the
69 same time, by placing the object files for each architecture in their
70 own directory. To do this, you must use a version of `make' that
71 supports the `VPATH' variable, such as GNU `make'. `cd' to the
72 directory where you want the object files and executables to go and run
73 the `configure' script. `configure' automatically checks for the
74 source code in the directory that `configure' is in and in `..'.
75  
76 If you have to use a `make' that does not supports the `VPATH'
77 variable, you have to compile the package for one architecture at a time
78 in the source code directory. After you have installed the package for
79 one architecture, use `make distclean' before reconfiguring for another
80 architecture.
81  
82 Installation Names
83 ==================
84  
85 By default, `make install' will install the package's files in
86 `/usr/local/bin', `/usr/local/man', etc. You can specify an
87 installation prefix other than `/usr/local' by giving `configure' the
88 option `--prefix=PATH'.
89  
90 You can specify separate installation prefixes for
91 architecture-specific files and architecture-independent files. If you
92 give `configure' the option `--exec-prefix=PATH', the package will use
93 PATH as the prefix for installing programs and libraries.
94 Documentation and other data files will still use the regular prefix.
95  
96 If the package supports it, you can cause programs to be installed
97 with an extra prefix or suffix on their names by giving `configure' the
98 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
99  
100 Optional Features
101 =================
102  
103 Some packages pay attention to `--enable-FEATURE' options to
104 `configure', where FEATURE indicates an optional part of the package.
105 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
106 is something like `gnu-as' or `x' (for the X Window System). The
107 `README' should mention any `--enable-' and `--with-' options that the
108 package recognizes.
109  
110 For packages that use the X Window System, `configure' can usually
111 find the X include and library files automatically, but if it doesn't,
112 you can use the `configure' options `--x-includes=DIR' and
113 `--x-libraries=DIR' to specify their locations.
114  
115 Specifying the System Type
116 ==========================
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  
126 See the file `config.sub' for the possible values of each field. If
127 `config.sub' isn't included in this package, then this package doesn't
128 need to know the host type.
129  
130 If you are building compiler tools for cross-compiling, you can also
131 use the `--target=TYPE' option to select the type of system they will
132 produce code for and the `--build=TYPE' option to select the type of
133 system on which you are compiling the package.
134  
135 Sharing Defaults
136 ================
137  
138 If you want to set default values for `configure' scripts to share,
139 you can create a site shell script called `config.site' that gives
140 default values for variables like `CC', `cache_file', and `prefix'.
141 `configure' looks for `PREFIX/share/config.site' if it exists, then
142 `PREFIX/etc/config.site' if it exists. Or, you can set the
143 `CONFIG_SITE' environment variable to the location of the site script.
144 A warning: not all `configure' scripts look for a site script.
145  
146 Operation Controls
147 ==================
148  
149 `configure' recognizes the following options to control how it
150 operates.
151  
152 `--cache-file=FILE'
153 Use and save the results of the tests in FILE instead of
154 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
155 debugging `configure'.
156  
157 `--help'
158 Print a summary of the options to `configure', and exit.
159  
160 `--quiet'
161 `--silent'
162 `-q'
163 Do not print messages saying which checks are being made.
164  
165 `--srcdir=DIR'
166 Look for the package's source code in directory DIR. Usually
167 `configure' can determine that directory automatically.
168  
169 `--version'
170 Print the version of Autoconf used to generate the `configure'
171 script, and exit.
172  
173 `configure' also accepts some other, not widely useful, options.
174