Qualcomm's Embedded Linker (ELD) now has the build foundation for plugins that live outside the linker's source tree. A plugin can compile against an installed public interface and the LinkerWrapper library, with CMake finding the required headers and libraries. That matters for embedded teams that customize memory layout, symbol handling, or image generation but don't want every extension tied to a private checkout of the toolchain.
The change also checks required interface versions during configuration, lets a build select a subset of plugins, and leaves runtime library lookup to the deployment environment. Qualcomm validated a standalone HelloWorld plugin against its packaged toolchain and checked that the resulting binary records the expected shared-library dependency without embedding a private search path.
This foundation doesn't yet prove that third-party plugins will stay compatible across releases. It does create the boundary needed to test that promise. A firmware infrastructure team can now put one linker plugin in its own repository, build it in continuous integration against each supported ELD package, and find an interface break before the next production image is due.