Configurations

The following configurations are provided:
(except on the Xbox 360, where the standard set of Xbox 360 configurations is used)

'Release'

In this configuration all components are built with optimisation and compiled against a release version of the c runtime library.
Most assertions are turned off under this configuration, but some 'release build assertions' are left on.
Interface checking is enabled under this configuration.
Memory tracking is turned on under this configuration for the PathEngine dll but not for the testbed.

Suffix: No suffix is added for this configuration, e.g. 'bin/PathEngine.dll'.

'Debug'

In this configuration all components are built without optimisation and compiled against a debug version of the c runtime library.
All assertions are turned on under this configuration.
Interface checking is enabled under this configuration.
Memory tracking is turned on under this configuration.

Suffix: '_D', e.g. 'bin/PathEngine_D.dll'.

The full source package is required to build this configuration.

Building for maximum speed

A number of changes can be made to the standard release configuration, in order to build for maximum speed.

The MEMORY_TRACKING preprocessor define is set for this standard release build.
Removing this preprocessor define will remove some overhead per memory allocation.
(In general, though, PathEngine already attempts to avoid dynamic allocation as far as possible in performance critical code.)

And, to build for maximum speed, this release build can be modified to add a PATHENGINE_FULL_RELEASE preprocessor define.
This turns off interface checking, and any release build assertions.

If you don't need support for multithreading then you can also get some extra speed by building against single threaded system libraries instead of the multithreaded versions.