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.
A, B, C, D
Projects B and D are exported.
L, J, A, Z
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.
When you use the EGL SDK, it is strongly recommended that you avoid having identically named packages in different directories.
Related tasks
Generating from the EGL Software Development Kit (SDK)
Related reference
EGLSDK