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