Show options - Liquid War 6
Description: Liquid War 6

Next: Path options, Previous: Doc options, Up: Reference

### 4.3 Show options

#### 4.3.1 show-build-abs-srcdir

— Command-line option: `--show-build-abs-srcdir`

> Shows the top source directory on the machine where the binary was compiled, as an absolute path.

#### 4.3.2 show-build-bin-id

— Command-line option: `--show-build-bin-id`

> Shows the internal 'bin-id' value. This value does not mean anything in itself but it's supposed to change each time you compile the game.

#### 4.3.3 show-build-bugs-url

— Command-line option: `--show-build-bugs-url`

> Shows the URL to make bug reports.

#### 4.3.4 show-build-cflags

— Command-line option: `--show-build-cflags`

> Shows what value you should put in 'CFLAGS' (environment variable) if you want to compile programs that use Liquid War 6 as a library, and include 'liquidwar6.h'.

#### 4.3.5 show-build-codename

— Command-line option: `--show-build-codename`

> Shows the codename associated with this version, generally the name of someone famous who is war-related (a general, an emperor...).

#### 4.3.6 show-build-configure-args

— Command-line option: `--show-build-configure-args`

> Shows the arguments that have been passed to the GNU Autoconf './configure' script when building the program. This can be very usefull if you want to know how the program has been built.

#### 4.3.7 show-build-copyright

— Command-line option: `--show-build-copyright`

> Shows a very short copyright notice.

#### 4.3.8 show-build-datadir

— Command-line option: `--show-build-datadir`

> Shows the 'datadir' value as passed to the GNU Autoconf './configure' script when compiling the program. Default is '/usr/local/share'. This is the generic, non Liquid War 6 specific data directory. Liquid War 6 related data is stored elsewhere (usually in a sub-directory) see the 'data-dir' switch for more information. 'datadir' is not 'data-dir'. That's the point.

#### 4.3.9 show-build-date

— Command-line option: `--show-build-date`

> Shows the date when the binary was compiled.

#### 4.3.10 show-build-docdir

— Command-line option: `--show-build-docdir`

> Shows the 'docdir' value as passed to the GNU Autoconf './configure' script when compiling the program. Default is '/usr/local/share/doc/liquidwar6'.

#### 4.3.11 show-build-enable-allinone

— Command-line option: `--show-build-enable-allinone`

> Shows wether the 'allinone' option has been chosen when building the game. This depends on parameters passed to './configure'.

#### 4.3.12 show-build-enable-console

— Command-line option: `--show-build-enable-console`

> Shows wether the console has been enabled when building the game. This depends on parameters passed to './configure' and also on the presence of ncurses and readline.

#### 4.3.13 show-build-enable-fullstatic

— Command-line option: `--show-build-enable-fullstatic`

> Shows wether the 'fullstatic' option has been chosen when building the game. This depends on parameters passed to './configure'.

#### 4.3.14 show-build-enable-gcov

— Command-line option: `--show-build-enable-gcov`

> Shows wether the game was build with suitable informations for gcov. This depends on parameters passed to './configure'.

#### 4.3.15 show-build-enable-gprof

— Command-line option: `--show-build-enable-gprof`

> Shows wether the game was build with suitable informations for gprof. This depends on parameters passed to './configure'.

#### 4.3.16 show-build-enable-gtk

— Command-line option: `--show-build-enable-gtk`

> Shows wether GTK+ support has been enabled when building the game. This depends on parameters passed to './configure' and also on the presence of GTK+ headers and libs. It uses pkg-config to detect it.

#### 4.3.17 show-build-enable-instrument

— Command-line option: `--show-build-enable-instrument`

> Shows wether the game was build with the '-finstrument-functions' GCC switch. This depends on parameters passed to './configure'.

#### 4.3.18 show-build-enable-mod-caca

— Command-line option: `--show-build-enable-mod-caca`

> Shows wether the mod-caca graphical backend has been enabled when building the game. This depends on parameters passed to './configure' and also on the presence of libcaca related libraries.

#### 4.3.19 show-build-enable-mod-csound

— Command-line option: `--show-build-enable-mod-csound`

> Shows wether the mod-csound audio backend has been enabled when building the game. This depends on parameters passed to './configure' and also on the presence of the csound library.

#### 4.3.20 show-build-enable-mod-gl1

— Command-line option: `--show-build-enable-mod-gl1`

> Shows wether the mod-gl1 graphical backend has been enabled when building the game. This depends on parameters passed to './configure' and also on the presence of SDL and OpenGL related libraries.

