Old School: Legacy SDKs and Carbide
Carbide C++
- August 6th, 2008
I know there are people out there developing for somewhat elderly devices, and I still get regular questions from users who download Carbide.c++ v1.3 and are unpleasantly surprised when they try to write the ultimate Series 60 2nd Edition application and Carbide refuses to oblige.
To accommodate folks using older kits, we have put Carbide.c++ v1.2 back up for download. It can be found here.
Note that no active development is being done on Carbide v1.2; we simply provide it as a service to people who need it to develop for older kits.
As far as i know, support for S60 2nd edition SDKs is still there in Carbide.c++ 1.3. It is just not set as “ON” by default, hence it is not available in new project wizard. Through some hacks, one can turn it on to work with S60 2nd edition SDKs in Carbide.c++ 1.3.
My question is, then what is the significance of “not” providing S60 2nd edition SDKs support by-default in Carbide.c++ 1.3?
Thanks,
Kiran.
> My question is, then what is the significance of “not” providing S60 2nd edition SDKs support
> by-default in Carbide.c++ 1.3?
Basically, it means we did no testing to ensure compatibility with older kits and provide no guarantees that it will work. If anyone reports problems using Carbide v1.3 or newer with unsupported kits our answer will be that they need to use v1.2 for development with those kits, since that is the last version that went through a full test cycle with legacy SDKs.
Thanks for the reply Matt. I got the point now.
Kiran.