prefix(1) [debian man page]

PREFIX(1)						      General Commands Manual							 PREFIX(1)

NAME

       prefix  - Script that allows you to reconfigure environment variables for multiple installations of a set of software installed on the same
       machine

SYNOPSIS

       prefix

DESCRIPTION

       It is assumed that the software for each installation is all under a single directory whose name is assigned  to  an  environment  variable
       called PREFIX.

       This  arrangement  of  enabling	multiple installations of software on a single machine is useful at many times. On a single server, it can
       provide for development, test, and production installations of software. Alternatively, on development  servers,  it  allows  for  multiple
       development  "sandboxes",  one  for each developer. On production servers, it allows for multiple versions of the production software to be
       installed. One might be the currently running software, one the previous software kept online as a fall-back, and  one  a  new  release	of
       software wich is scheduled to be brought online soon.

       There are three usages of the prefix script:

	      (1) The interactive usage should be placed as the last line
		  of a user's ".profile".  The user must be running the
		  Korn shell (ksh) or the Bourne Again shell (bash).
		  The user is prompted to enter one of the known PREFIX locations,
		  specified in the $HOME/.prefixes file or the /etc/prefixes file.
		  During configuration, the $PREFIX/.prefixrc file is sourced
		  in order to accomplish environment-specific configurations.

	      (2) The non-interactive user configuration does not consult
		  $HOME/.prefixes or /etc/prefixes or prompt the user, but merely
		  configures the environment in accordance with the cmd line argument.

	      (3) The batch command usage is mainly for running commands from
		  cron or running commands in another environment without changing
		  to that environment.

       Usage (1): . prefix		       (sets up environment)
	     (2): . prefix <prefix>	       (non-interactive setup)
	     (3): prefix <prefix> <cmd> <args> (runs cmd configured for PREFIX)

       This manual page was written for the Debian distribution because the original program does not have a manual page.

AUTHOR

       Prefix was written by Stephen Adkins <spadkins@gmail.com>, and is part of the App-Options distribution.

       This manual page was written by Jotam Jr. Trejo <jotamjr@debian.org.sv>, for the Debian systems (but may be used by others).

								   Oct 07, 2010 							 PREFIX(1)

ALLEGRO(1)							       4.0.3								ALLEGRO(1)

NAME

       allegro-config - script to get information about the installed version of Allegro

SYNOPSIS

       allegro-config [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--libs] [--cflags] [--static] [--shared] [--env] [release|debug|profile]

DESCRIPTION

       allegro-config  is a tool that is used to configure to determine the compiler and linker flags that should be used to compile and link pro-
       grams that use the Allegro library. It is intended to be used on Unix systems instead of the simple "-lalleg" call.

EXAMPLE

       gcc -o mygame mygame.o `allegro-config --libs`

       allegro-config will insert arguments needed to link into the command line.

OPTIONS

       allegro-config accepts the following options:

       --version
	       Print the currently installed version of Allegro on the standard output.

       --libs  Print the linker flags that are necessary to link an Allegro program.

       --cflags
	       Print the compiler flags that are necessary to compile an Allegro program.

       --prefix=PREFIX
	       If specified, use PREFIX instead of the installation prefix that Allegro was built with when computing the output for the  --cflags
	       and  --libs options. This option is also used for the exec prefix if --exec-prefix was not specified. This option must be specified
	       before any --libs or --cflags options.

       --exec-prefix=PREFIX
	       If specified, use PREFIX instead of the installation exec prefix that Allegro was built with when  computing  the  output  for  the
	       --cflags and --libs options.  This option must be specified before any --libs or --cflags options.

       --static
	       Like --libs, but always print the linker flags needed to get a statically linked executable.

       --shared
	       Like --libs, but always print the linker flags needed to get an executable linked against shared libs.

       --env   Print some needed environment variables in the way needed in shell scripts. Output may be loaded into your environment using

	       BASH#> eval `allegro-config --env`

       release This will use the optimized Allegro library which you should use when you are compiling for a release.

       debug   This  will  add	extra debug info into your programs, useful to find out where your program crashed or simply to debug it (names of
	       functions are seen). You may choose this option while developing a program.

       profile This may be used when you want to profile your program - i.e. measure the speeds of various function calls.

SEE ALSO

       allegro-dev-tools(1)
       The allegro info entry

COPYRIGHT

       This manual page was   written	by   Eduard   Bloch <blade@debian.org>, for the Debian GNU/Linux  system  (but may be used by others).	It
       is heavily based on a similar manpage for gtk-config, written by Owen Taylor. His notice:

       Copyright (C)  1998 Owen Taylor

       Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, pro-
       vided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice  appear  in  sup-
       porting documentation.

Version 							    8 June 2003 							ALLEGRO(1)