|
|
| (10 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| ==Overview== | | ==Overview== |
| This article describes the packages to be installed on the software build system as part of your STRIDE target integration.
| | 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. |
|
| |
|
| STRIDE Framework components are distributed as a set of compressed archives. Each archive package comprises functionally-related files. The content of each the listed in here packages is also included in the [[Desktop Installation]].
| | == Source Components == |
| | These components are distributed in source form. |
|
| |
|
| = Source Packages = | | === STRIDE Runtime === |
| These packages are distributed in source form.
| | This component contains ANSI C/C++ source files implementing the [[Runtime Reference|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. |
| | |
| == STRIDE Runtime == | |
| This package contains ANSI C/C++ source files implementing the [[Runtime Reference|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 [[Runtime_Reference#The_Platform_Abstraction_Layer|Platform Abstraction Layer]] (PAL) is also required to map specific OS services to runtime system calls. | | An Operating System-specific [[Runtime_Reference#The_Platform_Abstraction_Layer|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. An OS-specific SDK package (see [[#Platform_SDK|below]]) will contain the runtime sources along with an appropriate PAL, makefile to build the runtime library and other useful stuff. | | The runtime files are typically built into a library that is then linked with your target application. |
|
| |
|
| === Installation ===
| | '''NOTE:''' ''An OS-specific SDK component (see [[#Platform_SDK|below]]) will contain the runtime sources along with an appropriate PAL, makefile to build the SRIDE Runtime library and other useful stuff.'' |
| The STRIDE runtime sources are distributed as a zip archive. To install, run an unzipping utility, maintaining the directory structure of the archived files. We recommend that you create a parent directory named "stride" into which you upzip the archive.
| |
|
| |
|
| '''Note:''' All SDK packages include the STRIDE runtime. If you will be installing an SDK or have installed an SDK, explicit runtime installation is unnecessary.
| | === Platform SDK === |
| | An SDK is a target platform specific component that contains the [[#STRIDE_Runtime|STRIDE Runtime]] and a complete [[Runtime_Reference#The_Platform_Abstraction_Layer|PAL]] implementation. In addition it includes a default configuration and a sample Makefile to easily build a convinient stride library and a strideDaemon application. |
|
| |
|
| ==== Linux ====
| | Each of the standard [[:Category:SDKs|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 [[STRIDE Off-Target Environment | Off-Target Environment]]. |
| The following installation example assumes that the runtime archive is located in your home directory and that the directory <tt>~/stride</tt> exists. The version numbers in your archive file name may be different than those shown in the example.
| |
|
| |
|
| cd ~/stride
| | === Samples === |
| unzip ../STRIDE_runtime-src_4.1.xx.zip
| |
| | |
| Once unzipped, files will have been installed under <tt>~/stride/SDK</tt>.
| |
| | |
| ==== Windows ==== | |
| The following installation example assumes the the runtime archive is located in your root directory and that the directory <tt>\stride</tt> exists. The version numbers in your archive file name may be different than those shown in the example.
| |
| | |
| The example uses the open source [http://www.7-zip.org/ 7-Zip] utility to unzip the archive.
| |
| | |
| cd \stride
| |
| "\Program Files\7-Zip\7z" x ..\STRIDE_runtime-src_4.1.xx.zip
| |
| | |
| Once unzipped, files will have been installed under <tt>\stride\SDK</tt>.
| |
| | |
| == Platform SDK ==
| |
| An SDK is a target platform specific package that contains the [[#STRIDE_Runtime|STRIDE Runtime]] and a complete [[Runtime_Reference#The_Platform_Abstraction_Layer|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 [[:Category:SDKs|Platform SDK packages]] 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 [[The Sandbox]].
| |
| | |
| === Installation ===
| |
| SDKs are distributed as zip archives. To install, run an unzipping utility, maintaining the directory structure of the archived files. We recommend that you create a parent directory named "stride" into which you upzip the archive.
| |
| | |
| ==== Linux ====
| |
| The following installation example assumes that the SDK archive is located in your home directory and that the directory <tt>~/stride</tt> exists. The version numbers in your archive file name may be different than those shown in the example.
| |
| | |
| cd ~/stride
| |
| unzip ../STRIDE_sdk-linux_4.1.xx.zip
| |
| | |
| Once unzipped, files will have been installed under <tt>~/stride/SDK</tt>.
| |
| | |
| ==== Windows ====
| |
| The following installation example assumes the the SDK archive is located in your root directory and that the directory <tt>\stride</tt> exists. The version numbers in your archive file name may be different than those shown in the example.
| |
| | |
| The example uses the open source [http://www.7-zip.org/ 7-Zip] utility to unzip the archive.
| |
| | |
| cd \stride
| |
| "\Program Files\7-Zip\7z" x ..\STRIDE_sdk-windows_4.1.xx.zip
| |
| | |
| Once unzipped, files will have been installed under <tt>\stride\SDK</tt>.
| |
| | |
| == 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]]. | | 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]]. |
|
| |
|
| ===Installation=== | | == Binary Components == |
| The Test Unit samples are distributed as zip archives. To install, run an unzipping utility, maintaining the directory structure of the archived files. We recommend that you unzip the archive into a parent directory named "stride".
| |
| | |
| ====Linux====
| |
| The following installation example assumes that the Samples archive is located in your home directory and that the directory <tt>~/stride</tt> exists. The version numbers in your archive file name may be different than those shown in the example.
| |
| | |
| cd ~/stride
| |
| unzip ../STRIDE_samples_4.1.xx.zip
| |
| | |
| Once unzipped, files will have been installed under <tt>~/stride/Samples</tt>.
| |
| | |
| ====Windows====
| |
| The following installation example assumes the the Samples archive is located in your root directory and that the directory <tt>\stride</tt> exists. The version numbers in your archive file name may be different than those shown in the example.
| |
| | |
| The example uses the open source [http://www.7-zip.org/ 7-Zip] utility to unzip the archive.
| |
| | |
| cd \stride
| |
| "\Program Files\7-Zip\7z" x ..\STRIDE_samples_4.1.xx.zip
| |
| | |
| Once unzipped, files will have been installed under <tt>\stride\Samples</tt>.
| |
| | |
| =Binary Packages= | |
| | |
| == 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]].
| |
| | |
| === Installation ===
| |
| The build tools are distributed as zip archives on Windows and tgz archives on Linux. To install, run the appropriate decompression utility. It's recommended that these files be placed in a location that is on your PATH as they are run as part of an application build.
| |
| | |
| ==== Linux ====
| |
| The following installation example assumes that the build tools archive is located in your home directory and that the directory <tt>~/stride/bin</tt> exists. The version numbers in your archive file name may be different than those shown in the example.
| |
| | |
| cd ~/stride/bin
| |
| tar xvzf ~/STRIDE_buildtools-linux-gcc41_4.1.xx.tgz
| |
| | |
| ==== Windows ====
| |
| The following installation example assumes the the build tools archive is located in your root directory and that the directory <tt>\stride\bin</tt> exists. The version numbers in your archive file name may be different than those shown in the example.
| |
| | |
| The example uses the open source [http://www.7-zip.org/ 7-Zip] utility to unzip the archive.
| |
| | |
| cd \stride\bin
| |
| "\Program Files\7-Zip\7z" x \STRIDE_buildtools-windows_4.1.xx.zip
| |
|
| |
|
| === Related Topics === | | === Build Tools === |
| * [[Desktop Installation]]
| | 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]]. |
| * [[Stride_Runner#Environment_Variables|Environment Variable Setup]]
| |
|
| |
|
| [[Category:Framework Integration]] | | [[Category:Installation]] |
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.