Summary

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

Details

Page properties

Content

...	...	@@ -22,7 +22,8 @@
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. afterwards, execute arbitrary shell commands sequentially if the KiCo compilation and wrapper code generation finished successfully
	25	+1. afterwards run an associated launch configuration (e.g. for a Java Application) and
	26	+1. execute arbitrary shell commands sequentially if the KiCo compilation and wrapper code generation finished successfully
26	26
27	27	KiCo launch configurations work per project basis so that 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.
28	28
...	...	@@ -44,8 +44,6 @@
44	44	* //compiled_//main_loc : The absolute file system path (e.g. ///home/me/workspace/MyProject/kieler-gen/MyModel.sct//)
45	45	* //compiled_//main_name_no_ext : The file name without its file extension (e.g. //MyModel//)
46	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		-
49	49	[[image:attach:variable_selection_dialog.png]]
50	50
51	51	The values of the launch config can also be **(re)set to an environment**. This will revert the fields for the compilation target, wrapper code generation and command execution.
...	...	@@ -78,12 +78,13 @@
78	78
79	79	An environment consists of
80	80
81		-1. a unique **name**, that does not contain a comma
	80	+1. a unique **name**, which may not contain a comma
82	82	1. a **related project wizard**
83	83	1. information about a **main file** for the project
84	84	1. information about the **target code** KiCo should produce
85	85	1. information for **wrapper code generation**
86		-1. a list of **shell commands** which should be run as part of a project launch
	85	+1. a list of **shell commands**, which should be run as part of a project launch
	86	+1. an **associated launch shortcut**, which is used on the compiled main file
87	87
88	88	Besides the name, all of these are optional, but can improve the workflow.
89	89
...	...	@@ -133,8 +133,10 @@
133	133
134	134	In the **template file** one can use special **placeholders**.
135	135
136		-**${model_name}** will be replaced with the name of the model.
	136	+**${file_name}** is replaced with the name withouth extension of the file that is generated (e.g. //Main.java// will be //Main//).
137	137
	138	+**${model_name}** is replaced with the name of the last compiled model.
	139	+
138	138	**${declarations}** and** ${decls}** will be replaced with additional declarations of variables and functions (<@decl>...</@decl> of a snippet definition). Declarations should occur before the tick loop of the model file. In general they are not required for Java code but may be useful in C applications (e.g. for //extern// calls).
139	139
140	140	**${initializations}** and **${inits}** will be replaced with initialization code for components (<@init>...</@init> of a snippet definition). Initialization should occur before the tick loop of the model file.

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-15532232
	1	+16810575

URL

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