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,10 +12,26 @@
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. 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
	19	+== The KiCo Launch Configuration ==
	20	+
	21	+Prom provides a launch configuration (launch config) to
	22	+
	23	+1. compile code from models via KiCo
	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
	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	+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	+
	31	+
	32	+
	33	+=== Launch Groups ===
	34	+
19	19	== Prom Environments ==
20	20
21	21	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).
...	...	@@ -35,14 +35,16 @@
35	35
36	36	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.
37	37
38		-KiCo can produce code in different programming languages from a model file, including C and Java.
	54	+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.
39	39
40		-== Project Wizards with Prom ==
	56	+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.
41	41
42		-Todo
	58	+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.
43	43
44		-== The KiCo Launch Configuration ==
	60	+=== Paths for initial content ===
45	45
	62	+== Project Wizards with Prom ==
	63	+
46	46	Todo
47	47
48	48	== Wrapper Code Generation ==
...	...	@@ -50,3 +50,5 @@
50	50	Todo
51	51
52	52	== Automatically generated files ==
	71	+
	72	+Todo

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-13762654
	1	+13762661

URL

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