[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [dsdp-mtj-dev] Questions about S60 3rd Ed. FP1 SDK support
- From: Gorkem Ercan <gercan@xxxxxxx>
- Date: Thu, 28 May 2009 15:50:18 +0300
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=ro57v8mFtJH2cUeT9L4t/9D2oWtwz6LY/gOYp7Lhkv/be8duPGh0gMyt8A0ijGoWuS TE6Nn816lhgW0igdNDkMbMSDAo9YQKFrF5cIbJlkmhMATFQ+Z83Y1xWsF/vBGHS7iPG7 K4VfvBZSDmtoQDn1Yoek4y+oyDRD9zeYXZM8U=
The change on the MTJ code basically enables UEIDeviceImporter to import an SDK that does not report a CLDC API. The problem stems from the workaround to avoid importing SDKs that supports CDC. So the fix is isolated to removing the workaround. As a side note, I am not sure, why we want to avoid importing CDC compatible SDKs actually. It is true that current MTJ does not offer CDC compatible tooling but someone may just want to provide that on top of it.
Once the SDK is imported everything seems to work fine. There are a few places where the CLDC API info is used but on those places it just falls back to CLDC 1.0.