The Eclipse Embedded CDT plug-ins for Arm & RISC-V C/C++ developers (formerly known as the GNU MCU Eclipse plug-ins). Includes the archive of previous plug-ins versions, as Releases.
The current logic identifies toolchains by the name.
The new RISC-V toolchain showed that this might not be unique, and the toolchains must be identified by a long name, which includes the executable name.
Internally toolchains must be identified by the unique ID, which is an unsigned long, initially based on the Java hash, but not necessarily.
This should also fix the unexplained inconsistencies in IDs, in RISC-V configurations, like toolchain.path.2021824384 vs "...toolchain.id..." ... value="2273142912", forxPack GNU RISC-V Embedded GCC` (the correct hash is the value, not the path key).
ilg-ul
commented
2 years ago
The current logic identifies toolchains by the name.
The new RISC-V toolchain showed that this might not be unique, and the toolchains must be identified by a long name, which includes the executable name.
Internally toolchains must be identified by the unique ID, which is an unsigned long, initially based on the Java hash, but not necessarily.
This should also fix the unexplained inconsistencies in IDs, in RISC-V configurations, like
toolchain.path.2021824384vs"...toolchain.id..." ... value="2273142912", forxPack GNU RISC-V Embedded GCC` (the correct hash is the value, not the path key).Also the Linaro toolchains have unexpected IDs.