Epson S5U1C17001C, Manual

Page: 276 / 742

5-154
EPSOn
S5U1C17001C ManUal
(C COMPilEr PaCkagE fOr S1C17 faMily) (Ver. 1.5.0)
5 gnU17 iDE
5.7.9 Executing a Build Process
After creating source files, setting build options, and editing a linker script file, you can execute a build process.
Shown below is the procedure for executing a build process.
Building all projects in the workspace
Do one of the following to build all projects present in the workspace:
• Select [Build All] from the [Project] menu.
• Click the [Build All] button in the window toolbar.
Building a selected project
Do the following to build a project individually:
(1) Select the project you want to build in the [C/C++ Projects] or [Navigator] view.
(2) Do the following to execute a build process:
• Select [Build Project] from the [Project] menu.
• Select [Build Project] from the context menu in the [C/C++ Projects] or [Navigator] view.
You also can select a working set from [Build Working Set] on the [Project] menu and build only projects in-
cluded in the selected working set.
Build process
When you begin building a project, the
IDE
executes the processing described below.
1. Save any unsaved files in the editor.
2. Generate the following files according to the settings for project properties:
• Makefile ( <project name>
_gnu17IDE.mak
) and dependency file ( <source name>
.d
)
• Linker script file ( <project name>
_gnu17IDE.lds
)
• Parameter file ( <project name>
_gnu17IDE.par
)*
• Command file ( <project name>
_gnu17IDE.cmd
)*
* These files are needed for debugging and do not affect the build process. Normally, no command file is
generated in a build process. A build process generates a command file that includes a minimum com-
mand set required for starting up the debugger only when
<project name>
_gnu17IDE.cmd
does not
exist.
3. Execute make.exe . The following files will be generated:
• Object file for each source (
<source name>
.o
)
• Assembly file (
<C source name>
.ext0
) for each C source
• Executable format object file (
<project name>
.elf
)
• S-record-format psa file (
<project name>
.psa
)
• Link map file (
<project name>
.map
)
• Dump file (
<project name>
.dump
)
While a build process is underway, the command line in [Console] view shows each tool being executed.
Any errors occurring during a build process can be reviewed in [Problems] view. From there, you can jump the
corresponding spot in the editor in error. For more information on this feature, refer to "Jump to a line with an
error" in Section 5.5.3.
Note that make.exe is designed to generate and link only the object files (*.o) that have yet to be generated or
that require updating by checking the dependency list of the source files and object files (*.o) written in the
makefile.
Therefore, in the first build process, make.exe compiles/assembles all sources to generate object files (*.o) and
to link the generated files. Thereafter, it compiles/assembles only the altered sources (including alteration of
include files) and links the generated files.