|
That should work. The following sequence using the attached sample does:
1) Open the project and build (F7). The subroutine step will fail and failure steps get built. Build output:
Building project step 'Project steps'...
Building project step 'call sub'...
Building subroutine step 'Sub1'...
Building subroutine step 'dir something'...
'dirxyz' is not recognized as an internal or external command,
operable program or batch file.
Process completed with exit code 1
Step 'dir something' failed
Building failure step 'fail message'...
step dir something failed with output
'dirxyz' is not recognized as an internal or external command,
operable program or batch file.
Process completed with exit code 1
Build ended.
2) Correct the 'dir something' subroutine step by removing xyz from the command. Build | Start (F7) builds the failed step, returns from the subroutine (skips the 2nd subroutine) and builds the remaining project steps:
--------------------Starting Build: 'testfail.bld'--------------------
Building subroutine step 'dir something'...
Volume in drive C has no label.
Volume Serial Number is A0EE-9B67
Directory of C:\
<some dir output>
Building project step 'log completion'...
a step running after the subroutine
Build successfully completed.
Be careful not to re/start the build in other ways (rebuild selected, rebuild, start from cursor, etc.), as those actions will reset the build call stack.
|