STRIDE Extensions for Visual Studio - Revision history

Ivailop at 19:32, 7 January 2016

2016-01-07T19:32:14Z

← Older revision		Revision as of 19:32, 7 January 2016
Line 90:		Line 90:
	=== STRIDE Compile-Instrument Properties ===		=== STRIDE Compile-Instrument Properties ===

	==== Visual Studio 2010 ~~/ 2012~~ ====		==== Visual Studio 2010 (or newer) ====

	The default settings are usually sufficient so you don't need to make any changes.		The default settings are usually sufficient so you don't need to make any changes.

Marku: /* Sort Out Header Files */

2015-07-06T21:22:40Z

Sort Out Header Files

← Older revision		Revision as of 21:22, 6 July 2015
Line 79:		Line 79:

	=== Sort Out Header Files ===		=== Sort Out Header Files ===
	Every header file in the project that has [[~~Test_Units_Pragmas2 \| pragmas~~]] will cause harnessing code to be generated when processed by the STRIDE compiler. (Other non-stride header files can also be processed by the STRIDE compiler, but this only results in longer compile times.)		Every header file in the project that has [[Test Pragmas]] will cause harnessing code to be generated when processed by the STRIDE compiler. (Other non-stride header files can also be processed by the STRIDE compiler, but this only results in longer compile times.)

	For each header file to be used as input to the STRIDE rules:		For each header file to be used as input to the STRIDE rules:

Marku at 19:22, 3 July 2015

2015-07-03T19:22:06Z

