Internal Organisation

Internally, the PathEngine run-time breaks down into a set of internal static libraries.
These components can be used to build the PathEngine run-time as a dll (or as a shared object on Linux), or can be statically linked directly against a client application.
Additional static libraries can then be added to build the PathEngine testbed and content tools.

Static libraries required for the PathEngine run-time

The following libraries are required for building the PathEngine run-time:

• Expat.lib
• ParseXML.lib
• Geometry.lib
• Mesh3D.lib
• Mesh2D.lib
• MeshPair.lib
• PathEngine_Core.lib
• PathEngine_Interface.lib
• Content_Processing.lib

On platforms that support dll linkage, these static libraries can be combined to build the PathEngine dll.
On Linux (and other unix-like platforms) these can instead be built into the corresponding shared object format.

On all platforms it is also possible to statically link a client application directly against these internal libraries.

Additional libraries required for the testbed

The following additional components are required to build the PathEngine testbed:

• TestBed_Application.lib
• TestBed_Interface.lib

Building the exporter plugins

The 3DS Max and Maya exporter plugins require the main run-time libraries, plus the following additional library:

• Exporter_Common.lib

3D content processing

The PathEngine 3D content processing functionality is provided through the following additional static library:

• Content_Processing_3D.lib

Content processing applications can either link statically against this library (in addition to the main run-time libraries), Or against a stand-alone 3D content processing dll built from the same set of libraries.

Project directories

Each static library and each build target has a 'project directory' in the source tree.
The project directory contains source and header files relating to that library or build target.

Finding project directories for the static libraries

Projects directories for the libraries are located in 'SDKRoot/code/libs'.

Finding project directories for the build targets themselves

Project directories for build targets are located directly in the 'SDKRoot/code' directory.
So the PathEngine dll project directory is 'SDKRoot/code/PathEngine', the testbed project directory is 'SDKRoot/code/TestBed', and so on.