There are a number of options that you can use to control exactly how
Allegro will be compiled. On Unix platforms you do this by passing arguments
to the configure script (run "configure --help" for a list), but on other
platforms you can set the environment variables:
-
DEBUGMODE=1
Selects a debug build, rather than the normal optimised version.
-
PROFILEMODE=1
Selects a profiling build, rather than the normal optimised version.
-
WARNMODE=1
Selects strict compiler warnings. If you are planning to work on Allegro
yourself, rather than just using it in your programs, you should be sure
to have this mode enabled.
-
STATICLINK=1 (MSVC only)
Link as a static library, rather than the default DLL.
-
PGCC=1 (djgpp, RSXNT, and Mingw32 only)
Uses optimisation options suitable for the Pentium optimising compiler,
rather than the stock djgpp version of gcc.
-
CROSSCOMPILE=1 (djgpp only)
Allows you to build the djgpp library under Linux, using djgpp as a
cross-compiler.
-
ALLEGRO_USE_C=1 (djgpp only)
Allows you to build the djgpp library using C drawing code instead of the
usual asm routines. This is only really useful for testing, since the asm
version is faster.
If you only want to recompile a specific test program or utility, you can
specify it as an argument to make, eg. "make demo" or "make grabber". The
makefiles also provide some special pseudo-targets:
-
'default'
The normal build process. Compiles the current library version (one of
optimised, debugging, or profiling, selected by the above environment
variables), builds the test and example programs, and converts the
documentation files.
-
'all'
Compiles all three library versions (optimised, debugging, and
profiling), builds the test and example programs, and converts the
documentation files.
-
'lib'
Compiles the current library version (one of optimised, debugging, or
profiling, selected by the above environment variables).
-
'install'
Copies the current library version (one of optimised, debugging, or
profiling, selected by the above environment variables), into your
compiler lib directory, recompiling it as required, and installs the
Allegro headers.
-
'installall'
Copies all three library versions (optimised, debugging, and profiling),
into your compiler lib directory, recompiling them as required, and
installs the Allegro headers.
-
'uninstall'
Removes the Allegro library and headers from your compiler directories.
This requires a Unix-style 'rm' utility to be available, eg. from the GNU
fileutils package.
-
'docs'
Converts the documentation files from the ._tx sources.
-
'clean'
Removes generated object and library files, either to recover disk space
or to force a complete rebuild the next time you run make. This target is
designed so that if you run a "make install" followed by "make clean",
you will still have a functional version of Allegro. This requires a
Unix-style 'rm' utility to be available, eg. from the GNU fileutils
package.
-
'distclean'
Like "make clean", but more so. This removes all the executable files and
HTML format documentation, leaving you with only the same files that are
included when you unzip a new Allegro distribution.
-
'veryclean'
Use with extreme caution! This target deletes absolutely all generated
files, including some that may be non-trivial to recreate. After you run
"make veryclean", a simple rebuild will not work: at the very least you
will have to run "make depend", and perhaps also fixdll.bat if you are
using the Windows library. These targets make use of non-standard tools
like SED, so unless you know what you are doing and have all this stuff
installed, you should not use them.
-
'depend'
Regenerates the dependency files (obj/*/makefile.dep). You need to run
this after "make veryclean", or whenever you add new headers to the
Allegro sources.
-
'compress' (djgpp only)
Uses the DJP or UPX executable compressors (whichever you have installed)
to compress the example executables and utility programs, which can
recover a significant amount of disk space.
Retour au Sommaire