This topic provides an overview of the validation workflow used to determine whether an RTSS/RTDLL binary is compatible with the wRTOS Runtime version that attempts to run it.
Validation Workflow
Step 1:
The user develops and builds an RTSS application or RTDLL. As a post-build step, the binary must be stamped using the StampTool that is provided as part of the SDK for it to be runnable by a wRTOS Runtime. The binaries are stamped with the version and license information of the SDK version that was used to build it.
Note: You can verify the stamped data of a binary using wRTOS StampTool with the /info flag.
Step 2:
The user runs the binary. wRTOS Runtime checks for the following criteria in the binary's stamp:
- Was the binary stamped with a valid license?
- Was the binary built by a compatible wRTOS SDK version?
The answer to the criteria must be Yes for wRTOS Runtime to run the application or load the RTDLL. If the answer to any one of the two criteria is No, wRTOS Runtime rejects the binary.
Note: A binary built by a Retail version SDK can be run on either a Retail or Evaluation Runtime. A binary built by an Evaluation SDK can only be run on an Evaluation Runtime.
Version Compatibility
Binaries built with wRTOS 1.0 SDK and later versions will run on wRTOS 1.0 Runtime and later, unless:
- The binary calls an API that does not exist in the Runtime.
- A breaking compatibility change occurred between major versions (see the Release Notes or Porting Guide).
