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:

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

Visual Studio 2005 project and solution files for the PC platform are included with the interface layer archive.
Project and solution files for other platforms (or alternative build infrastructure, in the case of non-MS platforms) can be found in the relevant platform source archives.

The remaining static libs are provided as binaries ('Release' and 'Debug' configurations). These can then be used to build 'Release', and 'Debug' configurations of the main SDK components.

Constraints on compilation environment

Because some of the internal libraries are supplied in binary form this puts some constraints on the compilation environment used when building from the interface layer source package.

Specifically, the compilation environment used in this case must be link compatible with the environment used to build the supplied static libs.
The interface layer binaries in the current release were built with Visual Studio 2005.

Note that this constraint doesn't apply to the whole client application, only to the interface layer source code and SDK components being built.
Once the PathEngine dll has been built with a compatible compilation environment, this dll is then dynamically linked, which is something that works as standard across application code generated by many different compilation environments.

Note, also, that this constraint doesn't apply when building from the full source package, since, in this case, all internal libraries are built from source.