STRIDE Build Tools - Revision history

Marku at 14:43, 4 July 2015

2015-07-04T14:43:13Z

← Older revision		Revision as of 14:43, 4 July 2015
Line 1:		Line 1:
	~~==Overview==~~		__NOTOC__
	[[image:STRIDE Build Process1.jpg\|thumb\|\|STRIDE Build Process Overview]]		[[image:STRIDE Build Process1.jpg\|thumb\|\|STRIDE Build Process Overview]]
	The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process on a supported platform, which may be easily invoked through makefiles or similar build utilities (eg. ANT).		The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process on a supported platform, which may be easily invoked through makefiles or similar build utilities (eg. ANT).

	~~Refer to~~ [[~~Build Integration~~]] ~~on how to obtain and integrate them in your environment.~~		The Build Tools consist of the following utilities:
			# [[s2scompile\|The STRIDE Compiler (s2scompile)]]<br>
			# [[s2sbind\|The STRIDE Database Binder (s2sbind)]]<br>
			# [[s2sinstrument\|The STRIDE Instrumentation Generator (s2sinstrument)]]

	~~==Command Line Utilities==~~
	~~# [[s2scompile\|The STRIDE Compiler (s2scompile)]]<br><br>~~
	~~# [[s2sbind\|The STRIDE Database Binder (s2sbind)]]<br><br>~~
	~~# [[s2sinstrument\|The STRIDE Instrumentation Generator (s2sinstrument)]]~~
	~~''Follow the above links for detailed information on each build tool.''~~

	~~==Examples==~~		Refer to [[Build Integration]] on how to obtain and integrate them in your environment.

	===Compiling multiple files===		=Compiling multiple files=
	In this scenario, the '''s2scompile''' utility is invoked with a list of header files, containing SCL, each to be compiled a resulting intermediate (.meta) file:		In this scenario, the '''s2scompile''' utility is invoked with a list of header files, containing SCL, each to be compiled a resulting intermediate (.meta) file:

	s2scompile –I"path/to/include" –DN=100 file1.h file2.h		s2scompile –I"path/to/include" –DN=100 file1.h file2.h

	===Database Binding===		=Database Binding=
	Here, the '''s2sbind''' utility is invoked with a list of .meta files to be bound into the specified database (.sidb) file:		Here, the '''s2sbind''' utility is invoked with a list of .meta files to be bound into the specified database (.sidb) file:

	s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta file2.h.meta		s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta file2.h.meta

	===Intercept Module Generation===		=Intercept Module Generation=
	====Single Intercept Module====
	=====Pre-build Instrumentation=====		==Single Intercept Module==

			===Pre-build Instrumentation===
	In this scenario, the compilation, binding and instrumentation are done before the user’s build. Here, '''s2scompile''' is called first, then '''s2sbind''', and finally '''s2sinstrument''':		In this scenario, the compilation, binding and instrumentation are done before the user’s build. Here, '''s2scompile''' is called first, then '''s2sbind''', and finally '''s2sinstrument''':

Line 32:		Line 32:
	s2sinstrument –-im_name=test -–mode=S(f1) -–mode=P(f2) test.sidb		s2sinstrument –-im_name=test -–mode=S(f1) -–mode=P(f2) test.sidb

	=====In-build Prototyping with Post-build Implementation=====		===In-build Prototyping with Post-build Implementation===
	Here, the compilation, binding and Intercept Module(IM) prototyping (header files only generation) are done incrementally. Note that at the second bind step during prototyping, '''s2sbind''' is given an option specifying the existing database to merge with. Also note that '''s2sinstrument''' is called the first two times with the "prototype" option specified and then finally is called with the "implement" option for code generation:		Here, the compilation, binding and Intercept Module(IM) prototyping (header files only generation) are done incrementally. Note that at the second bind step during prototyping, '''s2sbind''' is given an option specifying the existing database to merge with. Also note that '''s2sinstrument''' is called the first two times with the "prototype" option specified and then finally is called with the "implement" option for code generation:

Line 45:		Line 45:
	s2sinstrument –-im_name=test –-implement -–mode=S(f10,f11) -–mode=P(f20,f21) test.sidb		s2sinstrument –-im_name=test –-implement -–mode=S(f10,f11) -–mode=P(f20,f21) test.sidb

	====Multiple Intercept Modules====		==Multiple Intercept Modules==
	The compilation, binding and Intercept Module(IM) generation (headers and source) are done incrementally. For each component of the user’s build just a subset of SCL files are compiled, bound to a database (merged into the previously created database) and an IM generated for a set of interfaces defined in those SCL files.		The compilation, binding and Intercept Module(IM) generation (headers and source) are done incrementally. For each component of the user’s build just a subset of SCL files are compiled, bound to a database (merged into the previously created database) and an IM generated for a set of interfaces defined in those SCL files.
	This example shows how this can be accomplished. Notice that a unique name is specified for each IM when s2sinstrument is called:		This example shows how this can be accomplished. Notice that a unique name is specified for each IM when s2sinstrument is called:
Line 57:		Line 57:
	s2sinstrument –-im_name=test2 -–mode=P(f2) test.sidb		s2sinstrument –-im_name=test2 -–mode=P(f2) test.sidb

	====Partial Intercept Module====		==Partial Intercept Module==

	By default, the instrumentation of a referenced database generates IM code for all functions. If no '''--mode''' option is specified the generate IM code would be all Stub.		By default, the instrumentation of a referenced database generates IM code for all functions. If no '''--mode''' option is specified the generate IM code would be all Stub.
Line 70:		Line 70:

	s2sinstrument --default_mode=# --mode=P(f1,f2) test.sidb		s2sinstrument --default_mode=# --mode=P(f1,f2) test.sidb


	~~[[Category: Reference]]~~
	~~[[Category: Build Tools]]~~

Ivailop: /* Examples */

2011-07-06T19:29:16Z

Examples

← Older revision		Revision as of 19:29, 6 July 2011
Line 16:		Line 16:
	In this scenario, the '''s2scompile''' utility is invoked with a list of header files, containing SCL, each to be compiled a resulting intermediate (.meta) file:		In this scenario, the '''s2scompile''' utility is invoked with a list of header files, containing SCL, each to be compiled a resulting intermediate (.meta) file:

	s2scompile –I"~~C:\STRIDE\inc~~" –DN=100 file1.h file2.h		s2scompile –I"path/to/include" –DN=100 file1.h file2.h

	===Database Binding===		===Database Binding===
Line 28:		Line 28:
	In this scenario, the compilation, binding and instrumentation are done before the user’s build. Here, '''s2scompile''' is called first, then '''s2sbind''', and finally '''s2sinstrument''':		In this scenario, the compilation, binding and instrumentation are done before the user’s build. Here, '''s2scompile''' is called first, then '''s2sbind''', and finally '''s2sinstrument''':

	s2scompile ~~–I”C:\STRIDE\inc”~~ –DN=100 file1.h file2.h		s2scompile –I"path/to/include" –DN=100 file1.h file2.h
	s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta file2.h.meta		s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta file2.h.meta
	s2sinstrument –-im_name=test -–mode=S(f1) -–mode=P(f2) test.sidb		s2sinstrument –-im_name=test -–mode=S(f1) -–mode=P(f2) test.sidb
