Using output of optional tools in post-build steps

When specified in a build configuration, the post-build command will be executed after generating the ELF file and before calling the optional tools (for example, generating the SREC file). For this reason, when you try to use a file produced by an optional tool in a post-build command, you get the error message “No such file or directory”.

To use secondary outputs in a post-build command, you can do one of the following:

Move your post-build commands to the custom makefile. It will build your project as usual and then execute the post-build command right after the secondary output is produced.
Create and launch a sequence of two build configurations. The first configuration will produce secondary output (SREC, HEX and LST files), and the second configuration will execute the post-build commands for these files.

Using a custom makefile

Create the makefile.targets file in the project root.
Open this file in the editor and specify the target name, for example, user_all. It should build the default all target and then execute your post build commands.
```
user_all: all post_buid_step
```
Create the post_build_step rule. It should be executed only if the optional tool output exists. In case of the SREC file, makefile defines the SECONDARY_FLASH variable for the output:
```
post_build_step: $(SECONDARY_FLASH)
```
Add the post-build commands.
In the project properties, click C/C++ Build and open the Behavior tab.
In the Build (Incremental build) field, specify your custom target instead of the default one.

Using a sequence of two build configurations

In the project properties, go to C/C++ Build > Settings. Select the first build configuration, click Cross Settings, and select optional tools to be used for building the project.
For instance, select the Create flash image option to use the Standard S32DS Create Flash Image tool. Then go to Standard S32DS Create Flash Image > General and configure the tool.
To create the second configuration, click Manage Configurations in the project properties, then click New in the pop-up dialog box. Specify the name of the second configuration. Choose to copy settings from the existing configuration and select the first configuration from the Existing configuration list. Click OK.

Then select the just created configuration in the pop-up dialog box and click Set Active. Click OK.
In the project properties, go to C/C++ General > Path and Symbols. Make sure the second configuration is selected in the Configuration field. On the Reference tab, expand the <project_name> list and flag the first configuration.
When you run the second configuration, this reference will call the first configuration prior to the second one.
In the project properties, go to C/C++ Build > Settings > Build Steps. Select the second configuration in the Configuration field and specify the post-build command that uses secondary output created by the first configuration.
For instance, save a copy of the SREC file in the project folder where output of the second configuration is stored:
Run the second configuration.
This command launches the first build configuration that creates all specified build targets, including secondary output. Then the second configuration executes the post-build command.