root/MGET/Branches/Jason/Libraries/geos-3.3.2/INSTALL @ 891

Revision 891, 3.5 KB (checked in by jjr8, 17 months ago)

* Incremented build number.
* Added Libraries/geos-3.3.2

Line 
1Compatibility notes
2===================
3
4OS/X 10.6, compile with gcc-4.0 rather than the default gcc that
5comes with XCode.
6
7  CC=gcc-4.0 CXX=g++-4.0 ./configure
8
9Quickstart
10==========
11
12As root:
13
14   ./configure
15   make
16   make install
17
18The default install location for GEOS is /usr/local.
19
20Linux: Make sure that /usr/local/lib is added to /etc/ld.so.conf
21       Make sure that you run /sbin/ldconfig afterwards
22
23Solaris: Make sure that /usr/local/lib is added to LD_LIBRARY_PATH
24
25
26Basic Installation
27==================
28
29The simplest way to compile this package is:
30
31
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
38     Running `configure' takes awhile.  While running, it prints some
39     messages telling which features it is checking for.
40
41  2. Type `make' to compile the package.
42
43  3. Optionally, type `make check' to run any self-tests that come with
44     the package.
45
46  4. Type `make install' to install the programs and any data files and
47     documentation.
48
49  5. You can remove the program binaries and object files from the
50     source code directory by typing `make clean'.  To also remove the
51     files that `configure' created (so you can compile the package for
52     a different kind of computer), type `make distclean'.  There is
53     also a `make maintainer-clean' target, but that is intended mainly
54     for the package's developers.  If you use it, you may have to get
55     all sorts of other programs in order to regenerate files that came
56     with the distribution.
57
58
59Compilers and Options
60=====================
61
62   Some systems require unusual options for compilation or linking that
63the `configure' script does not know about.  You can give `configure'
64initial values for variables by setting them in the environment.  Using
65a Bourne-compatible shell, you can do that on the command line like
66this:
67     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
68
69Or on systems that have the `env' program, you can do it like this:
70     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
71
72
73Installation Names
74==================
75
76   By default, `make install' will install the package's files in
77`/usr/local/bin', `/usr/local/man', etc.  You can specify an
78installation prefix other than `/usr/local' by giving `configure' the
79option `--prefix=PATH'.
80
81
82Operation Controls
83==================
84
85`configure' recognizes the following options to control how it
86operates.
87
88--cache-file=FILE
89     Use and save the results of the tests in FILE instead of
90     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
91     debugging `configure'.
92
93--help
94     Print a summary of the options to `configure', and exit.
95
96--quiet
97--silent
98-q
99     Do not print messages saying which checks are being made.  To
100     suppress all normal output, redirect it to `/dev/null' (any error
101     messages will still be shown).
102
103--srcdir=DIR
104     Look for the package's source code in directory DIR.  Usually
105     `configure' can determine that directory automatically.
106
107--version
108     Print the version of Autoconf used to generate the `configure'
109     script, and exit.
110
111--prefix
112     Change the default installation location
113
114`configure' also accepts some other, not widely useful, options.
Note: See TracBrowser for help on using the browser.