## Adding Symbian Custom Kits

The Carbide.c++ Developer Edition 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.

NOTE The features that enable build support with CustKits are only available for Carbide.c++ Developer Edition and higher level products.

- Adding a CustKit without a devices.xml entry
Use the Add SDK dialog to add 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.
- Mapping a CustKit SDK to a known SDK release
  Use the SDK Properties 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.

Figure 1 - SDK Information group showing SDK errors

> Some issues to look for in the SDK Properties dialog include:

- SDK Name — 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
- OS version — ensure the correct OS version is assigned to the CustKit tells Carbide what platforms the SDK supports
- SDK version — used to filter which template projects and/or UI Designer projects are available and the UI components displayed

##### Related references

- Working with SDKs