
Hitachi Embedded Workshop User Manual
50
3.3.2
Build File Phase Order
If you were to select a C source file from the “Workspace” window and then activate [Build->Build File] (or
press
) you would expect the file to be compiled. Likewise, if you were to select an assembly source file from
the workspace window and then activate [Build->Build File] you would expect the file to be assembled. The
connection between file group and which phase(s) to execute is managed by the “Build File Order” tab of the
“Build Phases” dialog (figure 3.9).
Figure 3.9: Build Phases Dialog Build File Order Tab
The list displays all of the current phases that will be executed when the build file operation is selected upon the
file group shown in the “File group” list box. In figure 3.9 the “C source file” file group is selected and the
“Compiler” and “MyPhase” phases are associated with it.
Entries in the “Phase order” list, of the “Build File Order” tab, are added automatically as new entries are added
to the “Build Order” tab. For example, if you were to add a phase which takes C source files as input then this
phase will be automatically added to the list of phases to execute when a build file operation is applied to a C
source file. If you don’t want a certain phase to execute when [Build->Build File] is selected then clear the
check box to the left of the phase name in the “Phase order” list.
3.4
Setting Custom Build Phase Options
Once you have defined a custom phase, you will want to specify the command line options that should be used
when it is executed. Each defined phase has a menu option on the [Options] menu. To specify options for that
phase select it. The dialog that will be invoked depends upon whether the custom phase selected was a multiple
or single phase (according to the selection of phase type in figure 3.3b).