equal
deleted
inserted
replaced
29 <tr valign="top"> |
29 <tr valign="top"> |
30 <td class="Cell"><b>Symbian SDK's</b></td> |
30 <td class="Cell"><b>Symbian SDK's</b></td> |
31 <td class="Cell"><p>Lists all the installed and recognized SDKs that are supported by the IDE. SDKs no longer supported by Carbide are not shown. You can double-click the <b>SDK ID</b> or <b>Location</b> entry to edit them directly.</p> |
31 <td class="Cell"><p>Lists all the installed and recognized SDKs that are supported by the IDE. SDKs no longer supported by Carbide are not shown. You can double-click the <b>SDK ID</b> or <b>Location</b> entry to edit them directly.</p> |
32 <p>Checked SDKs indicate build configurations available for creating projects. Unchecked SDKs are not displayed when creating new projects. </p> |
32 <p>Checked SDKs indicate build configurations available for creating projects. Unchecked SDKs are not displayed when creating new projects. </p> |
33 <p>SDKs shown in <span class="style2">RED</span> indicate a problem, usually no <span class="code">EPOCROOT</span> or unsupported Symbian OS version. </p> |
33 <p>SDKs shown in <span class="style2">RED</span> indicate a problem, usually no <span class="code">EPOCROOT</span> or unsupported Symbian OS version. </p> |
34 <p>If you see a <span class="code style3">BAD_SDK_ROOT</span> error message in the Location column, it indicates you have a bad build configuration. To correct this you must remove the bad configurations from all the projects in your current workspace. Once that is done, you can delete or redirect the SDK or point it to the correct one.</p> |
34 <p>If you see a <span class="style3">BAD_SDK_ROOT</span> error message in the Location column, it indicates you have a build configuration with an SDK ID unknown to Carbide. To correct this you can either 1) remove the bad configurations from all the projects in your current workspace or 2) fix the location with the proper path and rescan your SDKs. If you delete an SDK with <span class="code">BAD_SDK_ROOT</span> before removing it's configuration the SDK will continue to appear in the Symbian SDKs until the configurations are fixed or removed.</p> |
35 <p>Click on a SDK name to see its <span class="code">EPOCROOT</span> location and build configuration status in the SDK Information area. </p> </td> |
35 <p>Click on a SDK name to see its <span class="code">EPOCROOT</span> location and build configuration status in the SDK Information area. </p> </td> |
36 </tr> |
36 </tr> |
37 <tr valign="top"> |
37 <tr valign="top"> |
38 <td class="Cell"><b>Add </b></td> |
38 <td class="Cell"><b>Add </b></td> |
39 <td class="Cell"><p>Click to <a href="../tasks/sdks/sdk_add.htm">add</a> an SDK to the <b>Symbian SDKs</b> list.</p></td> |
39 <td class="Cell"><p>Click to <a href="../tasks/sdks/sdk_add.htm">add</a> an SDK to the <b>Symbian SDKs</b> list.</p></td> |
42 <td class="Cell"><b>Delete </b></td> |
42 <td class="Cell"><b>Delete </b></td> |
43 <td class="Cell">Click to remove the selected SDK from the <b>Symbian SDKs</b> list. </td> |
43 <td class="Cell">Click to remove the selected SDK from the <b>Symbian SDKs</b> list. </td> |
44 </tr> |
44 </tr> |
45 <tr valign="top"> |
45 <tr valign="top"> |
46 <td class="Cell"><b>Properties</b></td> |
46 <td class="Cell"><b>Properties</b></td> |
47 <td class="Cell"><p>Click to view and edit the <a href="../tasks/sdks/sdk_view_properties.htm">properties</a> of the currently selected SDK in the <b>Symbian SDKs</b> list.</p> </td> |
47 <td class="Cell"><p>Click to <a href="../tasks/sdks/sdk_view_properties.htm">view</a> the OS version of the currently selected SDK in the <b>Symbian SDKs</b> list. If the OS version cannot be determined, it will default to 9.5.</p> </td> |
48 </tr> |
48 </tr> |
49 <tr valign="top"> |
49 <tr valign="top"> |
50 <td class="Cell"><b>Scan for installable features in SDKs</b></td> |
50 <td class="Cell"><b>Scan for installable features in SDKs</b></td> |
51 <td class="Cell">Controls whether Carbide dynamically discovers and installs features from SDKs during startup and SDK rescanning. Disable to not perform this scan of SDKs. It is on by default.</td> |
51 <td class="Cell">Controls whether Carbide dynamically discovers and installs features from SDKs during startup and SDK rescanning. Disable to not perform this scan of SDKs. It is on by default.</td> |
52 </tr> |
52 </tr> |
53 <tr valign="top"> |
53 <tr valign="top"> |
54 <td class="Cell"><p><b>Rescan All SDKs</b></p> </td> |
54 <td class="Cell"><p><b>Rescan All SDKs</b></p> </td> |
55 <td class="Cell"><p>Click to <a href="../tasks/sdks/sdk_search.htm">rescan</a> the drive for newly installed SDKs. </p> |
55 <td class="Cell"><p>Click to <a href="../tasks/sdks/sdk_search.htm">rescan</a> the drive for newly installed SDKs. </p> |
56 <p class="note"><b>NOTE</b> Carbide.c++ scans for available SDKs each time it is started.</p></td> |
56 <p>Carbide scans system drives for installed SDKs at startup or during a forced rescan, adding any detected Symbian SDKs automatically. Automatically added SDKs have IDs of "<span class="code"><drive spec>_SDK</span>". You many edit the SDK ID if you don't like the name that Carbide has chosen.</p></td> |
57 </tr> |
57 </tr> |
58 </table> |
58 </table> |
59 <h5>Related tasks</h5> |
59 <h5>Related tasks</h5> |
60 <ul> |
60 <ul> |
61 |
61 |