Target Integration Overview: Difference between revisions
		
		
		
		Jump to navigation
		Jump to search
		
| No edit summary | No edit summary | ||
| Line 1: | Line 1: | ||
| [[Image:STRIDE Build Process1.jpg|thumb|300px|STRIDE Build Process]] | [[Image:STRIDE Build Process1.jpg|thumb|300px|STRIDE Build Process]] | ||
| The ultimate goals of a STRIDE target integration are to: | The ultimate goals of a STRIDE target integration are to: | ||
| * Update STRIDE Settings as needed | |||
| ** [[s2scompile|STRIDE Compiler]] settings | |||
| ** [[Runtime Reference|STRIDE Runtime]] configuration | |||
| * Update your target build process to | |||
| ** [[Runtime Integration|Include the STRIDE Runtime]] sources | |||
| ** [[Build Integration|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 detailed step by step description and details on hoew it should be done: | |||
| For detailed description  | |||
| * [[Runtime Integration]] | * [[Runtime Integration]] | ||
| * [[Build Integration]] | * [[Build Integration]] | ||
Revision as of 23:37, 17 May 2010
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 detailed step by step description and details on hoew it should be done:
