There are several ways to create an installation package for an STK Engine application. You can:
The process of deploying an application will depend on whether the application will be installed on a system where STK is already installed or a system that does not have STK installed. The items below outline the requirements for each option. Each set of instructions above includes instructions for creating an install for applications that may or may not be deployed on systems that already have STK installed.
64-bit binaries and base data set
32-bit binaries and base data set
Note: You can include the AGI License Server when deploying an STK Engine application.
When creating an installation package for an STK Engine Application, it's important for the STK Engine Application's installer to adhere to the following algorithm:
IF STK exists on the computer where the STK Engine Application will be installed THENCheck the version of STK that's installedIF the installed STK version is greater than or equal to the version used to build the STK Engine Application THEN Do NOT install the STK merge modules Install the STK Engine Application ELSE IF the installed STK version is less than the version used to build the STK Engine Application THEN Notify the user to upgrade STK to the same major version that was used to build the STK Engine Application ENDIF ELSE IF STK does not exist THEN Install the STK merge modules Install the STK Engine Application ENDIF
STK 11.2.1 Programming Interface