<
From version < 2.1 >
edited by aas2
on 2015/08/19 14:25
To version < 6.1 >
edited by aas2
on 2015/08/19 15:25
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -12,18 +12,39 @@
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. To do so, there are //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. 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.
16 16  
17 17  ----
18 18  
19 19  == Prom Environments ==
20 20  
21 -Todo
21 +Environments are used to set default settings for project creation and launching for different target platforms.
22 22  
23 -== Using Project Wizards with Prom ==
23 +An Environment consists of
24 24  
25 +1. a unique **name**, that does not contain a comma
26 +1. a **related project wizard**
27 +1. data about a **main file** for the project
28 +1. information about the **target language** KiCo should produce from models
29 +1. information for **wrapper code generation**
30 +1. a list of **shell commands** which should be run as part of a project launch
31 +
32 +Besides the name, all of these are optional, but can improve the workflow.
33 +
34 +The related project wizard is run as part of the Prom project wizard and takes care of the actual project creation.
35 +
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 +
38 +
39 +
40 +== Project Wizards with Prom ==
41 +
25 25  Todo
26 26  
27 27  == The KiCo Launch Configuration ==
28 28  
29 29  Todo
47 +
48 +== Wrapper Code Generation ==
49 +
50 +Todo
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -13762628
1 +13762650
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/13762628/Project Creation, Initialization and Launch (Prom)
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/13762650/Project Creation, Initialization and Launch (Prom)