Summary

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

Details

Page properties

Content

...	...	@@ -24,8 +24,6 @@
24	24	1. at the same time, generate wrapper code for these model files
25	25	1. afterwards, execute arbitrary shell commands sequentially, if the KiCo compilation and wrapper code generation finished successfully
26	26
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		-
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	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.
...	...	@@ -50,7 +50,7 @@
50	50
51	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	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.
	51	+On the //Execute// tab, a list of **shell commands** can be added. They are typically used to further compile the KiCo and wrapper code output and afterwards deploy the result to the target platform. The commands 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	54
55	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	56
...	...	@@ -67,7 +67,7 @@
67	67	1. a unique **name**, that does not contain a comma
68	68	1. a **related project wizard**
69	69	1. information about a **main file** for the project
70		-1. information about the **target code** KiCo should produce from models
	68	+1. information about the **target code** KiCo should produce
71	71	1. information for **wrapper code generation**
72	72	1. a list of **shell commands** which should be run as part of a project launch
73	73
...	...	@@ -75,7 +75,7 @@
75	75
76	76	The related project wizard is run as part of the Prom project wizard and takes care of the actual project creation.
77	77
78		-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.
	76	+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.
79	79
80	80	The **wrapper code origin** is used to initialize the wrapper code snippet directory of a newly created project.
81	81
...	...	@@ -83,6 +83,8 @@
83	83
84	84	=== Paths for initial content ===
85	85
	84	+The paths for main file origin and snippets origin accept an URL with the platform protocol provided by Eclipse.
	85	+
86	86	== Project Wizards with Prom ==
87	87
88	88	Todo

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-13762684
	1	+13762686

URL

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