Build Output Files

When building a Standalone Application, multiple files are generated next to the ELF executable file.

Launch Output Folder

Using a MicroEJ Application Launch, the files are generated in a folder which is named like the main type and which is located in the output folder specified in the run configuration.

Build Output Files from MicroEJ Application Launch

Build Output Files from MicroEJ Application Launch

Published Module Files

After building the Standalone Application, the published module contains the following main files:

  • [name]-[version].out: Firmware (ELF Executable)
  • [name]-[version].zip: Virtual Device
  • [name]-[version] Build intermediate files, including the content of the launch output Folder)
Published Standalone Application Module Files

Published Standalone Application Module Files

The SOAR Map File

The file lists every embedded symbol of the application (section, Java class or method, etc.) and its size in ROM or RAM. This file can be opened using the Memory Map Analyzer.

The embedded symbols are grouped into multiple categories. For example, the Object class and its methods are grouped in the LibFoundationEDC category. For each symbol or each category, you can see its size in ROM (Image Size) and RAM (Runtime Size).

The SOAR groups all the Java strings in the same section, which appears in the ApplicationStrings category. The same applies to the static fields (Statics category), the types (Types category), and the class names (ClassNames category).

The SOAR Information File

The soar/<main class>.xml file can be opened using any XML editor.

This file contains the list of the following embedded elements:

  • method (in selected_methods tag)
  • resource (in selected_resources tag)
  • system property (in java_properties tag)
  • string (in selected_internStrings tag)
  • type (in selected_types tag)
  • immutable (in selected_immutables tag)