1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Building C/C++ projects</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<h1>Building C/C++ projects</h1>
<p>The CDT relies on an external make utility, such as GNU make, to
build a project. The CDT can generate makefiles automatically when you
create a Managed Make C project or a Managed Make C++ project. You have
the option of creating a Standard Make C project or a Standard Make C++
project and providing the makefile yourself.</p>
<h2>Required utilities</h2>
<p>You must install and configure the following utilities:
</p>
<ul>
<li>Build (e.g. make).</li>
<li>Compile (e.g. gcc).</li>
<li>Debug (e.g. gdb).</li>
</ul>
<strong>Note: </strong> while make, gcc and gdb are the examples used in the
documentation, virtually any similar set of tools or utilities could be
used.
<p></p>
<p><strong>Tip: </strong>Cygwin contains these utilities (make, gcc and gdb) for
a Windows environment. While running the cygwin installation,
ensure <span class="typewriter">gcc</span> and <span class="typewriter">make</span> are selected since they are not
installed by default. For more information, see <a
href="http://www.cygwin.com">http://www.cygwin.com</a>. If you are a
Red Hat user, all that you need to do to build your project is included
in the Red Hat Linux installation.
For other operating systems, please refer to your installation
documentation.</p>
<p></p>
<h2>Build terminology</h2>
<p>The CDT uses a number of terms to describe the scope of the build. </p>
<h3>Build Project</h3>
<p>This is an incremental build (make all, assuming all is defined in
your makefile). Only the components affected by modified files in that
particular project are built.</p>
<h3>Rebuild Project</h3>
<p>Builds every file in the project whether or not a file has been
modified since the last build. A rebuild is a clean followed by a build.</p>
<p>For more information on builds, see:</p>
<ul>
<li><strong>Workbench User Guide > Concepts > Workbench > Builds</strong></li>
<li><strong>Workbench User Guide > Tasks > Building resources</strong></li>
</ul>
<p>Build-related information is displayed as follows:</p>
<ul>
<li>The Console view displays the output of the build tools.</li>
<li>The Problems view displays a list of compiler errors and warnings
related to your projects.</li>
<li>For Standard Make projects, the Makefile targets are displayed in
the Make Targets view.</li>
</ul>
<p>For more information about the Problems view, see <strong>Workbench User
Guide > Reference > User interface information > Views and
editors > Problems view</strong>.</p>
<h2>Getting a makefile</h2>
<p>You can either create a C/C++ project for which you supply the <strong>makefile</strong>
or create a C/C++ project for which the CDT generates makefiles
automatically.</p>
<p>To create a new project, from the menu bar choose <strong>File > New
> Project</strong>. In the dialog that appears, expand the C/C++ group
and choose e.g. C Project</p>
<ul>
<li>In the resulting wizard page, to create a project for which you supply the <strong>makefile</strong>,
select <strong>Makefile project</strong> and choose one of the alternatives under that.
An empty project, or a simple "Hello World" can be created.
You edit and manage the makefile yourself.
<p> </p>
</li>
<li>To create a project for which the CDT supplies a basic <strong>makefile</strong>,
select another project type, e.g. <strong>Executable</strong> and choose one of the examples
under that, or choose <strong>Empty Project</strong>.
</li>
</ul>
<h2>Setting build preferences</h2>
<p>You can set build preferences in Eclipse:</p>
<dl>
<dt>Build order</dt>
<dd>If certain projects must be built before others, you can set the <em>build
order</em>. If your project refers to another project, the CDT must
build the other project first. To set the build order, from the menu
bar select <strong>Window > Preferences</strong> and choose <strong> General > Preferences > Build Order</strong>.
<p>When you set the build order, the CDT does not rebuild projects
that depend on a project; you must rebuild all projects to ensure all
changes are propagated.</p>
</dd>
<dt>Automatic save</dt>
<dd>You can set the CDT to perform an <em>automatic save</em> of all
modified resources when you perform a manual build. In the preferences dialog,
select <strong>General > Workspace</strong> and check <strong>Save automatically before build</strong>.
By default,
this feature is <em>not</em> enabled.</dd>
</dl>
<h2>Controlling the building of your project</h2>
<p>For a Makefile project, the C/C++ compiler that a project uses
is controlled by the project's <strong>Properties</strong> setting.
To view a project's properties, right-click on the project and select <strong>Properties</strong>.
In the dialog that appears, the <strong>C/C++ Build</strong>
page enables you to control a variety of settings, including:</p>
<dl>
<dt>Build Command</dt>
<dd>On the <strong>Builder Settings</strong> tab, this controls which <code>make</code> is used. To change it, uncheck <strong>Use
default build command</strong> and change it or add arguments to the make command.</dd>
<dt>Build Setting</dt>
<dd>On the <strong>Behaviour</strong> tab, this controls whether the compiler will <strong>Stop on first build error</strong> or not
(keep going). Unchecking <strong>Stop on first build error</strong> will force the compiler to attempt to build all referenced
projects even if the current project has errors.</dd>
<dt>Workbench Build Behavior</dt>
<dd>On the <strong>Behaviour </strong> tab, this controls which makefile target will be built depending on the scope of the
build, e.g. <code>all</code> or <code>clean</code>.</dd>
</dl>
<p>For a standard (non-Makefile) project (often called "Managed Build" or "Managed Make" project from
earlier CDT version), the project properties dialog enables
you to manage the build configurations of your project. For additional
information see:</p>
<ul>
<li><strong>Reference > C/C++ Properties > C/C++ Project Properties > Managed Make
Projects</strong></li>
<li><strong>Reference > C/C++ Properties > C/C++ Project Properties > Managed Make File
Properties</strong></li>
</ul>
<h2>Viewing build information</h2>
<p>Build-related information is displayed as follows: </p>
<ul>
<li>The <strong>Console</strong> view displays the output of the make utility.</li>
<li>The <strong>Problems</strong> view displays a list of compiler errors and
warnings related to your projects. </li>
<li>For a Standard Make project, build actions display in the <strong>Make
Targets</strong> view.</li>
</ul>
<p><img border="0" src="../images/ngconcepts.gif" alt="Related concepts"
width="143" height="21">
<br>
<a href="cdt_c_projects.htm">CDT Projects</a><br>
<a href="cdt_c_proj_file_views.htm">Project file views</a></p>
<p><img border="0" src="../images/ngtasks.gif" alt="Related tasks"
width="143" height="21">
<br>
<a href="../tasks/cdt_o_build_task.htm">Building projects</a></p>
<p><img border="0" src="../images/ngref.gif" alt="Related reference"
width="143" height="21">
<br>
<a href="../reference/cdt_u_properties.htm">Project Properties</a></p>
<p><img src="../images/rh03_04.gif" alt="Red Hat Copyright Statement"><br>
<img src="../images/ng00_04a.gif" alt="IBM Copyright Statement">
</p>
</body>
</html>
|
