This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
dev:launcher [2022/11/15 13:41] – [TestLauncher] ursgraf | dev:launcher [2022/11/15 14:58] – [Standalone Launcher] 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 //ch.ntb.inf.deep.launcher// there is also a standalone launcher. It can be started from the command line and accepts | + | In the package //org.deepjava.launcher// there is also a standalone launcher. It can be started from the command line and accepts |
+ | < | ||
+ | Usage: java org.deepjava.launcher.StandAloneLauncher [/config ConfigName] deepfile | ||
+ | / | ||
+ | By specifying this switch, you can set a different | ||
+ | configuration to compile for. | ||
+ | /map Dumps a mapfile | ||
+ | deepfile | ||
+ | </ | ||
+ | e.g. | ||
+ | < | ||
+ | cd < | ||
+ | java -cp "< | ||
+ | </ | ||
+ | or if the compiler is packed into a jar file | ||
+ | < | ||
+ | java -cp < | ||
+ | </ | ||
===== 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 "C:\< | + | * --deepfile microzedExampleProject.deep --targetconfig BootFromRam --interface-files-path "< |
* --deepfile junitHostTest.deep --targetconfig BootFromRam | * --deepfile junitHostTest.deep --targetconfig BootFromRam | ||
* --deepfile microzedjunitTarget.deep --targetconfig BootFromRam | * --deepfile microzedjunitTarget.deep --targetconfig BootFromRam |