#### 4.3.21 show-build-enable-mod-gles2

— Command-line option: `--show-build-enable-mod-gles2`

> Shows wether the mod-gles2 graphical backend has been enabled when building the game. This depends on parameters passed to './configure' and also on the presence of SDL and OpenGL ES related libraries.

#### 4.3.22 show-build-enable-mod-http

— Command-line option: `--show-build-enable-mod-http`

> Shows wether the mod-http network backend has been enabled when building the game. This depends on parameters passed to './configure' and also on the presence of libCurl.

#### 4.3.23 show-build-enable-mod-ogg

— Command-line option: `--show-build-enable-mod-ogg`

> Shows wether the mod-ogg audio backend has been enabled when building the game. This depends on parameters passed to './configure' and also on the presence of SDL and related libraries.

#### 4.3.24 show-build-enable-mod-soft

— Command-line option: `--show-build-enable-mod-soft`

> Shows wether the mod-soft graphical backend has been enabled when building the game. This depends on parameters passed to './configure' and also on the presence of SDL related libraries.

#### 4.3.25 show-build-enable-openmp

— Command-line option: `--show-build-enable-openmp`

> Shows wether the program was built with OpenMP support. This depends on parameters passed to './configure'.

#### 4.3.26 show-build-enable-optimize

— Command-line option: `--show-build-enable-optimize`

> Shows wether the 'optimize' option has been chosen when building the game. This depends on parameters passed to './configure'.

#### 4.3.27 show-build-enable-paranoid

— Command-line option: `--show-build-enable-paranoid`

> Shows wether the game was build with paranoid memory management. This is for debugging purposes, the default already includes some controls, with turned it's really... paranoid.

#### 4.3.28 show-build-enable-profiler

— Command-line option: `--show-build-enable-profiler`

> Shows wether the game was build with Google Profiler support. This depends on parameters passed to './configure'.

#### 4.3.29 show-build-enable-valgrind

— Command-line option: `--show-build-enable-valgrind`

> Shows wether the game was build with valgrind later use in mind. This depends on parameters passed to './configure'.

#### 4.3.30 show-build-endianness

— Command-line option: `--show-build-endianness`

> Returns the endianness. 'little' corresponds to x86-like systems, 'big' to ppc-like systems.

#### 4.3.31 show-build-gcc-version

— Command-line option: `--show-build-gcc-version`

> Returns the version of the GNU C compiler which was used to compile the program.

#### 4.3.32 show-build-gnu

— Command-line option: `--show-build-gnu`

> Returns 1 (true) if host OS is a GNU system, or at least has been considered as such when compiling, 0 (false) if not.

#### 4.3.33 show-build-gp2x

— Command-line option: `--show-build-gp2x`

> Returns 1 (true) if host is a GP2X, 0 (false) if not.

#### 4.3.34 show-build-home-url

— Command-line option: `--show-build-home-url`

> Shows the URL of the program, its homepage.

#### 4.3.35 show-build-host-cpu

— Command-line option: `--show-build-host-cpu`

> Shows the host CPU, as defined by 'host_cpu' in GNU Autoconf.

#### 4.3.36 show-build-host-os

— Command-line option: `--show-build-host-os`

> Shows the host OS, as defined by 'host_os' in GNU Autoconf.

#### 4.3.37 show-build-hostname

— Command-line option: `--show-build-hostname`

> Shows the name of the host where the binary was compiled.

#### 4.3.38 show-build-includedir

— Command-line option: `--show-build-includedir`

> Shows the 'includedir' value as passed to the GNU Autoconf './configure' script when compiling the program. Default is '/usr/local/include'.

#### 4.3.39 show-build-ldflags

— Command-line option: `--show-build-ldflags`

> Shows what value you should put in 'LDFLAGS' (environment variable) if you want to link programs against libliquidwar6.

#### 4.3.40 show-build-libdir

— Command-line option: `--show-build-libdir`

> Shows the 'libdir' value as passed to the GNU Autoconf './configure' script when compiling the program. Default is '/usr/local/lib'. This is the generic, non Liquid War 6 specific library directory. Dedicated Liquid War 6 modules are stored elsewhere (usually in a sub-directory) see the 'mod-dir' switch for more information.

#### 4.3.41 show-build-license

— Command-line option: `--show-build-license`

> Shows the license of the program (GNU GPL v3 or later).

#### 4.3.42 show-build-localedir

— Command-line option: `--show-build-localedir`

> Shows the 'localedir' value as passed to the GNU Autoconf './configure' script when compiling the program. Default is '/usr/local/share/locale'.

#### 4.3.43 show-build-mac-os-x

— Command-line option: `--show-build-mac-os-x`

> Returns 1 (true) if host OS is Mac OS X, 0 (false) if not.

#### 4.3.44 show-build-md5sum

— Command-line option: `--show-build-md5sum`

> Shows the MD5 checksum, which has been calculated from the C source files. Complementary with 'show-build-stamp'.

#### 4.3.45 show-build-ms-windows

— Command-line option: `--show-build-ms-windows`

> Returns 1 (true) if host OS is Microsoft Windows, 0 (false) if not.

#### 4.3.46 show-build-package-id

— Command-line option: `--show-build-package-id`

> Shows the package tarname with its version, that is, 'liquidwar6-<version>

#### 4.3.47 show-build-package-name

— Command-line option: `--show-build-package-name`

> Shows the package name, that is, 'Liquid War 6'.

#### 4.3.48 show-build-package-string

— Command-line option: `--show-build-package-string`

> Shows the package string, that is, 'Liquid War 6 <version>

#### 4.3.49 show-build-package-tarname

— Command-line option: `--show-build-package-tarname`

> Shows the package tarname, that is, liquidwar6.

#### 4.3.50 show-build-pointer-size

— Command-line option: `--show-build-pointer-size`

> Returns the pointer size, in bytes. Should be 4 on 32-bit systems and 8 on 64-bit systems.

#### 4.3.51 show-build-prefix

— Command-line option: `--show-build-prefix`

> Shows the 'prefix' value as passed to the GNU Autoconf './configure' script when compiling the program. Default is '/usr/local'.

#### 4.3.52 show-build-stamp

— Command-line option: `--show-build-stamp`

> Shows the build stamp. A very usefull value, more precise than the version to track down binaries. It is incremented each time the core C code is updated. It won't reflect all the programs for it does not take scripts in account, but if you are running a work-in-progress version, it might be very convenient to use this to know what your are running exactly. It's also used as the revision number (the third number afer MAJOR.MINOR).

#### 4.3.53 show-build-time

— Command-line option: `--show-build-time`

> Shows the time when the binary was compiled.

#### 4.3.54 show-build-top-srcdir

— Command-line option: `--show-build-top-srcdir`

> Shows the top source directory on the machine where the binary was compiled, as a (possibly) relative path.

#### 4.3.55 show-build-unix

— Command-line option: `--show-build-unix`

> Returns 1 (true) if host OS is a UNIX system, or at least has been considered as such when compiling, 0 (false) if not.

#### 4.3.56 show-build-version

— Command-line option: `--show-build-version`

> Shows the version. Note that this is different from the standard GNU 'version' command line option which shows a complete message with a short copyright notice. This one will just return the version, without the package tarname or anything else.

#### 4.3.57 show-build-version-base

— Command-line option: `--show-build-version-base`

> Shows the version base. This is basically MAJOR.MINOR and determines the level of compatibility of the program. Two programs with the same base version should be able to communicate on the network, share data files and even binary modules if on the same platform.

#### 4.3.58 show-build-version-major

— Command-line option: `--show-build-version-major`

> Shows the major version number. This is just used to differenciate alpha/beta releases (using 0) from stable releases (using 6).

#### 4.3.59 show-build-version-minor

— Command-line option: `--show-build-version-minor`

> Shows the minor version number. This is manually increased at each significant, public release of the game.

#### 4.3.60 show-build-x86

— Command-line option: `--show-build-x86`

> Tells wether the CPU belongs to x86 family.

#### 4.3.61 show-config-file

— Command-line option: `--show-config-file`

> Shows the config file path. Default is '$HOME/.liquidwar6/config.xml'.

#### 4.3.62 show-cwd

— Command-line option: `--show-cwd`

> Shows the current working directory, the value that the pwd command would return.

#### 4.3.63 show-data-dir

— Command-line option: `--show-data-dir`

> Shows the data directory path. This is where the games searches for most of its data,the most important exception being maps, which are stored elsewhere. Default is '/usr/local/share/liquidwar6-<version>/data'.

#### 4.3.64 show-default-config-file

— Command-line option: `--show-default-config-file`

> Shows the default config file path. Default is '$HOME/.liquidwar6/config.xml'.

#### 4.3.65 show-default-data-dir

— Command-line option: `--show-default-data-dir`

> Shows the default data directory path. This is where the games searches for most of its data,the most important exception being maps, which are stored elsewhere. Default is '/usr/local/share/liquidwar6-<version>/data'.

