Introduction to Rational® EGL Community Edition generation

Whenever you save an EGL source file, EGL uses that EGL source code to generate either JavaScript™ (for Rich UI Handlers) or Java™ (for services). At the end of the development process, you can deploy the generated code to the target platform where the application will run; see Deploying EGL applications.

EGL build

The EGL build process compiles your EGL source-code files and stores the output in a set of files that are used for debugging and generation. The built files are called IR files because they provide an intermediate representation of the generated output.

Most builds are incremental, adding content to existing IR files. The Workbench also provides the Clean option, which removes and rebuilds the IR files.

EGL generation

The EGL generation process requires not only IR files, but a set of rules that are specific to the target platform. You provide those rules by specifying a set of definitions that are called build parts. The build parts affect how output is generated, as well as how output is deployed. The most important build part is the build descriptor.

EGL generation includes a second validation step to ensure that the input to generation is appropriate to the target platform. This validation step is the source of most messages from the EGL generator.


Feedback