
Hitachi Embedded Workshop User Manual
121
8.2
Defining Version Control Commands
Commands are defined when the “Add…” or “Modify…” buttons are clicked on the dialogs shown in figure 8.3
and figure 7.4. In either case, the dialog shown in figure 8.5 is invoked.
Figure 8.5: Add/Modify Command Dialog
To define a command:
1. Enter the full path of the command into the “Version control executable” field or browse to it graphically
by clicking the “Browse…” button.
2. Enter the arguments for the command into the “Arguments” field.
3. Enter the initial directory in which you would like to run the executable from into the “Initial directory”
field or browse to it graphically by clicking the “Browse…” button. In most cases this should be set to the
“$(FILEDIR)” placeholder, i.e. execute the command from the same directory as the file.
4. Set the “Executable return code” options as described in the following section.
5. Click “OK” to define the new command.
8.2.1
Executable return code
If the return code of the command(s) can be used to indicate a failure then you should select the “Command has
failed if the return code is” option and set the two fields to the right as required.
If the “Command has failed if the return code is” option is selected then the HEW will check the return code of
each command to determine whether a failure occurred. If so, no further commands will be executed and any
other processes which would follow the commands (e.g. build) will not be executed.
If the “Return code of tool is not meaningful” option is selected then the HEW will not check the return code of
each. Consequently, all commands will execute regardless.