Changes for page Running KEITH
Last modified by Richard Kreissig on 2023/09/14 08:48
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. nre1 +XWiki.sdo - Content
-
... ... @@ -8,27 +8,40 @@ 8 8 9 9 For everything not mentioned here refer to [[Getting Eclipse>>doc:KIELER.Getting Eclipse||shape="rect"]] guide. 10 10 11 -Use the installer go to advanced mode, add the KIELER url. Thenselectfirst semanticsandafterthatpragmatics(**that is very****important**).Youcanseehatyouhavedonethatcorrectlyontheautomaticallygeneratedname ofyourEclipse:Itshould besomething like kieler-semantics-theia.11 +Use the installer go to advanced mode, add the KIELER url. If you plan to develop for the semantic language server (e.g. for the compiler) you should select KIELER semantics for diagram only KIELER pragmatics. In any case select the keith stream. 12 12 13 - SelecttheTheiastreamforsemanticsandtheKeithstream for pragmaticsand use thelatestEclipse ifpossible.Setthetargetplatformto latest andfinish.13 +If you plan to develop in elk at the same time first select the Eclispe Layout Kernel setup and after that the semantics or pragmatics setup. 14 14 15 15 Wait till everything installs and the setup tasks finish. If you have any problems in this stage refer to the [[Getting Eclipse>>doc:KIELER.Getting Eclipse||shape="rect"]] guide. 16 16 17 - \\17 +If you have problems in the workspace that are still there after a clean build do the following: 18 18 19 -The setup tasks for Modular Target will fail. Disable it after this happens and execute them again via //Help>Perform Setup Tasks//. Open the //plug-in development// perspective. Select working sets as top level elements. Run //clean build//. Several pragmatics projects have errors. Just close them and you will be fine. 19 +* Disable Project>Build automatically 20 +* Select all Klighd and pragmatics plugins and do Project>Clean>Only selected and build only selected 21 +* Do the same for the semantics projects 22 +* Enable Project>Build automatically 20 20 21 -To run the language server go to //Run Configurations// create a new E//clipse Application// run configuration and select //Run an application// and //de.cau.cs.kieler.language.server.LanguageServer// 24 +To run the language server go to //Run Configurations// create a new E//clipse Application// run configuration and select //Run an application// and //de.cau.cs.kieler.language.server.LanguageServer// (for semantics LS,//de.cau.cs.kieler.kgraph.language.server.LanguageServer// otherwise) 22 22 23 23 == [[image:attach:Screenshot from 2019-02-15 14-10-50.png]] == 24 24 25 25 \\ 26 26 27 -You have to edit the arguments too. The Vm arguments host and port are added to connect the LS via socket .30 +You have to edit the arguments too. The Vm arguments host and port are added to connect the LS via socket: 28 28 32 +{{code}} 33 +-os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl ${target.nl} -consoleLog 34 +{{/code}} 35 + 36 +{{code}} 37 +-Dhost=localhost -Dport=5007 38 +{{/code}} 39 + 40 +\\ 41 + 29 29 [[image:attach:Screenshot from 2019-02-15 14-13-34.png]] 30 30 31 -The default port to which KEITH tries to connect is 5007. 44 +The default port to which KEITH tries to connect is 5007. You can of course change this for the languae server but be aware that this has to be changed in KEITH too. 32 32 33 33 == Setting up a KEITH developer setup... == 34 34 ... ... @@ -105,8 +105,44 @@ 105 105 106 106 = Stuff that may help = 107 107 108 -== RunningthealreadybuildLS==121 +== How to run KEITH in developer setup (socket) == 109 109 123 +Run the following to build and run KEITH in its developer setup (in socket mode, so the LS has to be started separately) 124 + 125 +=== Running KEITH in the browser === 126 + 127 +\\ 128 + 129 +{{code language="bash"}} 130 +yarn && cd keith-app && yarn run socket 131 +{{/code}} 132 + 133 +//yarn// builds all the stuff. //yarn run socket// in keith-app starts the application. After an initial build via yarn you can run //yarn watch //to watch the changes in your repository. In another console you run yarn run socket in keith-app. Now refreshing your browser is enough to apply the changes. 134 + 135 +Per default the KEITH opens on localhost:3000. 136 + 137 +{{info}} 138 +If you previously build keith electron, you have to execute {{code language="none"}}yarn run rebuild:browser{{/code}} 139 +{{/info}} 140 + 141 +Run Launch in Chrome via VSCode to open a chrome browser on localhost:3000 142 + 143 +This is necessary to be able to debug in VSCode. 144 + 145 +=== Running KEITH as (unbundled) electron app === 146 + 147 +{{code language="bash"}} 148 +yarn && yarn run rebuild:electron && cd keith-app-electron && yarn run socket 149 +{{/code}} 150 + 151 +//yarn// builds all the stuff. //yarn run socket// in keith-app-electron starts the application. After an initial build via yarn you can run //yarn watch //to watch the changes in your repository. In another console you run yarn run socket in keith-app-electron. Now refreshing your browser is enough to apply the changes. 152 + 153 +{{info}} 154 +If you previously build keith electron, you have to execute {{code language="none"}}yarn run rebuild:electron{{/code}} 155 +{{/info}} 156 + 157 +== Running the already build LS (you normally do not want to do this) == 158 + 110 110 Go to the latest [[Bamboo build>>url:https://rtsys.informatik.uni-kiel.de/bamboo/browse/KISEMA-NSI||shape="rect"]] and go to Artifacts. 111 111 112 112 [[image:attach:image2019-2-7_17-46-58.png]] ... ... @@ -154,40 +154,8 @@ 154 154 155 155 The {{code language="none"}}LSP_PORT{{/code}} option is used to activate the connection via socket. It is also possible to specify a relative location to a LS via {{code language="none"}}LS_PATH=<path to LS>{{/code}}. 156 156 157 -= =HowrunKEITH in developersetup (socket)==206 += Known Issues = 158 158 159 -Run the following to build and run KEITH in its developer setup (in socket mode, so the LS has to be started separately) 160 - 161 -=== Running KEITH in the browser === 162 - 163 -\\ 164 - 165 -{{code language="bash"}} 166 -yarn && cd keith-app && yarn run socket 167 -{{/code}} 168 - 169 -//yarn// builds all the stuff. //yarn run socket// in keith-app starts the application. After an initial build via yarn you can run //yarn watch // to watch the changes in your repository. In another console you run yarn run socket in keith-app. Now refreshing your browser is enough to apply the changes. 170 - 171 -Per default the KEITH opens on localhost:3000. 172 - 173 -{{info}} 174 -If you previously build keith electron, you have to execute {{code language="none"}}yarn run rebuild:browser{{/code}} 175 -{{/info}} 176 - 177 -\\ 178 - 179 -=== Running KEITH as (unbundled) electron app === 180 - 181 -{{code language="bash"}} 182 -yarn && yarn run rebuild:electron && cd keith-app-electron && yarn run socket 183 -{{/code}} 184 - 185 -//yarn// builds all the stuff. //yarn run socket// in keith-app-electron starts the application. After an initial build via yarn you can run //yarn watch // to watch the changes in your repository. In another console you run yarn run socket in keith-app-electron. Now refreshing your browser is enough to apply the changes. 186 - 187 -{{info}} 188 -If you previously build keith electron, you have to execute {{code language="none"}}yarn run rebuild:electron{{/code}} 189 -{{/info}} 190 - 191 191 === Known issues for windows: === 192 192 193 193 nsfw.code not found: In the top level package.json exists a script called postinstall. Remove this on windows, delete the node_modules folder and rebuilt the application. This is a known issue of electron-builder.
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 - 656670791 +75694098 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/ 65667079/Running KEITH1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/75694098/Running KEITH