|How to add a tool that doesn't have an output? [message #1794102]
||Thu, 23 August 2018 14:40
| Kenny McCartney
Registered: August 2018
I'm trying (unsuccessfully) to add support for a new tool to our existing tool support in our Eclipse IDE, and I seem to be having problems. There are a few quirks with the new tool:
- it won't actually produce an output - it'll just update the executable file that is passed to it
- I don't want it to be the default target of the build command - I just want and additional target in the makefile that I can (optionally) call at some later point.
So, what I want to produce is something like this in the makefile.
# All Target
# Tool invocations
@echo 'Building target: $@'
# Usual build commands go here.
# Command for my new tool goes here. "MY_TOOL" is not the default make target
@echo Running my new tool
my_new_tool a.exe [OPTIONS]
I've successfully added the tool and options to the project options, and I can update the options when I create a project, but nothing shows up in the makefile, and I suspect it's because there's no explicit target that I'm building for (and therefore Eclipse assumes that no makefile rule is required). Is there a trick here? Is there a way to ensure that the build command for my new tool is generated in the makefile, even though there's no (apparent) target?
I've been through the CDT plug-in developer guide, and I guessed that not defining an outputType element for the tool would be the way to go, but I had no luck with that, and I'm now stuck.
Powered by FUDForum
. Page generated in 0.01549 seconds