7 <title>External Builds Support</title> |
7 <title>External Builds Support</title> |
8 <link rel="StyleSheet" href="../../book.css" type="text/css"/> |
8 <link rel="StyleSheet" href="../../book.css" type="text/css"/> |
9 </head> |
9 </head> |
10 <body bgcolor="#FFFFFF"> |
10 <body bgcolor="#FFFFFF"> |
11 <h2>External Builds Support</h2> |
11 <h2>External Builds Support</h2> |
12 <p> The IDE will perform the following tasks on external makefiles:</p> |
12 <p> The Carbide IDE performs the following tasks on external makefiles:</p> |
13 <ul> |
13 <ul> |
14 <li>Build</li> |
14 <li>Build</li> |
15 <li>Debug</li> |
15 <li>Debug</li> |
16 <li>File Management in Project Manager window</li> |
16 <li>File Management in Project Manager window</li> |
17 <li>Source Browsing</li> |
17 <li>Source Browsing</li> |
18 <li>Error Lookup</li> |
18 <li>Error Lookup</li> |
19 </ul> |
19 </ul> |
20 <p>The IDE can build an external makefile and debug its output. A linker plugin will enable the IDE to manage a command line and targets associated with a makefile. The command line is executed when a build step is initiated. The linker plugin will also supply the executable to use for debugging.</p> |
20 <p>Carbide can build an external makefile and debug its output. A linker plugin enables Carbide to manage a command line and targets associated with a makefile. The command line is executed when a build step is initiated. The linker plugin will also supply the executable to use for debugging.</p> |
21 <p>The linker plugin will provide a preference panel named External Build that is used to configure a target. The preference panel provides text fields for you to configure the command line for the target (which will enable building), specify the working directory and the output file used to launch a debugging session, and the debug platform.</p> |
21 <p>The linker plugin provides a preference panel named <strong>External Build</strong> that is used to configure a target. The preference panel provides text fields for you to configure the command line for the target (which will enable building), specify the working directory and the output file used to launch a debugging session, and the debug platform.</p> |
22 <p>The linker plugin is generic so that it can be used regardless of the target CPU and OS. The list of available debugger preference panels will be updated by the IDE when you select the debug platform.</p> |
22 <p>The linker plugin is generic so that it can be used regardless of the target CPU and OS. The list of available debugger preference panels will be updated by the IDE when you select the debug platform.</p> |
23 <p>The External Build Target preference panel will collect the following information:</p> |
23 <p>The <strong>External Build Target</strong> preference panel collects the following information:</p> |
24 <ul> |
24 <ul> |
25 <li>Build command line to be executed in the build step</li> |
25 <li>Build command line to be executed in the build step</li> |
26 </ul> |
26 </ul> |
27 <blockquote> |
27 <blockquote> |
28 <p>The command line will be sent to the OS shell and will contain all parameters and/or switches that are necessary for proper building of the make file.</p> |
28 <p>The command line will be sent to the OS shell and will contain all parameters and/or switches that are necessary for proper building of the make file.</p> |
36 <p>After the IDE converts the makefile into a Carbide project, source files can be added in the project manager window. Files that appear in the project manager will be parsed by the language parser and will supply Source Browsing information, such as code completion.</p> |
36 <p>After the IDE converts the makefile into a Carbide project, source files can be added in the project manager window. Files that appear in the project manager will be parsed by the language parser and will supply Source Browsing information, such as code completion.</p> |
37 <p>When a build step is initiated, the linker plugin will gather output after the command line begins executing. Output is directed to the IDE and displayed in a read-only Build Output Window. A build output window is displayed for each target. The build output window can be displayed manually by selecting the menu command View > Build Output (Windows) or Window > Build Output (Linux/Solaris/Mac). This command is enabled for targets that use the external build linker.</p> |
37 <p>When a build step is initiated, the linker plugin will gather output after the command line begins executing. Output is directed to the IDE and displayed in a read-only Build Output Window. A build output window is displayed for each target. The build output window can be displayed manually by selecting the menu command View > Build Output (Windows) or Window > Build Output (Linux/Solaris/Mac). This command is enabled for targets that use the external build linker.</p> |
38 <p>If multiple build steps are performed on the same target, the output from each build step will be appended to the build output window. Each block of output will be separated by “----Build started----” and “----Done----” tags.</p> |
38 <p>If multiple build steps are performed on the same target, the output from each build step will be appended to the build output window. Each block of output will be separated by “----Build started----” and “----Done----” tags.</p> |
39 <p>The build output window will allow users to navigate directly to the location of a compilation error. Double-click a line that contains an error message or press Enter when the cursor is in the line. If the IDE determines that a valid error message exists on the selected line, the source file is opened to the line on which the error occurred.</p> |
39 <p>The build output window will allow users to navigate directly to the location of a compilation error. Double-click a line that contains an error message or press Enter when the cursor is in the line. If the IDE determines that a valid error message exists on the selected line, the source file is opened to the line on which the error occurred.</p> |
40 <p>Click the right mouse button in the build output window to display a context menu.</p> |
40 <p>Click the right mouse button in the build output window to display a context menu.</p> |
|
41 <ul> |
|
42 <li>The <strong>Copy</strong> command copies selected text to the clipboard. If no text is selected then the line that contains the cursor is copied.</li> |
|
43 <li>The <strong>Clear All</strong> command clears the contents of output window.</li> |
|
44 <li>The <strong>Go To Error</strong> command navigates to the error location. This is identical to double-clicking.</li> |
|
45 </ul> |
41 </blockquote> |
46 </blockquote> |
42 <ul> |
|
43 <li>The Copy command will copy selected text to the clipboard. If no text is selected then the line that contains the cursor will be copied.</li> |
|
44 <li>The Clear All command will clear contents of output window.</li> |
|
45 <li>The Go To Error command will navigate to the error location. This is identical to double-clicking.</li> |
|
46 </ul> |
|
47 <div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div> |
47 <div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div> |
48 |
48 |
49 </body> |
49 </body> |
50 </html> |
50 </html> |