43 <li>Click the Build (<img src="../images/icon_build_project.png" alt="Build Project icon" width="17" height="17" align="absmiddle">) icon in the toolbar to build the project.</li> |
43 <li>Click the Build (<img src="../images/icon_build_project.png" alt="Build Project icon" width="17" height="17" align="absmiddle">) icon in the toolbar to build the project.</li> |
44 </ul> |
44 </ul> |
45 </li> |
45 </li> |
46 </ol> |
46 </ol> |
47 <blockquote> |
47 <blockquote> |
48 <p>Choosing any of the above actions causes Carbide to build the selected project. A <strong>Build Project</strong> dialog (below) and a progress bar appear during a lengthy build operation. All build output is shown in a <a href="../../reference/view_log.htm">Console</a> view while build errors and warnings appear in the Problems view.</p> |
48 <p>Choosing any of the above actions causes Carbide to build the selected project. A <strong>Build Project</strong> dialog (below) and a progress bar appear during a lengthy build operation. All build output is shown in a <a href="../../reference/view_console.htm">Console</a> view while build errors and warnings appear in the Problems view.</p> |
49 <p align="left"><img src="../images/dlg_build_project_progress.png" alt="Build Project progress dialog" width="532" height="233"></p> |
49 <p align="left"><img src="../images/dlg_build_project_progress.png" alt="Build Project progress dialog" width="532" height="233"></p> |
50 <p>Whether a full build or incremental build is requested, Carbide forwards the request to the SDK make system. The SDK make system determines if anything needs to be |
50 <p>Whether a full build or incremental build is requested, Carbide forwards the request to the SDK make system. The SDK make system determines if anything needs to be |
51 built. Carbide always checks that makefiles are up-to-date and |
51 built. Carbide always checks that makefiles are up-to-date and |
52 dependencies present.</p> |
52 dependencies present.</p> |
53 <p>The project is also built if you make a change to it and then click <b>Debug</b>. It may be useful to automatically save modified resources before a manual build process by enabling the <b>Save automatically before build</b> option in the <b>Window > Preferences > General ></b> <img src="../../images/command_link.png" width="16" height="12"> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'> Workspace</a> preference panel. </p> |
53 <p>The project is also built if you make a change to it and then click <b>Debug</b>. It may be useful to automatically save modified resources before a manual build process by enabling the <b>Save automatically before build</b> option in the <b>Window > Preferences > General ></b> <img src="../../images/command_link.png" width="16" height="12"> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'> Workspace</a> preference panel. </p> |
54 <p class="note"><b>NOTE</b> If you want to turn off building before launching, uncheck the <b>Build (if required) before launching</b> option in the <b>Window > Preferences > Run/Debug ><img src="../../images/command_link.png" width="16" height="12"> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> Launching</a></b> preference panel.</p> |
54 <p class="note"><b>NOTE</b> If you want to turn off building before launching, uncheck the <b>Build (if required) before launching</b> option in the <b>Window > Preferences > Run/Debug ><img src="../../images/command_link.png" width="16" height="12"> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> Launching</a></b> preference panel.</p> |
55 <p>When performing a build, output is displayed in the <a href="../../reference/view_log.htm">Console</a> view. If you do not want to clear the console before each build you need to uncheck the option <b>Always clear console before building</b> in the <b> Console</b> panel. This option is enabled by default. You can access this panel by selecting <b>Window > Preferences > C/C++ > Build ><img src="../../images/command_link.png" width="16" height="12"> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.ui.preferneces.CBuildConsolePreferernces)")'> Console</a></b> preference panel (below).</p> |
55 <p>When performing a build, output is displayed in the <a href="../../reference/view_console.htm">Console</a> view. If you do not want to clear the console before each build you need to uncheck the option <b>Always clear console before building</b> in the <b> Console</b> panel. This option is enabled by default. You can access this panel by selecting <b>Window > Preferences > C/C++ > Build ><img src="../../images/command_link.png" width="16" height="12"> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.ui.preferneces.CBuildConsolePreferernces)")'> Console</a></b> preference panel (below).</p> |
56 <p align="left"><img src="../images/pref_cdt_build_console.png" alt="Console preference panel" width="635" height="554"></p> |
56 <p align="left"><img src="../images/pref_cdt_build_console.png" alt="Console preference panel" width="635" height="554"></p> |
57 <p>Not clearing the console is useful when you are performing multiple builds, such as a regular project build, building a project package (.pkg) file, and building a ROM image. For example, if you do not clear the console before each build, then a subsequent build will not overwrite information from a previous build.</p> |
57 <p>Not clearing the console is useful when you are performing multiple builds, such as a regular project build, building a project package (.pkg) file, and building a ROM image. For example, if you do not clear the console before each build, then a subsequent build will not overwrite information from a previous build.</p> |
58 </blockquote> |
58 </blockquote> |
59 <ol start="2"> |
59 <ol start="2"> |
60 <li>Verifying a successful project build <br /> |
60 <li>Verifying a successful project build <br /> |
71 <li>Check the Problems view for error or warning messages<br /> |
71 <li>Check the Problems view for error or warning messages<br /> |
72 <p>Examine the <a href="PLUGINS_ROOT//org.eclipse.cdt.doc.user/reference/cdt_u_problems_view.htm">Problems</a> view to see what errors and warning messages were generated during the build. The Description column contains additional information about the problem that can help you resolve it.</p> |
72 <p>Examine the <a href="PLUGINS_ROOT//org.eclipse.cdt.doc.user/reference/cdt_u_problems_view.htm">Problems</a> view to see what errors and warning messages were generated during the build. The Description column contains additional information about the problem that can help you resolve it.</p> |
73 <p><img src="../images/new_build_project_problems_view.png" alt="Executables view" width="797" height="210"></p> |
73 <p><img src="../images/new_build_project_problems_view.png" alt="Executables view" width="797" height="210"></p> |
74 </li> |
74 </li> |
75 <li>Examine the Console view for more specific details on an error or warning message<br /> |
75 <li>Examine the Console view for more specific details on an error or warning message<br /> |
76 <p>Use the <a href="../../reference/view_log.htm">Console</a> view to see where a specific problem occured during the build.</p> |
76 <p>Use the <a href="../../reference/view_console.htm">Console</a> view to see where a specific problem occured during the build.</p> |
77 <p><img src="../images/new_build_project_console_view.png" alt="Executables view" width="797" height="210"></p> |
77 <p><img src="../images/new_build_project_console_view.png" alt="Executables view" width="797" height="210"></p> |
78 </li> |
78 </li> |
79 <li>Examine the Executables view for missing source files<br /> |
79 <li>Examine the Executables view for missing source files<br /> |
80 <p>Use the <a href="../../reference/view_executables.htm">Executables</a> view to see what source files were used during the build. Sources shown in gray are those Carbide cannot find. Missing sources in an SDK not built on your machine are common, but missing sources that you created can be resolved.</p> |
80 <p>Use the <a href="../../reference/view_executables.htm">Executables</a> view to see what source files were used during the build. Sources shown in gray are those Carbide cannot find. Missing sources in an SDK not built on your machine are common, but missing sources that you created can be resolved.</p> |
81 <p><img src="../images/new_build_project_executables_view.png" alt="Executables view" width="713" height="210"></p> |
81 <p><img src="../images/new_build_project_executables_view.png" alt="Executables view" width="713" height="210"></p> |