|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (4) » Build tools (5) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (9) » Carbide.c++ 2.0.x (12) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (25) » General (48) » Off-topic (5) » On-device debugging (13) » Performance Investigator (2) » Product features (18) » Product releases (16) » Screencast (14) » Support (36) » Tool setup (6) » UI Designer (8) » Usability (18) » Work in Progress (14) » Write-build-debug (4) |
|
» New Remote Connections View » Terminating Multiple Processes » Agile Tuning of the Austin Team » Introduction to the workspace screencast » Adding DLLs while Debugging |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Introducing Bugzilla for Carbide | Main | De-peeving On-device Debugging »
We just noticed a glitch in the S60 3rd FP2 SDK: The capability definition files are out of date. The consequence is that if you run the capability scanner against this SDK is will likely miss most of your capabilities and report that you don't need any.
Luckily the solution is easy: Just delete the 'capabilities' folder and contents under:
Then run the scanner again. Carbide contains the most recent capability definitions for all the S60 3rd SDK editions to date so when they aren't in the SDK, Carbide will use the ones installed in the IDE.
Tim