This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:launcher [2022/11/15 13:54] – [TestLauncher] ursgraf | dev: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 // | * Eclipse Launcher: In Eclipse it possible to define run configurations and perform a run. This event is handled by the // | ||
- | * Standalone Launcher: The // | + | * Standalone Launcher: The // |
* Test Launcher: The // | * Test Launcher: The // | ||
- Step | - Step | ||
Line 35: | Line 35: | ||
===== Standalone Launcher ===== | ===== Standalone Launcher ===== | ||
- | In the package // | + | In the package // |
< | < | ||
Usage: java org.deepjava.launcher.StandAloneLauncher [/config ConfigName] deepfile | Usage: java org.deepjava.launcher.StandAloneLauncher [/config ConfigName] deepfile | ||
Line 55: | Line 55: | ||
</ | </ | ||
===== 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 "< | * --deepfile microzedExampleProject.deep --targetconfig BootFromRam --interface-files-path "< |