Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Content

...	...	@@ -12,7 +12,7 @@
12	12
13	13	The KIELER Compiler (KiCo) can generate different code targets from models. For example it is possible to generate C and Java code from an SCT file. As a result KIELER has to integrate with existing development tools and practices for the C and Java world. In the context of embedded systems, the target device also varies heavily.
14	14
15		-Therefore the KIELER Project Management (Prom) has been developed. It eases the creation, compilation and deployment of projects, when using models that can be compiled via KiCo (e.g. SCCharts, Esterel). Furthermore it eases the creation of wrapper code, which is used to initialize and run the model. To do so, there are mainly three components, //Project Wizards//, an Eclipse //Launch Configuration// and so called //Environments//, which will be introduces in the following.
	15	+Therefore the KIELER Project Management (Prom) has been developed. It eases the creation, compilation and deployment of projects, when using models that can be compiled via KiCo (e.g. SCCharts, Esterel). Furthermore it eases the creation of wrapper code, which is used to initialize and run the model. To do so, there are mainly three components: An Eclipse //Launch Configuration//, so called //Environments//, and //Project Wizards,// which will be introduces in the following.
16	16
17	17	----
18	18
...	...	@@ -22,17 +22,35 @@
22	22
23	23	1. compile code from models via KiCo
24	24	1. at the same time, generate wrapper code for these model files
25		-1. execute arbitrary shell commands sequentially if the KiCo compilation and wrapper code generation finished successfully
	25	+1. afterwards, execute arbitrary shell commands sequentially, if the KiCo compilation and wrapper code generation finished successfully
26	26
27	27	The shell commands are typically used to further compile the KiCo and wrapper code output and afterwards deploy the result to the target platform.
28	28
29	29	KiCo launch configurations work per project basis, thus every project has to create its own launch config. This is done automatically when performing //Right Click > Run As > KiCo Compilation //(% style="color: rgb(0,51,102);" %)on a model file.(%%) (Screenshot)
30	30
	31	+The **Run As** command will search for a KiCo launch config for the project. If there is such a config, the selected file is only added to the list of model files which should be compiled. If there is none, a launch config is created by using the main file and environment the project has been created with. If the main file and environment information could not be found, dialogs will query it from the user.
	32	+
	33	+The **main file** of the launch config is used to set several file path variables, which can be used in several fields of the configuration, notably the shell commands to be executed, and wrapper code input. The variables that are set are
	34	+
	35	+* //main_name// : The file name, including its file extension (e.g. //MyModel.sct//)
	36	+* //main_path// : The project relative path (e.g. //src/MyModel.sct//)
	37	+* //main_loc// : The absolute file system path (e.g. ///home/me/workspace/MyProject/src/MyModel.sct//)
	38	+* //main_name_no_ext// : The file name without its file extension (e.g. //MyModel//)
	39	+
	40	+Further, similar variables for the compiled main path are set, that is, the main file in the directory of kieler generated files (see below)
	41	+
	42	+* //compiled_main_name// : The file name, including its file extension (e.g. //MyModel.sct//)
	43	+* //compiled_//main_path : The project relative path (e.g. //kieler-gen/MyModel.sct//)
	44	+* //compiled_//main_loc : The absolute file system path (e.g. ///home/me/workspace/MyProject/kieler-gen/MyModel.sct//)
	45	+* //compiled_//main_name_no_ext : The file name without its file extension (e.g. //MyModel//)
	46	+
	47	+//**Note:**// The variables are created in the first KiCo launch. So if you want to select them in a variable selection dialog of Eclipse, you must have started at least one KiCo launch configuration.
	48	+
31	31	=== Launch Groups ===
32	32
33	33	== Prom Environments ==
34	34
35		-Environments are used to set default settings for project creation and launching for different target platforms. They are configured in the **preferences** (Window > Preferences > KIELER > Environments).
	53	+Environments are used to provide default settings for project creation and launch. They are configured in the **preferences** (Window > Preferences > KIELER > Environments).
36	36
37	37	An Environment consists of
38	38

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-13762660
	1	+13762679

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/13762660/Project Creation, Initialization and Launch (Prom)
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/13762679/Project Creation, Initialization and Launch (Prom)