Changes for page Project Creation, Initialization and Launch (Prom)
Last modified by Richard Kreissig on 2023/09/14 10:56
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -16,31 +16,43 @@ 16 16 17 17 ---- 18 18 19 +== The KiCo Launch Configuration == 20 + 21 +Todo 22 + 19 19 == Prom Environments == 20 20 21 -Environments are used to set default settings for project creation and launching for different target platforms. 25 +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). 22 22 23 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. dataabout a main file for the project28 -1. information about the target 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 29 +1. a unique **name**, that does not contain a comma 30 +1. a **related project wizard** 31 +1. informationĀ about a **main file** for the project 32 +1. information about the **target code** KiCo should produce from models 33 +1. information for **wrapper code generation** 34 +1. a list of **shell commands** which should be run as part of a project launch 31 31 32 -Besides the name, all of these are optional. 36 +Besides the name, all of these are optional, but can improve the workflow. 33 33 34 34 The related project wizard is run as part of the Prom project wizard and takes care of the actual project creation. 35 35 36 - ==ProjectWizards withProm==40 +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 -Todo 42 +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 - ==TheKiCoLaunchConfiguration==44 +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 46 +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. 47 + 48 +=== Paths for initial content === 49 + 50 +== Project Wizards with Prom == 51 + 42 42 Todo 43 43 44 44 == Wrapper Code Generation == 45 45 46 46 Todo 57 + 58 +== Automatically generated files ==
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -137626 471 +13762655 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/137626 47/Project Creation, Initialization and Launch (Prom)1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/13762655/Project Creation, Initialization and Launch (Prom)