EGL build path and eglpath

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 References to parts.

When you specify the EGL build path, you can choose to export one or more of the projects that are listed in the build path. Then, when a project refers to the project being declared, each of the exported projects is made available to the referencing project, as in the following example:

• The EGL build path for project A comprises the following projects, in order:

    A, B, C, D

  Projects B and D are exported.

• The EGL build path for project L comprises the following projects, in order:

    L, J, A, Z

• The effective build path for project L also includes the projects that were exported from project A. In this case, the EGL build path for project L is effectively as follows:

    L, J, A, B, D, Z

  The exported projects are placed after the project that exports them, in the order in which the projects are listed in the build path of the exporting project.

The build path of a project always includes the project itself, which is usually first in build-path order, as is recommended. If you have multiple EGL source folders in your project, all must be listed in the EGL build path for that project, and the order of those folders is used by any project that refers to your project.

It is strongly recommended that you avoid having identically named packages in different projects or in different folders of the same project.

If you generate in the EGL SDK, the situation is as follows:

• Project information is not available.

• The command-line argument eglpath replaces the functionality of the EGL build path. eglpath is a list of operating-system directories that are searched when the EGL SDK attempts to resolve a part reference.

• The rules for when eglpath is used are equivalent to the rules for when the EGL build path is used; however, you cannot export directories as you can export projects.

When you use the EGL SDK, it is strongly recommended that you avoid having identically named packages in different directories.

Related concepts
Generation from the EGL Software Development Kit (SDK)
References to parts

Related tasks
Generating from the EGL Software Development Kit (SDK)

Related reference
EGLSDK