## SDK Preferences

Use the SDK Preferences page in the Preferences window to control which installed SDKs are available to projects during an import. To access SDK preferences preference panel, select Window > Preferences > Carbide.c++ > SDK Preferences.

NOTE There must be at least one recognized SDK installed before you can create a project. If the SDK you have installed is not recognized, you may still be able to add it to the Discovered Symbian OS SDK list. See Carbide.c++ Requirements for a list of supported SDKs.

NOTE This panel serves as a devices.xml file editor. The devices.xml file stores information about the installed SDKs used for Symbian OS development.

Figure 1. SDK Preferences preference panel

Name | Function
--- | ---
Available Symbian OS SDK's | Lists all the installed and recognized SDKs supported by the IDE. Only SDKs supported by the IDE are included in the list. Checked SDKs indicate build configurations available for creating projects. Unchecked SDKs are not displayed when creating new projects. SDKs shown in red indicate a problem, usually no EPOCROOT or missing build configurations. Click on a SDK name to see its EPOCROOT location and build configuration status in the SDK Information area.
Add New SDK | Click to add an SDK to the Available Symbian OS SDKs list.
Remove SDK | Click to remove the selected SDK from the Available Symbian OS SDK's list.
SDK Properties | Click to view and edit the properties of the currently selected SDK in the Available Symbian OS SDKs list.
Listen for devices.xml changes outside of Carbide | Enable of have Carbide issue an alert prompting you to rescan your SDKs when changes to the devices.xml file are made outside of Carbide. When disabled the devices.xml file is not scanned for changes.
Rescan All SDKs | Click to rescan the drive for newly installed SDKs. The devices.xml file is scanned for SDKs and the list of available SDKs is updated if the devices.xml file has changed. NOTE Carbide.c++ scans for available SDKs each time it is started.

### Legacy SDK's

For legacy SDK's the OS/SDK version is determined from the SDK id. Some older SDK's have two verisons, one where the emulator was built with MSVC and the other built with CodeWarrior. We support those SDK's built with CodeWarrior. The id of that SDK is S60_2nd_FP2_CW.

##### Related concepts

- SDK Support

##### Related tasks

- Working with SDKs
- Adding an SDK
- SDK Properties