1Installation Instructions for fllog 2************************************ 3 4To compile fllog you will need: 5 6 * A recent C++ compiler. The GNU C++ compilers in the 4.x series are 7 known to work. 8 9 * Version 1.1.x of the Fast Light Tool Kit (FLTK), with its 10 development library and headers. Versions 1.1.7 to 1.1.9 are known 11 to work. FLTK's multi-threading support is recommended but not 12 required. 13 14Once you have installed the required packages, the following commands 15should be sufficient to compile fllog and install it under /usr/local: 16 17 ./configure 18 make 19 make install (you may need superuser privileges for installation) 20 21The `install' target installs the executable, an icon, and a .desktop 22file. After installation, an fllog launcher should appear somewhere in 23your applications menu. 24 25Create the desktop launcher. fllog is designed as a desktop application 26that accepts target files to be wrapped or unwrapped by dropping the 27file onto the desktop launcher. 28 29Windows installation notes 30************************** 31 32fllog supports win32 systems as a cross compiled application using the 33MinGW win32 environment. 34 35To build an internationalized version of fllog, install these 36additional packages: 37 38 gettext gettext-devel libiconv libiconv2 39 40 ========== Generic installation instructions follow ========== 41 42Installation Instructions 43************************* 44 45Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, 462006 Free Software Foundation, Inc. 47 48This file is free documentation; the Free Software Foundation gives 49unlimited permission to copy, distribute and modify it. 50 51Basic Installation 52================== 53 54Briefly, the shell commands `./configure; make; make install' should 55configure, build, and install this package. The following 56more-detailed instructions are generic; see the `README' file for 57instructions specific to this package. 58 59 The `configure' shell script attempts to guess correct values for 60various system-dependent variables used during compilation. It uses 61those values to create a `Makefile' in each directory of the package. 62It may also create one or more `.h' files containing system-dependent 63definitions. Finally, it creates a shell script `config.status' that 64you can run in the future to recreate the current configuration, and a 65file `config.log' containing compiler output (useful mainly for 66debugging `configure'). 67 68 It can also use an optional file (typically called `config.cache' 69and enabled with `--cache-file=config.cache' or simply `-C') that saves 70the results of its tests to speed up reconfiguring. Caching is 71disabled by default to prevent problems with accidental use of stale 72cache files. 73 74 If you need to do unusual things to compile the package, please try 75to figure out how `configure' could check whether to do them, and mail 76diffs or instructions to the address given in the `README' so they can 77be considered for the next release. If you are using the cache, and at 78some point `config.cache' contains results you don't want to keep, you 79may remove or edit it. 80 81 The file `configure.ac' (or `configure.in') is used to create 82`configure' by a program called `autoconf'. You need `configure.ac' if 83you want to change it or regenerate `configure' using a newer version 84of `autoconf'. 85 86The simplest way to compile this package is: 87 88 1. `cd' to the directory containing the package's source code and type 89 `./configure' to configure the package for your system. 90 91 Running `configure' might take a while. While running, it prints 92 some messages telling which features it is checking for. 93 94 2. Type `make' to compile the package. 95 96 3. Optionally, type `make check' to run any self-tests that come with 97 the package. 98 99 4. Type `make install' to install the programs and any data files and 100 documentation. 101 102 5. You can remove the program binaries and object files from the 103 source code directory by typing `make clean'. To also remove the 104 files that `configure' created (so you can compile the package for 105 a different kind of computer), type `make distclean'. There is 106 also a `make maintainer-clean' target, but that is intended mainly 107 for the package's developers. If you use it, you may have to get 108 all sorts of other programs in order to regenerate files that came 109 with the distribution. 110 111Compilers and Options 112===================== 113 114Some systems require unusual options for compilation or linking that the 115`configure' script does not know about. Run `./configure --help' for 116details on some of the pertinent environment variables. 117 118 You can give `configure' initial values for configuration parameters 119by setting variables in the command line or in the environment. Here 120is an example: 121 122 ./configure CC=c99 CFLAGS=-g LIBS=-lposix 123 124 *Note Defining Variables::, for more details. 125 126Compiling For Multiple Architectures 127==================================== 128 129You can compile the package for more than one kind of computer at the 130same time, by placing the object files for each architecture in their 131own directory. To do this, you can use GNU `make'. `cd' to the 132directory where you want the object files and executables to go and run 133the `configure' script. `configure' automatically checks for the 134source code in the directory that `configure' is in and in `..'. 135 136 With a non-GNU `make', it is safer to compile the package for one 137architecture at a time in the source code directory. After you have 138installed the package for one architecture, use `make distclean' before 139reconfiguring for another architecture. 140 141Installation Names 142================== 143 144By default, `make install' installs the package's commands under 145`/usr/local/bin', include files under `/usr/local/include', etc. You 146can specify an installation prefix other than `/usr/local' by giving 147`configure' the option `--prefix=PREFIX'. 148 149 You can specify separate installation prefixes for 150architecture-specific files and architecture-independent files. If you 151pass the option `--exec-prefix=PREFIX' to `configure', the package uses 152PREFIX as the prefix for installing programs and libraries. 153Documentation and other data files still use the regular prefix. 154 155 In addition, if you use an unusual directory layout you can give 156options like `--bindir=DIR' to specify different values for particular 157kinds of files. Run `configure --help' for a list of the directories 158you can set and what kinds of files go in them. 159 160 If the package supports it, you can cause programs to be installed 161with an extra prefix or suffix on their names by giving `configure' the 162option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 163 164Optional Features 165================= 166 167Some packages pay attention to `--enable-FEATURE' options to 168`configure', where FEATURE indicates an optional part of the package. 169They may also pay attention to `--with-PACKAGE' options, where PACKAGE 170is something like `gnu-as' or `x' (for the X Window System). The 171`README' should mention any `--enable-' and `--with-' options that the 172package recognizes. 173 174 For packages that use the X Window System, `configure' can usually 175find the X include and library files automatically, but if it doesn't, 176you can use the `configure' options `--x-includes=DIR' and 177`--x-libraries=DIR' to specify their locations. 178 179Specifying the System Type 180========================== 181 182There may be some features `configure' cannot figure out automatically, 183but needs to determine by the type of machine the package will run on. 184Usually, assuming the package is built to be run on the _same_ 185architectures, `configure' can figure that out, but if it prints a 186message saying it cannot guess the machine type, give it the 187`--build=TYPE' option. TYPE can either be a short name for the system 188type, such as `sun4', or a canonical name which has the form: 189 190 CPU-COMPANY-SYSTEM 191 192where SYSTEM can have one of these forms: 193 194 OS KERNEL-OS 195 196 See the file `config.sub' for the possible values of each field. If 197`config.sub' isn't included in this package, then this package doesn't 198need to know the machine type. 199 200 If you are _building_ compiler tools for cross-compiling, you should 201use the option `--target=TYPE' to select the type of system they will 202produce code for. 203 204 If you want to _use_ a cross compiler, that generates code for a 205platform different from the build platform, you should specify the 206"host" platform (i.e., that on which the generated programs will 207eventually be run) with `--host=TYPE'. 208 209Sharing Defaults 210================ 211 212If you want to set default values for `configure' scripts to share, you 213can create a site shell script called `config.site' that gives default 214values for variables like `CC', `cache_file', and `prefix'. 215`configure' looks for `PREFIX/share/config.site' if it exists, then 216`PREFIX/etc/config.site' if it exists. Or, you can set the 217`CONFIG_SITE' environment variable to the location of the site script. 218A warning: not all `configure' scripts look for a site script. 219 220Defining Variables 221================== 222 223Variables not defined in a site shell script can be set in the 224environment passed to `configure'. However, some packages may run 225configure again during the build, and the customized values of these 226variables may be lost. In order to avoid this problem, you should set 227them in the `configure' command line, using `VAR=value'. For example: 228 229 ./configure CC=/usr/local2/bin/gcc 230 231causes the specified `gcc' to be used as the C compiler (unless it is 232overridden in the site shell script). 233 234Unfortunately, this technique does not work for `CONFIG_SHELL' due to 235an Autoconf bug. Until the bug is fixed you can use this workaround: 236 237 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash 238 239`configure' Invocation 240====================== 241 242`configure' recognizes the following options to control how it operates. 243 244`--help' 245`-h' 246 Print a summary of the options to `configure', and exit. 247 248`--version' 249`-V' 250 Print the version of Autoconf used to generate the `configure' 251 script, and exit. 252 253`--cache-file=FILE' 254 Enable the cache: use and save the results of the tests in FILE, 255 traditionally `config.cache'. FILE defaults to `/dev/null' to 256 disable caching. 257 258`--config-cache' 259`-C' 260 Alias for `--cache-file=config.cache'. 261 262`--quiet' 263`--silent' 264`-q' 265 Do not print messages saying which checks are being made. To 266 suppress all normal output, redirect it to `/dev/null' (any error 267 messages will still be shown). 268 269`--srcdir=DIR' 270 Look for the package's source code in directory DIR. Usually 271 `configure' can determine that directory automatically. 272 273`configure' also accepts some other, not widely useful, options. Run 274`configure --help' for more details. 275 276