|
|
Classification: |
C++ |
Category: |
SDK |
Created: |
04/15/2005 |
Modified: |
04/29/2005 |
Number: |
FAQ-1263 |
Platform: |
Not Applicable |
|
Question: Why isn't the new device I added using devices.exe listed in the dialog when I try to 'Import Project From .mmp File' in Code
Warrior? Code Warrior 'Import Project From .mmp File' doesn't allow me to import to one of the other installed SDKs. Why not?
Answer: The devices.exe tool allows you to manually add more devices (see FAQ-1112) as follows:> devices -add C:\symbian\newsdk C:\symbian\newsdk @newsdk:com.nokia.sdk
The devices.exe command does not mandate the format of the SDK name; however, the recommended practice is to adhere to the
below syntax. The kit id and names have no direct mapping to the SDK, except for coupling the SDK with the correct root (EPOCROOT)
directory; hence, any string can be used to set the kit id and the names.
:..
Code Warrior expects the above format when listing the devices in the above option. It uses the format to group different
SDKs by vendor name. If you add a new device using devices.exe without conforming to the above syntax, e.g.,
> devices -add C:\symbian\newsdk C:\symbian\newsdk @newsdk:mynewsdk.com
it will render the Code Warrior 'Import Project From .mmp File' option unuseable (it only takes one non-conformant device name to do this). The following behaviour will be experienced:
- some of the SDKs are not listed
- although you can select the listed SDKs, the 'Next' button cannot be pressed to do the import (it is greyed out).
Remove and re-add the device using devices.exe or Code Warrior with the correct syntax. Note that if the 'faulty' device has
the same 'kit id' as another valid device, Code Warrior will remove the first instance of the device - thus, potentially removing
the valid device. The Symbian Developer Library contains more information about devices.exe. See Developer Library » Tools and Utilities » Kit management
|
|
|