deep

a Cross Development Platform for Java

User Tools

Site Tools

You are here: start » dev » launcher
dev:launcher

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
dev:launcher [2022/11/15 13:54] – [Standalone Launcher] ursgrafdev:launcher [2022/11/16 11:40] (current) – [TestLauncher] ursgraf
Line 4: Line 4:
   - Step   - Step
     * Eclipse Launcher: In Eclipse it possible to define run configurations and perform a run. This event is handled by the //launcher//.     * Eclipse Launcher: In Eclipse it possible to define run configurations and perform a run. This event is handled by the //launcher//.
-    * Standalone Launcher: The //launcher// can be started by command line. +    * Standalone Launcher: The //launcher// can be started on the command line. 
     * Test Launcher: The //launcher// is started directly by running as a regular application. This can be handy for debug purposes, see below.     * Test Launcher: The //launcher// is started directly by running as a regular application. This can be handy for debug purposes, see below.
   - Step   - Step
Line 35: Line 35:
    
 ===== Standalone Launcher ===== ===== Standalone Launcher =====
-In the package //org.deepjava.launcher// there is also a standalone launcher. It can be started from the command line and accepts a deep project file together with a configuration as parameters.+In the package //org.deepjava.launcher// there is also a standalone launcher. It can be started from the command line and accepts a deep project file together with a configuration as parameters. It compiles and links but does not download to a target.
 <code> <code>
 Usage: java org.deepjava.launcher.StandAloneLauncher [/config ConfigName] deepfile Usage: java org.deepjava.launcher.StandAloneLauncher [/config ConfigName] deepfile
Line 55: Line 55:
 </code> </code>
 ===== TestLauncher ===== ===== TestLauncher =====
-The TestLauncher is a helper class to start building projects directly from the eclipse development workspace without loading the deep plugin in the first place. The TestLauncher has to be launched as Java application with appropriate parameters Arguments could be:+The TestLauncher is a helper class to start building projects directly from the eclipse development workspace without loading the deep plugin in the first place. The TestLauncher has to be launched as Java application with appropriate parameters. Arguments could be:
   * --deepfile 555ExampleProject.deep --targetconfig BootFromRam   * --deepfile 555ExampleProject.deep --targetconfig BootFromRam
-  * --deepfile microzedExampleProject.deep --targetconfig BootFromRam --interface-files-path "<path>\org.deepjava.trglib"+  * --deepfile microzedExampleProject.deep --targetconfig BootFromRam --interface-files-path "<path>/org.deepjava.trglib"
   * --deepfile junitHostTest.deep --targetconfig BootFromRam   * --deepfile junitHostTest.deep --targetconfig BootFromRam
   * --deepfile microzedjunitTarget.deep --targetconfig BootFromRam   * --deepfile microzedjunitTarget.deep --targetconfig BootFromRam
dev/launcher.1668516858.txt.gz · Last modified: 2022/11/15 13:54 by ursgraf

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki