Community
Participate
Working Groups
During custom toolchain creation, the toolChain`s Extension Element Details page should indicate that the toolChain`s targetTool property is required, and cannot be empty. This can be indicated with a * (asterisk) character after the property name, just like it is done with the id property.
This is not a bug in PDE (plugin development environment). However, I can't figure out where it belongs. Closing as INVALID. If you reopen with additional information we can move it to a different component.
Hi Curtis, I am not willing to reopen. You have a better grasp on what is a bug an what is not. However I am willing to provide as much additional information as possible and required to fix this. As this little issue caused me to struggle for weeks, without success, with a custom toolChain creation. So please let me know, what information shall I provide.
Fixing this should be as simple as checking a box in the schema file for the extension point you reference. The problem is that I have no idea who owns that extension point. The first step would for you to provide the fully qualified name of the extension point you are using. Is this C++ developement? My google search suggests that you might be using Eclipse CDT.
"org.eclipse.cdt.managedbuilder.core.buildDefinitions" is the extension point I am using. Under this, I`ve created a <projectType>, under that a <configuration>, and under that a <toolChain>, just like the Managed Build System Extensibility Document describes this in Section 6. I am using Eclipse CDT (4.3M3) for the plug-in development. I also found some references on this targetTool property in the above mentioned MBS document: "A tool-chain should specify the targetTool attribute to identify the tool that runs to generate the primary build output. If this is not specified, MBS uses the file extension of the build artifact name supplied by the user. This will work when the user uses one of the extensions expected by the tool, but will not work if they do not." I gave it a try to define the file extension of the build artifact and leave the targetTool property empty (just as the document describes), but I was not able to make this working. Of course I could be mistaken on defining the extension properly, but for me it seems that without the targetTool it is not going to work.
Reopening and moving to CDT.
