Distribution Files: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
==Overview== | ==Overview== | ||
The installation packages described in the [[Desktop Installation]] article contain a set of components necessary to | The installation packages described in the [[Desktop Installation]] article contain a set of components necessary to be installed on the software build system as part of your STRIDE target integration. | ||
== Source Components == | == Source Components == |
Latest revision as of 23:17, 29 March 2013
Overview
The installation packages described in the Desktop Installation article contain a set of components necessary to be installed on the software build system as part of your STRIDE target integration.
Source Components
These components are distributed in source form.
STRIDE Runtime
This component contains ANSI C/C++ source files implementing the STRIDE Runtime. The runtime is the fundamental component of the STRIDE framework as it implements services for testing while providing seamless connectivity between the target application and the host operating system.
An Operating System-specific Platform Abstraction Layer (PAL) is also required to map specific OS services to runtime system calls.
The runtime files are typically built into a library that is then linked with your target application.
NOTE: An OS-specific SDK component (see below) will contain the runtime sources along with an appropriate PAL, makefile to build the SRIDE Runtime library and other useful stuff.
Platform SDK
An SDK is a target platform specific component that contains the STRIDE Runtime and a complete PAL implementation. In addition it includes a default configuration and a sample Makefile to easily build a convinient stride library and a strideDaemon application.
Each of the standard Platform SDKs we provide is also intended to be used as an off-target evaluation or development sandbox. This allows you to use STRIDE in a small, controlled environment without needing to make changes to your target build. In addition, the SDK Makefile can serve as an example of the steps needed to integrate STRIDE with your target build. For more information, see Off-Target Environment.
Samples
The samples are a collection of native and script code that demonstrates the techniques for creating and executing tests using the STRIDE Framework. For more information, see Samples.
Binary Components
Build Tools
The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process as part of your target build. For more information, see Build Tools.