Line 35:		Line 35:
	Here, the compilation, binding and Intercept Module(IM) prototyping (header files only generation) are done incrementally. Note that at the second bind step during prototyping, '''s2sbind''' is given an option specifying the existing database to merge with. Also note that '''s2sinstrument''' is called the first two times with the "prototype" option specified and then finally is called with the "implement" option for code generation:		Here, the compilation, binding and Intercept Module(IM) prototyping (header files only generation) are done incrementally. Note that at the second bind step during prototyping, '''s2sbind''' is given an option specifying the existing database to merge with. Also note that '''s2sinstrument''' is called the first two times with the "prototype" option specified and then finally is called with the "implement" option for code generation:

	s2scompile ~~–I”C:\STRIDE\inc”~~ –DN=100 file1.h		s2scompile –I"path/to/include" –DN=100 file1.h
	s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta		s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta
	s2sinstrument –-im_name=test –-prototype=p1 -–mode=S(f10,f11) test.sidb		s2sinstrument –-im_name=test –-prototype=p1 -–mode=S(f10,f11) test.sidb

	s2scompile ~~–I”C:\STRIDE\inc”~~ –DN=100 file2.h		s2scompile –I"path/to/include" –DN=100 file2.h
	s2sbind –-input_database=test.sidb --output=test.sidb file2.h.meta		s2sbind –-input_database=test.sidb --output=test.sidb file2.h.meta
	s2sinstrument –-im_name=test –-prototype=p2 -–mode=P(f20,f21) test.sidb		s2sinstrument –-im_name=test –-prototype=p2 -–mode=P(f20,f21) test.sidb
Line 49:		Line 49:
	This example shows how this can be accomplished. Notice that a unique name is specified for each IM when s2sinstrument is called:		This example shows how this can be accomplished. Notice that a unique name is specified for each IM when s2sinstrument is called:

	s2scompile ~~–I”C:\STRIDE\inc”~~ –DN=100 file1.h		s2scompile –I"path/to/include" –DN=100 file1.h
	s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta		s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta
	s2sinstrument –-im_name=test1 -–mode=S(f1) test.sidb		s2sinstrument –-im_name=test1 -–mode=S(f1) test.sidb

	s2scompile ~~–I”C:\STRIDE\inc”~~ –DN=100 file2.h		s2scompile –I"path/to/include" –DN=100 file2.h
	s2sbind –-input_database=test.sidb --output=test.sidb file2.h.meta		s2sbind –-input_database=test.sidb --output=test.sidb file2.h.meta
	s2sinstrument –-im_name=test2 -–mode=P(f2) test.sidb		s2sinstrument –-im_name=test2 -–mode=P(f2) test.sidb

Marku: moved Build Tools to STRIDE Build Tools

2010-06-07T16:08:04Z

moved Build Tools to STRIDE Build Tools

← Older revision	Revision as of 16:08, 7 June 2010
(No difference)

Ivailop at 22:42, 17 May 2010

2010-05-17T22:42:07Z

← Older revision		Revision as of 22:42, 17 May 2010
Line 3:		Line 3:
	The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process on a supported platform, which may be easily invoked through makefiles or similar build utilities (eg. ANT).		The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process on a supported platform, which may be easily invoked through makefiles or similar build utilities (eg. ANT).

	Refer to [[~~Test~~ Integration]] on how to obtain and integrate them in your environment.		Refer to [[Build Integration]] on how to obtain and integrate them in your environment.

	==Command Line Utilities==		==Command Line Utilities==

Ivailop: /* Overview */

2009-06-17T05:58:58Z

Overview

← Older revision		Revision as of 05:58, 17 June 2009
Line 3:		Line 3:
	The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process on a supported platform, which may be easily invoked through makefiles or similar build utilities (eg. ANT).		The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process on a supported platform, which may be easily invoked through makefiles or similar build utilities (eg. ANT).

	Refer to [[~~Build~~ Integration]] on how to obtain and integrate them in your environment.		Refer to [[Test Integration]] on how to obtain and integrate them in your environment.

	==Command Line Utilities==		==Command Line Utilities==

Timd at 23:32, 21 April 2009

2009-04-21T23:32:10Z

← Older revision		Revision as of 23:32, 21 April 2009
Line 1:		Line 1:
	==Overview==		==Overview==
	[[image:STRIDE Build ~~Process~~.jpg\|thumb\|\|STRIDE Build Process Overview]]		[[image:STRIDE Build Process1.jpg\|thumb\|\|STRIDE Build Process Overview]]
	The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process on a supported platform, which may be easily invoked through makefiles or similar build utilities (eg. ANT).		The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process on a supported platform, which may be easily invoked through makefiles or similar build utilities (eg. ANT).

Timd: /* Overview */

2009-04-21T18:56:02Z

Overview

