Target Integration Overview: Difference between revisions
		
		
		
		Jump to navigation
		Jump to search
		
| No edit summary | No edit summary | ||
| Line 15: | Line 15: | ||
| * Able to execute on-demand built-in diagnostics to confirm integration | * Able to execute on-demand built-in diagnostics to confirm integration | ||
| For following articles provide  | For following articles provide step by step description and details on how it should be done: | ||
| * [[Distribution Files]] | * [[Distribution Files]] | ||
| * [[Runtime Integration]] | * [[Runtime Integration]] | ||
Revision as of 23:32, 19 May 2010
It is helpful to inventory the software and hardware that you will be using with STRIDE before you begin. See Evaluating your development environment for a list of things you should know about the target, tools and processes into which you will be integrating STRIDE.
The ultimate goals of a STRIDE target integration are to:
- Update STRIDE Settings as needed
- STRIDE Compiler settings
- STRIDE Runtime configuration
 
- Update your target build process to
- Include the STRIDE Runtime sources
- Run the STRIDE Build Tools as a pre-compile step
- Make it easy to add tests
 
- Add code to your target source
- To start and stop STRIDE Runtime threads
 
- Able to execute on-demand built-in diagnostics to confirm integration
For following articles provide step by step description and details on how it should be done:
