Summary

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

Details

Page properties

Content

...	...	@@ -30,7 +30,7 @@
30	30
31	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	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
	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. To use a variablethe syntax is **${**//variable_name//**}**. The variables that are set are
34	34
35	35	* //main_name// : The file name, including its file extension (e.g. //MyModel.sct//)
36	36	* //main_path// : The project relative path (e.g. //src/MyModel.sct//)
...	...	@@ -44,10 +44,20 @@
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.
	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. (Screenshot of selection dialog)
48	48
	49	+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.
	50	+
	51	+The **compilation via KiCo** is configured on the //Compilation// tab. Here you can add/remove files that should be compiled via KiCo and the target language as well as the file extension for the language (such as //.java// for Java). The files will be compiled sequentially in order of appearance in the list. Further, it is possible to add a file path to a template for the output. This is useful to add surrounding content to the KiCo output. The placeholder //${kico_code}// can be used in the template.
	52	+
	53	+On the //Execute// tab, a list of **shell commands** can be added. They are executed sequentially in order as they appear in the list, after the KiCo compilation and wrapper code generation finished successfully. If a command fails (returns a non-zero exit code), following commands will not be excuted. The name of commands have to be unique and must not contain a comma.
	54	+
	55	+The standard streams of executed shell commands (stdin, stderr, stdout), as well as errors from the KiCo compilation and wrapper code generation, are printed to the **Console View**. (Screenshot)
	56	+
49	49	=== Launch Groups ===
50	50
	59	+
	60	+
51	51	== Prom Environments ==
52	52
53	53	Environments are used to provide default settings for project creation and launch. They are configured in the **preferences** (Window > Preferences > KIELER > Environments).
...	...	@@ -67,12 +67,10 @@
67	67
68	68	A main file typically contains the entry point of the program on the target environment. Its wrapper code initializes and runs the model and sets inputs and outputs to the physical components of the target device. To ease the project setup and because wrapper code for a specific target platform is often similar, it is possible to define default content for the main file. Therefore the field **main file origin** can contain an absolute file path to a file with the default contents of a newly created main file for this Environment. Furthermore predefined wrapper code snippets can be injected as part of a project launch, which is described below.
69	69
70		-The desired programming language of KiCo generated code, can be set for an Environment. Further one can define the file extension (e.g. '.java' for Java files) for that language.
	80	+The **wrapper code origin** is used to initialize the wrapper code snippet directory of a newly created project.
71	71
72		-To generate wrapper code from a model one can define an input template and a directory with files that contain wrapper code snippets. The wrapper code origin is used to initialize the wrapper code snippet directory of a newly created project.
	82	+The other fields are default settings for KiCo launch configurations.
73	73
74		-Last but not least, a list of shell commands can be defined, which will be executed sequentially when the code generation from KiCo and wrapper code generation both finished successfully. These commands are typically used to further compile the output and deploy the result to the target devide. As with names of Environments, the names of shell commands have to be unique and must not contain a comma.
75		-
76	76	=== Paths for initial content ===
77	77
78	78	== Project Wizards with Prom ==

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-13762679
	1	+13762684

URL

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