Desktop Installation: Difference between revisions
m (Packages moved to Installation) |
No edit summary |
||
| Line 3: | Line 3: | ||
= Source Packages = | = Source Packages = | ||
These packages are distributed in source form | These packages are distributed in source form. | ||
== STRIDE Runtime == | == STRIDE Runtime == | ||
| Line 15: | Line 15: | ||
The runtime files are typically built into a library that is then linked with your target application. An OS-specific SDK package 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. An OS-specific SDK package will contain the runtime sources along with an appropriate PAL, makefile to build the runtime library and other useful stuff. | ||
The | === Installation === | ||
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. | |||
==== 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. | |||
<source lang="bash"> | |||
cd ~/stride | |||
unzip ../STRIDE4.1_runtime-src_4.1.01.zip | |||
</source> | |||
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. | |||
<source lang="dos"> | |||
cd \stride | |||
"\Program Files\7-Zip\7z" x ..\STRIDE4.1_runtime-src_4.1.01.zip | |||
</source> | |||
Once unzipped, files will have been installed under <tt>\stride\SDK</tt>. | |||
== SDK (''includes STRIDE Runtime'') == | == SDK (''includes STRIDE Runtime'') == | ||
The SDK intended to be used primarily 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 [[Sandbox Evaluation]]. | |||
=== Installation === | === Installation === | ||
SDKs are distributed as zip archives. To install, run an unzipping utility. We recommend that you create a parent directory named "stride" into which you upzip the archive. | 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 ==== | ==== Linux ==== | ||
The following installation example assumes that the SDK archive is located in your home directory. | 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. | ||
<source lang="bash"> | <source lang="bash"> | ||
cd ~ | cd ~/stride | ||
unzip ../STRIDE4.1_sdk-linux_4.1.01.zip | unzip ../STRIDE4.1_sdk-linux_4.1.01.zip | ||
</source> | </source> | ||
| Line 35: | Line 60: | ||
==== Windows ==== | ==== Windows ==== | ||
The following installation example assumes the the | 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. | |||
<source lang="dos"> | <source lang="dos"> | ||
cd \ | cd \stride | ||
"\Program Files\7-Zip\7z" x ..\STRIDE4.1_sdk-windows_4.1.01.zip | "\Program Files\7-Zip\7z" x ..\STRIDE4.1_sdk-windows_4.1.01.zip | ||
</source> | </source> | ||
| Line 47: | Line 71: | ||
Once unzipped, files will have been installed under <tt>\stride\SDK</tt>. | Once unzipped, files will have been installed under <tt>\stride\SDK</tt>. | ||
== Samples == | |||
The Test Unit samples are a collection of source code that demonstrates the techniques for creating and executing test code on a target application, in both C and C++ development environments. | |||
For more information, see [[Test Unit Samples]]. | |||
===Installation=== | |||
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. | |||
== Samples = | <source lang="bash"> | ||
cd ~/stride | |||
unzip ../STRIDE4.1_samples_4.1.01.zip | |||
</source> | |||
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. | |||
<source lang="dos"> | |||
cd \stride | |||
"\Program Files\7-Zip\7z" x ..\STRIDE4.1_samples_4.1.01.zip | |||
</source> | |||
Once unzipped, files will have been installed under <tt>\stride\Samples</tt>. | |||
=Binary Packages= | =Binary Packages= | ||
Revision as of 00:06, 3 June 2009
STRIDE Framework components are distributed as as set of compressed archives. Each archive package comprises functionally-related files.
Source Packages
These packages are distributed in source form.
STRIDE Runtime
This package contains ANSI C source files implementing the STRIDE Runtime. The runtime is the fundamental component of the STRIDE framework as it implements
- Runtime APIs - providing test services to Test Units
- An Intercept Module thread - upon which tests are run
- Host transport services - enabling I/O between the target and host computer
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. An OS-specific SDK package will contain the runtime sources along with an appropriate PAL, makefile to build the runtime library and other useful stuff.
Installation
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.
Linux
The following installation example assumes that the SDK archive is located in your home directory and that the directory ~/stride exists. The version numbers in your archive file name may be different than those shown in the example.
cd ~/stride
unzip ../STRIDE4.1_runtime-src_4.1.01.zip
Once unzipped, files will have been installed under ~/stride/SDK.
Windows
The following installation example assumes the the SDK archive is located in your root directory and that the directory \stride exists. The version numbers in your archive file name may be different than those shown in the example.
The example uses the open source 7-Zip utility to unzip the archive.
cd \stride
"\Program Files\7-Zip\7z" x ..\STRIDE4.1_runtime-src_4.1.01.zip
Once unzipped, files will have been installed under \stride\SDK.
SDK (includes STRIDE Runtime)
The SDK intended to be used primarily 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 Sandbox Evaluation.
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 ~/stride exists. The version numbers in your archive file name may be different than those shown in the example.
cd ~/stride
unzip ../STRIDE4.1_sdk-linux_4.1.01.zip
Once unzipped, files will have been installed under ~/stride/SDK.
Windows
The following installation example assumes the the SDK archive is located in your root directory and that the directory \stride exists. The version numbers in your archive file name may be different than those shown in the example.
The example uses the open source 7-Zip utility to unzip the archive.
cd \stride
"\Program Files\7-Zip\7z" x ..\STRIDE4.1_sdk-windows_4.1.01.zip
Once unzipped, files will have been installed under \stride\SDK.
Samples
The Test Unit samples are a collection of source code that demonstrates the techniques for creating and executing test code on a target application, in both C and C++ development environments.
For more information, see Test Unit Samples.
Installation
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 ~/stride exists. The version numbers in your archive file name may be different than those shown in the example.
cd ~/stride
unzip ../STRIDE4.1_samples_4.1.01.zip
Once unzipped, files will have been installed under ~/stride/Samples.
Windows
The following installation example assumes the the Samples archive is located in your root directory and that the directory \stride exists. The version numbers in your archive file name may be different than those shown in the example.
The example uses the open source 7-Zip utility to unzip the archive.
cd \stride
"\Program Files\7-Zip\7z" x ..\STRIDE4.1_samples_4.1.01.zip
Once unzipped, files will have been installed under \stride\Samples.
Binary Packages
Build Tools
s2scompile s2sbind s2sinstrument
Host Tools
The Host Tools package includes stride, the program you run on your host computer to run STRIDE tests on your target.
Requires software license.