The Interface Layer Package

Obtaining source for the interface layer

Source code for the interface layer is provided (separately from the main release) in the 'interfaceLayerMM_mm.zip' archive, where MM is the major release number and mm is the minor release number.

Unzip the contents of this archive into the same directory as the release itself.
The interface layer and release version numbers must be the same.

Contents of the package

The package contains source code and project files for the main SDK components, and for the following internal static libraries:

• ParseXML.lib
• PathEngine_Interface.lib
• Exporter_Common.lib
• TestBed_Application.lib

Other static libraries are provided as binaries and these can then be combined with the above libraries to build 'Release', and 'Debug' configurations of the main SDK components.

Visual Studio project and solution files for the PC platform are included with the interface layer archive.

Constraints on compilation environment

Because some of the libraries in the interface layer package are supplied without source code this means that there are some constraints on the compilation environment used when linking statically against these libraries.
For example, certain compilation settings, such as the type of C standard library linkage, need to be consistent across statically linked libraries.

But note that this constraint doesn't need to apply to the whole client application, only to the interface layer source code and SDK components being built from this source code.
Once the PathEngine dll has been built with compatible compilation settings, this dll can then be dynamically linked, and the mechanism used for this dynamic linkage is something that works as standard across application code generated by many different compilation environments.