Using eglpath with the EGL SDK

When you develop your EGL source code in the workbench, each EGL project and EGL web project is associated with an EGL build path so that the project can reference parts in other projects. For details on when the EGL build path is used and on why the order of build-path entries is important, see “Scope.” This topic describes how the eglpath argument affects the EGL build path when you generate with the java EGLSDK command.

If you generate in the EGL SDK and not in the workbench, the situation is as follows:
  • Project information is not available.
  • The command-line option eglpath replaces the functionality of the EGL build path.
  • The rules for when to use eglpath are equivalent to the rules for when to use the EGL build path.

The eglpath option specifies a list of root directories and EGLAR files, separated by semicolons. The root directories contain EGL files within an EGL package structure.

For example, suppose you have files belonging to Projects A and B, on your C drive, and each of those projects has two packages: Project A has myPackage1 and myPackage2, and Project B has myPackageX and myPackageY.

In this example, you would set the eglpath argument to: 
"C:\ProjectA\EGLSource;C:\ProjectB\EGLSource"
Note:
The EGL package structure must be maintained under the specified root directories, so that the generator can resolve references to parts correctly.