Source Code Packages

Source code packages

Source code packages are provided in separate archives from the base SDK package, but should be extracted into the same SDK root directory.

One source package is provided for each supported target platform.

Note that the source code packages are not stand-alone, and each source code package adds to the base package.
(So it is necessary to install first the base SDK package, and then the source code package or packages for the platforms you want to build for. If you install just source code package then there will be missing files when you come to build.)

A set of platform 'codes' are used to identify target platform, in source package naming, and then also in build setup and internal platform specific code directory setup.

Platform codes

PathEngine platform codes are defined as follows:

PC indicates a build for MS Windows Operating System, with x86 target processor architecture.

x64 indicates a build for MS Windows OS, with x64 target processor architecture.

GCCx86 indicates a build for environments with GCC as a compilation environment, and with x86 target processor architecture.

GCCx64 indicates a build for environments with GCC as a compilation environment, and with x64 target processor architecture.

Obtaining and installing the source code packages

The source code packages should be downloaded from the downloads page on the PathEngine website.

Unzip the contents of each source code archive into the same directory as the base SDK archive (making sure that the package version match for the two archives).

Each package contains source code and project files for the main SDK components, with Visual Studio project files included, where relevant, and alternative project setup information for other platforms (see Building with the Python Build Scripts).

There are common files shared by all of the source code archives (and also between source code and binary packages), so you may need to tell your dearchiver tool to 'ignore repeated files' in order to avoid warnings about this, when installing more than one package on top of the base archive.