PathEngine home previous: Building with GCCnext: Customising Memory Management
Contents, Programmers Guide, Building the Source Code, Preprocessor Defines

Preprocessor Defines

For PathEngine and the testbed:

MEMORY_TRACKING - defining this enables memory tracking, (see Memory Tracking).
MEMORY_LOG - defining this enables memory logging
MEMORY_OVERWRITE_CHECKING - defining this enables instrumentation for detecting writes outside allocated memory
MEMORY_OVERWRITE_CHECKING2 - defining this enables instrumentation for detecting writes after memory has been deallocated
(Note that only one set of memory instrumentation may be turned on in a given build.)

These memory instrumentation options are only supported when linking the run-time library as a dll, on platforms that support dll linkage.

For all components:

PATHENGINE_FULL_RELEASE - removes validation code at the interface and 'release build assertions'.
PATHENGINE_SINGLE_THREADED - can be used to remove some logic related to thread synchronisation, when only single threaded application is required. (For maximum benefit, the supplied project files or platform configuration should also be modified, e.g. to switch to single threaded run-time libraries.)

All other defines should be left as setup in the project files.


Documentation for PathEngine release 5.16 - Copyright © 2002-2008 PathEnginenext: Customising Memory Management