|
2
|
1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
|
2 |
<html>
|
|
|
3 |
<head>
|
|
|
4 |
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
|
|
|
5 |
<meta http-equiv="Content-Style-Type" content="text/css" />
|
|
|
6 |
<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
|
|
|
7 |
<title>Adding Symbian Custom Kits</title>
|
|
|
8 |
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
|
|
|
9 |
</head>
|
|
|
10 |
<body bgcolor="#FFFFFF">
|
|
|
11 |
<h2>Adding Symbian Custom Kits</h2>
|
|
|
12 |
<p>The <span class="note">Carbide.c++ Developer Edition</span> and higher level products includes functionality to work with Symbian CustKits or any arbitrary SDK source base. This enables you to work with evolving SDKs as they are released. </p>
|
|
|
13 |
<p class="note"><b>NOTE</b> The features that enable build support with CustKits are only available for Carbide.c++ Developer Edition and higher level products. </p>
|
|
|
14 |
<ul>
|
|
|
15 |
<li><b>Adding a CustKit without a devices.xml entry</b></li>
|
|
|
16 |
Use the <b>Add SDK</b> dialog to <a href="sdk_add.htm">add</a> an SDK entry for the CustKit that you want to use with the project. You may want to add a Symbian source base that Carbide.c++ can recognize if you do not plan to build from the command line. Once you've added the CustKit, you can now import projects against the newly added SDK.
|
|
|
17 |
<li><b>Mapping a CustKit</b><b> SDK to a known SDK release <br />
|
|
|
18 |
<br />
|
|
|
19 |
</b>Use the <a href="sdk_view_properties.htm">SDK Properties</a> window to map an unrecognized SDK (S60_3rd_Ed_FP2) to a known version of a similar SDK (S60_3rd_Ed) . This should enable you to import projects against the CustKit SDK. </li>
|
|
|
20 |
</ul>
|
|
|
21 |
<p align="center"><img src="images/sdk_info_errors_shown.png" width="373" height="192"></p>
|
|
|
22 |
<p align="center" class="figure">Figure 1 - SDK Information group showing SDK errors </p>
|
|
|
23 |
<blockquote>
|
|
|
24 |
<p>Some issues to look for in the SDK Properties dialog include:
|
|
|
25 |
</p>
|
|
|
26 |
</blockquote>
|
|
|
27 |
<ul>
|
|
|
28 |
<ul>
|
|
|
29 |
<li><b>SDK Name</b> — templates and UI designs may not display if the name used is not a known default (e.g. com.nokia.s60) as defined under the SDK properties</li>
|
|
|
30 |
<li><b>OS version</b> — ensure the correct OS version is assigned to the CustKit tells Carbide what platforms the SDK supports </li>
|
|
|
31 |
<li><b>SDK version</b> — used to filter which template projects and/or UI Designer projects are available and the UI components displayed </li>
|
|
|
32 |
</ul>
|
|
|
33 |
</ul>
|
|
|
34 |
<h5>Related concepts</h5>
|
|
|
35 |
<ul>
|
|
|
36 |
<li><a href="../../concepts/SDKSupport.html">SDK Support </a></li>
|
|
|
37 |
</ul>
|
|
|
38 |
<h5>Related tasks </h5>
|
|
|
39 |
<ul>
|
|
|
40 |
<li><a href="sdk_search.htm">Searching SDKs</a></li>
|
|
|
41 |
<li><a href="sdk_view_properties.htm">View SDK Properties</a> </li>
|
|
|
42 |
</ul>
|
|
|
43 |
<h5>Related references </h5>
|
|
|
44 |
<ul>
|
|
|
45 |
<li><a href="../../reference/SDKPreferences.html">SDK Preferences Panel</a></li>
|
|
|
46 |
</ul>
|
|
|
47 |
<div id="footer">Copyright © 2009 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 |
|
|
|
49 |
</body>
|
|
|
50 |
</html> |