#### 4.3.66 show-default-log-file

— Command-line option: `--show-default-log-file`

> Shows the default log file path. Default is '$HOME/.liquidwar6/log.csv'.

#### 4.3.67 show-default-map-dir

— Command-line option: `--show-default-map-dir`

> Shows the default map directory. This is where builtin maps are stored. Default is '/usr/local/share/liquidwar6-<version>/map'.

#### 4.3.68 show-default-map-path

— Command-line option: `--show-default-map-path`

> Shows the default map search path. This is where the game searches for maps. It's the combination of command-line arguments and builtin paths. Might return more directories than the one specified in a single 'map-path=dir1:dir2' argument.

#### 4.3.69 show-default-mod-dir

— Command-line option: `--show-default-mod-dir`

> Shows the default module directory path. This is where all dynamically loaded modules are stored. Default is '/usr/local/lib/liquidwar6-<version>'.

#### 4.3.70 show-default-music-dir

— Command-line option: `--show-default-music-dir`

> Shows the default music directory. This is where builtin musics are stored. Default is '/usr/local/share/liquidwar6-<version>/music'.

#### 4.3.71 show-default-music-path

— Command-line option: `--show-default-music-path`

> Shows the default music search path. This is where the game searches for musics. It's the combination of command-line arguments and builtin paths. Might return more directories than the one specified in a single 'music-path=dir1:dir2' argument.

#### 4.3.72 show-default-prefix

— Command-line option: `--show-default-prefix`

> Shows the default prefix used. This should logically be the value passed to the GNU Autoconf ./configure script when building the game. Most other path are deduced from this one. Default is '/usr/local'.

#### 4.3.73 show-default-script-file

— Command-line option: `--show-default-script-file`

> Shows the default main script file path. This file is very important, since the program is more or less a hudge scheme interpreter, and this file is the file loaded by Guile. In short, it is the main program. Default is '/usr/local/share/liquidwar6-<version>/script/liquidwar6.scm'.

#### 4.3.74 show-default-user-dir

— Command-line option: `--show-default-user-dir`

> Shows the default user directory path. This is where run-time data, config files, log files, are stored. Default is '$HOME/.liquidwar6/'.

#### 4.3.75 show-log-file

— Command-line option: `--show-log-file`

> Shows the log file path. Default is '$HOME/.liquidwar6/log.csv'.

#### 4.3.76 show-map-dir

— Command-line option: `--show-map-dir`

> Shows the map directory. This is where builtin maps are stored. Default is '/usr/local/share/liquidwar6-<version>/map'.

#### 4.3.77 show-map-path

— Command-line option: `--show-map-path`

> Shows the map search path. This is where the game searches for maps. It's the combination of command-line arguments and builtin paths. Might return more directories than the one specified in a single 'map-path=dir1:dir2' argument.

#### 4.3.78 show-mod-dir

— Command-line option: `--show-mod-dir`

> Shows the module directory path. This is where all dynamically loaded modules are stored. Default is '/usr/local/lib/liquidwar6-<version>'.

#### 4.3.79 show-music-dir

— Command-line option: `--show-music-dir`

> Shows the music directory. This is where builtin maps are stored. Default is '/usr/local/share/liquidwar6-<version>/music'.

#### 4.3.80 show-music-path

— Command-line option: `--show-music-path`

> Shows the music search path. This is where the game searches for musics. It's the combination of command-line arguments and builtin paths. Might return more directories than the one specified in a single 'music-path=dir1:dir2' argument.

#### 4.3.81 show-prefix

— Command-line option: `--show-prefix`

> Shows the prefix used. This should logically be the value passed to the GNU Autoconf ./configure script when building the game. Most other path are deduced from this one. Default is '/usr/local'.

#### 4.3.82 show-run-dir

— Command-line option: `--show-run-dir`

> Shows the run directory, usually the path where the binary is. It depends on how and where the program is launched. It is guessed from the argc/argv values at runtime.

#### 4.3.83 show-script-file

— Command-line option: `--show-script-file`

> Shows the main script file path. This file is very important, since the program is more or less a hudge scheme interpreter, and this file is the file loaded by Guile. In short, it is the main program. Default is '/usr/local/share/liquidwar6-<version>/script/liquidwar6.scm'.

#### 4.3.84 show-user-dir

— Command-line option: `--show-user-dir`

> Shows the user directory path. This is where run-time data, config files, log files, are stored. Default is '$HOME/.liquidwar6/'.