← Older revision		Revision as of 18:56, 21 April 2009
Line 1:		Line 1:
	==Overview==		==Overview==
			[[image:STRIDE Build Process.jpg\|thumb\|\|STRIDE Build Process Overview]]
	The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process on a supported platform, which may be easily invoked through makefiles or similar build utilities (eg. ANT).		The STRIDE Build Tools are a set of command line utilities that perform the Stride compile/build process on a supported platform, which may be easily invoked through makefiles or similar build utilities (eg. ANT).

	Refer to [[Build Integration]] on how to obtain and integrate them in your environment.		Refer to [[Build Integration]] on how to obtain and integrate them in your environment.

	==Command Line Utilities==		==Command Line Utilities==

Ivailop: /* Partial Intercept Module */

2009-03-20T00:30:22Z

Partial Intercept Module

← Older revision		Revision as of 00:30, 20 March 2009
Line 66:		Line 66:
	s2sinstrument --default_mode=P --mode=(f3) test.sidb		s2sinstrument --default_mode=P --mode=(f3) test.sidb

	In certain cases it might be desirable to generate partial intercept module - IM code for only specific set of functions. That requires disabling the default behaviour and listing the requested functions with '''--mode''' option. For example to generate ~~Stub\|Delegate\|User\|Dynamic~~ IM code for only functions f1 and f2:		In certain cases it might be desirable to generate partial intercept module - IM code for only specific set of functions. That requires disabling the default behaviour and listing the requested functions with '''--mode''' option. For example to generate Proxy IM code for only functions f1 and f2:

	s2sinstrument --default_mode=# --mode=~~SDud#myGroupID~~(f1,f2) test.sidb		s2sinstrument --default_mode=# --mode=P(f1,f2) test.sidb


	[[Category: Reference]]		[[Category: Reference]]
	[[Category: Build Tools]]		[[Category: Build Tools]]

Ivailop: /* Multiple Intercept Modules */

2009-03-20T00:29:00Z

Multiple Intercept Modules

← Older revision		Revision as of 00:29, 20 March 2009
Line 50:		Line 50:
	s2scompile –I”C:\STRIDE\inc” –DN=100 file1.h		s2scompile –I”C:\STRIDE\inc” –DN=100 file1.h
	s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta		s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta
	s2sinstrument –-im_name=test1 -–mode=~~SDud#myGroupID~~(f1) test.sidb		s2sinstrument –-im_name=test1 -–mode=S(f1) test.sidb

	s2scompile –I”C:\STRIDE\inc” –DN=100 file2.h		s2scompile –I”C:\STRIDE\inc” –DN=100 file2.h

Ivailop: /* In-build Prototyping with Post-build Implementation */

2009-03-20T00:28:43Z

In-build Prototyping with Post-build Implementation

← Older revision		Revision as of 00:28, 20 March 2009
Line 36:		Line 36:
	s2scompile –I”C:\STRIDE\inc” –DN=100 file1.h		s2scompile –I”C:\STRIDE\inc” –DN=100 file1.h
	s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta		s2sbind –-starting_suid=123 --output=test.sidb file1.h.meta
	s2sinstrument –-im_name=test –-prototype=p1 -–mode=~~SDud#myGroupID~~(f10,f11) test.sidb		s2sinstrument –-im_name=test –-prototype=p1 -–mode=S(f10,f11) test.sidb

	s2scompile –I”C:\STRIDE\inc” –DN=100 file2.h		s2scompile –I”C:\STRIDE\inc” –DN=100 file2.h
Line 42:		Line 42:
	s2sinstrument –-im_name=test –-prototype=p2 -–mode=P(f20,f21) test.sidb		s2sinstrument –-im_name=test –-prototype=p2 -–mode=P(f20,f21) test.sidb

	s2sinstrument –-im_name=test –-implement -–mode=~~SDud#myGroupID~~(f10,f11) -–mode=P(f20,f21) test.sidb		s2sinstrument –-im_name=test –-implement -–mode=S(f10,f11) -–mode=P(f20,f21) test.sidb

	====Multiple Intercept Modules====		====Multiple Intercept Modules====