← Older revision		Revision as of 19:22, 3 July 2015
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
	~~If you are using the STRIDE Framework for Windows, an alternative to the [[Building_an_Off-Target_Test_App \| standard method]] of building test apps (using ''make'') is to use the STRIDE~~ Extensions for Visual Studio ~~and~~ integrate directly into your existing Visual Studio C/C++ project.		The Stride Extensions for Visual Studio can be used to integrate directly into your existing Visual Studio C/C++ project.

	== Prerequisites ==		== Prerequisites ==
	* Visual Studio 2008 or later (an express distribution is fine)		* Visual Studio 2008 or later (an express distribution is fine)
	* a recent version of the ~~STRIDE Framework [[Desktop_Installation#Windows_Installation\|~~installed]]		* a recent version of the Stride installed
	* a static library version of the runtime built using the source files included in the [[Windows_SDK \| Windows SDK]]		* a static library version of the runtime built using the source files included in the [[Windows_SDK \| Windows SDK]]
	** to build the library open a [http://msdn.microsoft.com/en-us/library/ms235639(v=vs.100).aspx Visual Studio Command Prompt] and do as follows:		** to build the library open a [http://msdn.microsoft.com/en-us/library/ms235639(v=vs.100).aspx Visual Studio Command Prompt] and do as follows:
Line 21:		Line 21:

	== Installation ==		== Installation ==
	STRIDE Extensions need to be added to any project that is to generate ~~harnessing code (i~~.~~e. a project that includes header files with [[Test_Units \| test code declarations]].)~~		STRIDE Extensions need to be added to any project that is to generate ''intercept module''.

	=== Visual Studio 2010 (or newer) ===		=== Visual Studio 2010 (or newer) ===
Line 79:		Line 79:

	=== Sort Out Header Files ===		=== Sort Out Header Files ===
	Every header file in the project that has [[~~Test_Units~~ \| ~~test code declarations~~]] will cause harnessing code to be generated when processed by the STRIDE compiler. (Other non-stride header files can also be processed by the STRIDE compiler, but this only results in longer compile times.)		Every header file in the project that has [[Test_Units_Pragmas2 \| pragmas]] will cause harnessing code to be generated when processed by the STRIDE compiler. (Other non-stride header files can also be processed by the STRIDE compiler, but this only results in longer compile times.)

	~~<u>''NOTE:''</u> ''If you don't have any header with test code declarations, you could simple create a new one using [[Test_Units#Simple_Test_Unit_Examples \| this snippet]].''~~

	For each header file to be used as input to the STRIDE rules:		For each header file to be used as input to the STRIDE rules:
Line 142:		Line 140:
	== Update Your Startup ==		== Update Your Startup ==

	Update your application's main function to initialize the STRIDE subsystem as described in [[Windows_SDK#Target_Integration \| this article]].		Update your application's main function to initialize the STRIDE subsystem as described in [[Windows_SDK#Target_Integration \| this article]]. <u>''Note''</u> ''that the sample code assumes you have generated your Intercept Module with a name of '''myintercept'''. Make sure to replace any reference to that token in the code to the name you [[#STRIDE_Compile-Instrument_Properties \| chose above]].''

	<u>''~~NOTE:~~''</u> ''~~This~~ sample code assumes you have generated your Intercept Module with a name of '''myintercept'''. Make sure to replace any reference to that token in the code to the name you [[#STRIDE_Compile-Instrument_Properties \| chose above]].''

Marku at 19:37, 11 November 2014

2014-11-11T19:37:04Z

← Older revision		Revision as of 19:37, 11 November 2014
Line 145:		Line 145:

	<u>''NOTE:''</u> ''This sample code assumes you have generated your Intercept Module with a name of '''myintercept'''. Make sure to replace any reference to that token in the code to the name you [[#STRIDE_Compile-Instrument_Properties \| chose above]].''		<u>''NOTE:''</u> ''This sample code assumes you have generated your Intercept Module with a name of '''myintercept'''. Make sure to replace any reference to that token in the code to the name you [[#STRIDE_Compile-Instrument_Properties \| chose above]].''

	~~[[Category: Installation]]~~

Ivailop: /* Installation */

2014-03-21T18:59:11Z

Installation

← Older revision		Revision as of 18:59, 21 March 2014
Line 23:		Line 23:
	STRIDE Extensions need to be added to any project that is to generate harnessing code (i.e. a project that includes header files with [[Test_Units \| test code declarations]].)		STRIDE Extensions need to be added to any project that is to generate harnessing code (i.e. a project that includes header files with [[Test_Units \| test code declarations]].)

	=== Visual Studio 2010 ~~/ 2012~~ ===		=== Visual Studio 2010 (or newer) ===
	* Right click on the project in the '''Solution Explorer''' window and choose '''Build Customizations…''' from the menu that is displayed.		* Right click on the project in the '''Solution Explorer''' window and choose '''Build Customizations…''' from the menu that is displayed.
	* In the dialog that is displayed, click '''Find Existing…''' and select '''$(STRIDE_DIR)\SDK\Windows\settings\stride.targets''' (if asked, say “No” to adding to standard “Build Customizations Search Path”)		* In the dialog that is displayed, click '''Find Existing…''' and select '''$(STRIDE_DIR)\SDK\Windows\settings\stride.targets''' (if asked, say “No” to adding to standard “Build Customizations Search Path”)
Line 29:		Line 29:

	=== Visual Studio 2008 ===		=== Visual Studio 2008 ===
	<u>''NOTE:''</u> ''Due to limitations in Visual Studio 2008 the STRIDE integration is much more complicated compared to new versions. We recommend upgrading to Visual Studio 2010 or ~~2012~~.''		<u>''NOTE:''</u> ''Due to limitations in Visual Studio 2008 the STRIDE integration is much more complicated compared to new versions. We recommend upgrading to Visual Studio 2010 or newer.''

	* Right click on the project in the '''Solution Explorer''' window and choose '''Build Custom Build Rules...''' from the menu that is displayed.		* Right click on the project in the '''Solution Explorer''' window and choose '''Build Custom Build Rules...''' from the menu that is displayed.

Ivailop: /* Prerequisites */

2012-12-27T20:12:36Z

Prerequisites

← Older revision		Revision as of 20:12, 27 December 2012
Line 5:		Line 5:
	* Visual Studio 2008 or later (an express distribution is fine)		* Visual Studio 2008 or later (an express distribution is fine)
	* a recent version of the STRIDE Framework [[Desktop_Installation#Windows_Installation\|installed]]		* a recent version of the STRIDE Framework [[Desktop_Installation#Windows_Installation\|installed]]
	* a static library version of the runtime built using the source files included in the [[Windows_SDK \| Windows SDK]]:		* a static library version of the runtime built using the source files included in the [[Windows_SDK \| Windows SDK]]
			** to build the library open a [http://msdn.microsoft.com/en-us/library/ms235639(v=vs.100).aspx Visual Studio Command Prompt] and do as follows:
	<pre>		<pre>
	> md %STRIDE_DIR%\SDK\Windows\lib		> md %STRIDE_DIR%\SDK\Windows\lib

Ivailop: /* Prerequisites */

2012-12-11T19:52:44Z

Prerequisites

← Older revision		Revision as of 19:52, 11 December 2012
Line 10:		Line 10:
	> cd %STRIDE_DIR%\SDK\Windows\src		> cd %STRIDE_DIR%\SDK\Windows\src
	> ..\bin\make clean		> ..\bin\make clean
	> ..\bin\make		> ..\bin\make RTSINGLEPROC=0
	> copy %STRIDE_DIR%\SDK\Windows\out\lib\stride-x86-Windows_NT.lib %STRIDE_DIR%\SDK\Windows\lib\stride.lib		> copy %STRIDE_DIR%\SDK\Windows\out\lib\stride-x86-Windows_NT.lib %STRIDE_DIR%\SDK\Windows\lib\stride.lib
	> ..\bin\make clean		> ..\bin\make clean
	> ..\bin\make DEBUG=1		> ..\bin\make RTSINGLEPROC=0 DEBUG=1
	> copy %STRIDE_DIR%\SDK\Windows\out\lib\stride-x86-Windows_NT-d.lib %STRIDE_DIR%\SDK\Windows\lib\stride-d.lib		> copy %STRIDE_DIR%\SDK\Windows\out\lib\stride-x86-Windows_NT-d.lib %STRIDE_DIR%\SDK\Windows\lib\stride-d.lib
	</pre>		</pre>
	* an existing C/C++ Visual Studio project		* an existing C/C++ Visual Studio project
	** or you can easily create a new one, e.g. "Win32 Console Application", by using the project wizard provided within Visual Studio.		** or you can easily create a new one, e.g. "Win32 Console Application", by using the project wizard provided within Visual Studio.

	== Installation ==		== Installation ==

Ivailop: /* Update Your Startup */

2012-12-11T19:51:09Z

Update Your Startup

← Older revision		Revision as of 19:51, 11 December 2012
Line 143:		Line 143:
	Update your application's main function to initialize the STRIDE subsystem as described in [[Windows_SDK#Target_Integration \| this article]].		Update your application's main function to initialize the STRIDE subsystem as described in [[Windows_SDK#Target_Integration \| this article]].

	<u>''NOTE:''</u> ''This sample code assumes you have generated your Intercept Module with a name of '''myintercept'''. ~~Refer~~ to the ~~section~~ [[#STRIDE_Compile-Instrument_Properties \| above]]'' ~~on configuring the Intercept Module name.~~		<u>''NOTE:''</u> ''This sample code assumes you have generated your Intercept Module with a name of '''myintercept'''. Make sure to replace any reference to that token in the code to the name you [[#STRIDE_Compile-Instrument_Properties \| chose above]].''

	[[Category: Installation]]		[[Category: Installation]]

Ivailop: /* Visual Studio 2010 / 2012 */

2012-12-11T19:46:53Z

Visual Studio 2010 / 2012

← Older revision		Revision as of 19:46, 11 December 2012
Line 96:		Line 96:

	When you build your project, notice that:		When you build your project, notice that:
	* The STRIDE build tools automatically run and generate a STRIDE database (.sidb) file and an intercept module (IM) source ~~file~~. By default the names are derived from '''$(TargetName)''', and the associated files are written to the '''$(ProjectDir)''' directory.		* The STRIDE build tools automatically run and generate a STRIDE database (.sidb) file and intercept module (IM) source files. By default the names are derived from '''$(TargetName)''', and the associated files are written to the '''$(ProjectDir)''' directory.
	* The IM source, ''$(TargetName)IM.cpp'', is automatically compiled and linked along with your other project sources.		* The IM source, ''$(TargetName)IM.cpp'', is automatically compiled and linked along with your other project sources.

Line 102:		Line 102:
	* Right click on the project in the '''Solution Explorer''' window and choose '''Properties''' from the menu that is displayed.		* Right click on the project in the '''Solution Explorer''' window and choose '''Properties''' from the menu that is displayed.
	* From the properties dialog, select '''Configuration Properties \| STRIDE Compile-Instrument'''		* From the properties dialog, select '''Configuration Properties \| STRIDE Compile-Instrument'''
	* Update '''Database Name''' and/or the '''Intercept Module Name''' ~~from the~~ right pane values as desired.		* Update '''Database Name''' and/or the '''Intercept Module Name''' right pane values as desired.

	<u>''NOTE:''</u> ''If you do not see '''STRIDE Compile-Instrument''' try [[#Sort_Out_Header_Files \| adding a header file]] to your project.''		<u>''NOTE:''</u> ''If you do not see '''STRIDE Compile-Instrument''' try [[#Sort_Out_Header_Files \| adding a header file]] to your project.''

Marku: /* Update Your Startup */

2012-12-11T16:39:22Z

Update Your Startup

← Older revision		Revision as of 16:39, 11 December 2012
Line 143:		Line 143:
	Update your application's main function to initialize the STRIDE subsystem as described in [[Windows_SDK#Target_Integration \| this article]].		Update your application's main function to initialize the STRIDE subsystem as described in [[Windows_SDK#Target_Integration \| this article]].

	<u>''NOTE:''</u> ''This sample code assumes you have generated your Intercept Module with a name of '''myintercept'''. ~~Make sure to replace any reference to that token you the code~~ to the ~~name you~~ [[#STRIDE_Compile-Instrument_Properties \| ~~chose~~ above]].''		<u>''NOTE:''</u> ''This sample code assumes you have generated your Intercept Module with a name of '''myintercept'''. Refer to the section [[#STRIDE_Compile-Instrument_Properties \| above]]'' on configuring the Intercept Module name.

	[[Category: Installation]]		[[Category: Installation]]