1 2What To Read 3================== 4 5You should read the 'Installation' section. 6Read the other sections if you want more details on configure's options. 7'File list' at the bottom provides a list of files installed by the package. 8It might be useful if the need arises to un-install the software later. 9 10Installation 11================== 12 13On most systems, tkgeomap can be built and installed with the usual 14sequence: 15 16 ./configure 17 make 18 make install 19 20configure studies the local system and determines how to build and install the 21software. It stores the resulting instructions in a file called Makefile. 22make actually builds the software. 'make install' moves the software files 23and documentation to their destination directories and creates any necessary 24links. See below for a list of files installed by 'make install'. 25 26By default, the software is installed in /usr/local. This destination can 27be over-ridden with the prefix option to configure, i.e. for the first step 28above enter './configure --prefix=install_dir'. 29 30You can correct a build failure or customize the build and install process by 31giving options to configure. Enter 'configure --help' for a complete list of 32available options. 33 34Here is a list of options specific to tkgeomap: 35 36 --with-tcl specifies the directory that contains tclConfig.sh 37 Default location is /usr/local/lib. 38 --with-tclinclude specifies the directory that contains the tcl headers 39 (e.g. tcl.h, tclDecls.h). Default location is 40 /usr/local/include, but some systems have several 41 versions of tcl installed with a header directory for 42 each. 43 --with-tclgeomap specifies the location of the tclgeomap library, 44 i.e. libtclgeomap2.11.6.so. The default is 45 /usr/local/lib. 46 --with-tclgeomap-include 47 specifies the location of the tclgeomap public headers, 48 i.e. tclgeomap.h. Default location is 49 /usr/local/include. 50 --prefix specifies where to install everything. Default 51 location is /usr/local, i.e. the libraries go to 52 /usr/local/lib and the headers go to /usr/local/include. 53 Use prefix if tcl is not in /usr/local, or if you want 54 to install tkgeomap elsewhere, e.g. $HOME/local. 55 If you install tkgeomap separately from tcl, you 56 should indicate the location of the libraries in the 57 auto_path variable. See the tcl man page for package 58 for more information. 59 60===================== 61 62The rest of this file gives extra options and details for the configure 63and build process. The file list is at the end. Most users do not need to 64read beyond this point. 65 66Compilers and Options 67===================== 68 69 Some systems require unusual options for compilation or linking that 70the `configure' script does not know about. You can give `configure' 71initial values for variables by setting them in the environment. Using 72a Bourne-compatible shell, you can do that on the command line like 73this: 74 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure 75 76Or on systems that have the `env' program, you can do it like this: 77 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure 78 79Compiling For Multiple Architectures 80==================================== 81 82 You can compile the package for more than one kind of computer at the 83same time, by placing the object files for each architecture in their 84own directory. To do this, you must use a version of `make' that 85supports the `VPATH' variable, such as GNU `make'. `cd' to the 86directory where you want the object files and executables to go and run 87the `configure' script. `configure' automatically checks for the 88source code in the directory that `configure' is in and in `..'. 89 90 If you have to use a `make' that does not supports the `VPATH' 91variable, you have to compile the package for one architecture at a time 92in the source code directory. After you have installed the package for 93one architecture, use `make distclean' before reconfiguring for another 94architecture. 95 96Installation Names 97================== 98 99 By default, `make install' will install the package's files in 100the directory tree occupied by Tcl. You can specify an 101installation prefix other than the Tcl default by giving `configure' the 102option `--prefix=PATH'. 103 104 You can specify separate installation prefixes for 105architecture-specific files and architecture-independent files. If you 106give `configure' the option `--exec-prefix=PATH', the package will use 107PATH as the prefix for installing programs and libraries. 108Documentation and other data files will still use the regular prefix. 109 110 In addition, if you use an unusual directory layout you can give 111options like `--bindir=PATH' to specify different values for particular 112kinds of files. Run `configure --help' for a list of the directories 113you can set and what kinds of files go in them. 114 115 If the package supports it, you can cause programs to be installed 116with an extra prefix or suffix on their names by giving `configure' the 117option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 118 119Optional Features 120================= 121 122 Some packages pay attention to `--enable-FEATURE' options to 123`configure', where FEATURE indicates an optional part of the package. 124They may also pay attention to `--with-PACKAGE' options, where PACKAGE 125is something like `gnu-as' or `x' (for the X Window System). The 126`README' should mention any `--enable-' and `--with-' options that the 127package recognizes. 128 129 For packages that use the X Window System, `configure' can usually 130find the X include and library files automatically, but if it doesn't, 131you can use the `configure' options `--x-includes=DIR' and 132`--x-libraries=DIR' to specify their locations. 133 134Specifying the System Type 135========================== 136 137 There may be some features `configure' can not figure out 138automatically, but needs to determine by the type of host the package 139will run on. Usually `configure' can figure that out, but if it prints 140a message saying it can not guess the host type, give it the 141`--host=TYPE' option. TYPE can either be a short name for the system 142type, such as `sun4', or a canonical name with three fields: 143 CPU-COMPANY-SYSTEM 144 145See the file `config.sub' for the possible values of each field. If 146`config.sub' isn't included in this package, then this package doesn't 147need to know the host type. 148 149 If you are building compiler tools for cross-compiling, you can also 150use the `--target=TYPE' option to select the type of system they will 151produce code for and the `--build=TYPE' option to select the type of 152system on which you are compiling the package. 153 154Sharing Defaults 155================ 156 157 If you want to set default values for `configure' scripts to share, 158you can create a site shell script called `config.site' that gives 159default values for variables like `CC', `cache_file', and `prefix'. 160`configure' looks for `PREFIX/share/config.site' if it exists, then 161`PREFIX/etc/config.site' if it exists. Or, you can set the 162`CONFIG_SITE' environment variable to the location of the site script. 163A warning: not all `configure' scripts look for a site script. 164 165Operation Controls 166================== 167 168 `configure' recognizes the following options to control how it 169operates. 170 171`--cache-file=FILE' 172 Use and save the results of the tests in FILE instead of 173 `./config.cache'. Set FILE to `/dev/null' to disable caching, for 174 debugging `configure'. 175 176`--help' 177 Print a summary of the options to `configure', and exit. 178 179`--quiet' 180`--silent' 181`-q' 182 Do not print messages saying which checks are being made. To 183 suppress all normal output, redirect it to `/dev/null' (any error 184 messages will still be shown). 185 186`--srcdir=DIR' 187 Look for the package's source code in directory DIR. Usually 188 `configure' can determine that directory automatically. 189 190`--version' 191 Print the version of Autoconf used to generate the `configure' 192 script, and exit. 193 194`configure' also accepts some other, not widely useful, options. 195 196File list 197================== 198 199'make install' creates the following files and links. 200 201Library files and indeces (this is the actual software): 202/usr/local/lib/libtkgeomap2.11.6.so 203/usr/local/lib/tkgeomap2.11.6/pkgIndex.tcl 204/usr/local/lib/tkgeomap2.11.6/tkgeomap_procs.tcl 205/usr/local/lib/tkgeomap2.11.6/wdgeomap.tcl 206 207Headers (needed to compile other extensions that use tclgeomap): 208/usr/local/include/tkgeomap2.11.6/tkgeomap.h 209 210Man pages (note, most of these are just links): 211/usr/local/man/mann/igeomap.n 212/usr/local/man/mann/tkgeomap.n 213/usr/local/man/mann/tkgeomap_procs.n 214/usr/local/man/mann/xytolatlon.n 215/usr/local/man/mann/latlontoxy.n 216