Difference between revisions of "STRIDE Off-Target Environment"
| Line 1: | Line 1: | ||
| − | |||
[[image:STRIDE_Desktop.jpg|right|300px| The Off-Target configuration puts both host and target code on the desktop]] | [[image:STRIDE_Desktop.jpg|right|300px| The Off-Target configuration puts both host and target code on the desktop]] | ||
| − | Two | + | Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a '''host-only''' ''Off-Target Configuration'' that emulates your target system. |
| − | + | In order to conduct '''training''' or build and execute our [[Samples_Overview | Samples]], we leverage this environment (i.e. single Windows or Linux (x86) computer for both the target and host systems). Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ''Off-Target Environment'' are directly transferable to a production environment. This enables the user to create their own ''sandbox'' for training and Off-Target unit testing. | |
| − | + | The Off-Target Environment utilizes the [[Desktop_Installation#SDK|Framework's "SDK"]] that can be built and executed on the host system. When using the SDK Makefile a simulated target ''native application'' is generated, which we call a '''Test Application (TestApp)'''. | |
| + | |||
| + | The [[STRIDE Runner]] application executes on the same system and communicates with the '''TestApp''' process over a TCP/IP connection. This setup frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle. | ||
| + | |||
| + | Please verify that your Host system contains one of the following '''compilers''': | ||
| + | * For Windows Microsoft Visual Studio 2005 or later is required. If you don't already have Visual Studio, the free [http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express Visual C++ Express] can be used (download [http://www.microsoft.com/express/download/#webInstall here]). | ||
| + | * For Linux the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] (included by default in almost all Linux distros) is required. | ||
| + | |||
| + | For instructions on building a '''TestApp''' refer to the following [[Build a TestApp | article]]. | ||
| − | |||
| − | |||
[[Category:Installation]] | [[Category:Installation]] | ||
Revision as of 16:05, 8 June 2011
Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a host-only Off-Target Configuration that emulates your target system.
In order to conduct training or build and execute our Samples, we leverage this environment (i.e. single Windows or Linux (x86) computer for both the target and host systems). Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the Off-Target Environment are directly transferable to a production environment. This enables the user to create their own sandbox for training and Off-Target unit testing.
The Off-Target Environment utilizes the Framework's "SDK" that can be built and executed on the host system. When using the SDK Makefile a simulated target native application is generated, which we call a Test Application (TestApp).
The STRIDE Runner application executes on the same system and communicates with the TestApp process over a TCP/IP connection. This setup frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.
Please verify that your Host system contains one of the following compilers:
- For Windows Microsoft Visual Studio 2005 or later is required. If you don't already have Visual Studio, the free Visual C++ Express can be used (download here).
- For Linux the GNU Compiler Collection (included by default in almost all Linux distros) is required.
For instructions on building a TestApp refer to the following article.
