I filed IZ#152247 on behalf of MC. Although the issue was resolved, the
resolution doesn't satisfy MC's requirements. What they need is a means
of replacing the NativeExecutor with one of their own. The fix for 152247
was at to high of a level and didn't address the root problem, which was
that MC needs to have control over execution of the binary.
Note: MC would like this issue fixed in a NB 6.7 patch.
> For embedded development our output is a hex file that we need to load
> into a piece of silicon then allow it to execute. It never executes
> natively on the PC.
> We really do not want to override the whole RUN action as we use it to
> perform all the make requirements that cnd already provides.
> All we would like to do is suppress the actual native execution of the
> output on the PC, then use that signal to go to our debugger module so
> it can perform the loading and programming of the hex file onto the
> silicon chip.
Reassigning to Andrew. He is working in this now.
Vincent, could you, please, why 152247 wasn't enough for you?
The issue 152247 only addresses customizing the action of the whole Run button.
You have to re-create the whole functionlity.
Right now CND does everything we need by calling make and building the project etc. The only issue is the final action is to execute natively the output at the end. Since in most native development, the output is an application. Launching an application is accpetable.
The results of our build is a hex file that needs to be loaded into a target tool and then allowed to execute remote from the PC.
We would like to customize ONLY the last action step of executing the native application.