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,43 +16,31 @@ 16 16 17 17 ---- 18 18 19 -== The KiCo Launch Configuration == 20 - 21 -Todo 22 - 23 23 == Prom Environments == 24 24 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).21 +Environments are used to set default settings for project creation and launching for different target platforms. 26 26 27 27 An Environment consists of 28 28 29 -1. a unique **name**, that does not contain a comma30 -1. a **related project wizard**31 -1. informationĀabout a**main file**for the project32 -1. information about the **targetcode**KiCo should produce from models33 -1. information for **wrapper code generation**34 -1. a list of **shell commands**which should be run as part of a project launch25 +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 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 35 35 36 -Besides the name, all of these are optional , but can improve the workflow.32 +Besides the name, all of these are optional. 37 37 38 38 The related project wizard is run as part of the Prom project wizard and takes care of the actual project creation. 39 39 40 - Amain 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 projectsetup and because wrapper code for a specific target platform is often similar, it is possible todefine default content for the main file. Therefore the field **main file origin** can contain an absolutefile path to a filewiththe 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.36 +== Project Wizards with Prom == 41 41 42 -T he desired programming language of KiCo generatedcode, can be set for an Environment. Further one can define the file extension (e.g. '.java' for Java files) for that language.38 +Todo 43 43 44 - Togeneratewrapper codefromamodel one can define an input template and a directory withfiles that contain wrapper code snippets. The wrapper code origin isused to initialize the wrapper code snippetdirectory of anewlycreated project.40 +== The KiCo Launch Configuration == 45 45 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 - 52 52 Todo 53 53 54 54 == Wrapper Code Generation == 55 55 56 56 Todo 57 - 58 -== Automatically generated files ==
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -137626 551 +13762647 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/137626 55/Project Creation, Initialization and Launch (Prom)1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/13762647/Project Creation, Initialization and Launch (Prom)