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