A tool conflict for the tools "Create Flash Image", "Create Listing" and "Print Size" is reported in the tool chain editor. The conflict exists for all available ARM tool chains.
Reproduce by:
Project->Properties->Tool Chain Editor->Select Tools
Environment:
GNU ARM C/C++ Development Support 0.5.3.201007072245 org.eclipse.cdt.cross.arm.gnu.feature.group
Eclipse IDE for C/C++ Developers 1.3.0.20100617-0520 epp.package.cpp (Eclipse HELIOS, CDT 7.0)
I confirm the bug.
I thought the bug was introduced when I added support for Yagarto and devkitPro, so I expected a quick fix.
Unfortunately, after double checking the code and found nothing, I decided to check old versions and I discovered the bug to be also present in version 20090413, with a feeling it is there from the very beginning... :-(
Fixing it requires a look in the CDT sources, to find the condition that triggers it.
Since functionally the plug-in does not seem affected, I'm afraid we'll have to live with it for a while...
Liviu
priority raised, for a quicker fix
The bug still exists in version 0.5.4.201202210114 with Eclipse Juno build id: 20121004-1855.
I know, unfortunately it is due to some CDT strange behaviour when editing the toolchain details, I could not identify a direct plug-in bug.
In other words, using the CDT toolchain editor damages the project.
Could you try to create a new project and see if new projects work properly?
Liviu
I have created a new project and the tool chain works fine.
As a workaround I will never modifiy the settings in the Eclipse Tool Chain Editor because after removing and re-adding "Create Flash Image", "Create Listing", and "Print Size" the commands are no longer executed.
the tool conflict is also present when using the latest 1.1.0 plug-in, so more likely it is caused by a CDT bug.
to be investigated.
I further investigated this error, and it is triggered by a validation test in CDT, checking if there are multiple tools using the same input. In our case all the extra tools use the .elf generated by the linker as input, so the validation fails.
Although annoying, this message is benign.