|
» 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 (8) » Carbide.c++ 2.0.x (1) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (24) » General (46) » Off-topic (4) » On-device debugging (13) » Performance Investigator (2) » Product features (16) » Product releases (16) » Screencast (12) » Support (30) » Tool setup (5) » UI Designer (8) » Usability (15) » Work in Progress (13) » Write-build-debug (4) |
|
» CodeWarrior on-device debugging screencast » Migrating from CodeWarrior to Carbide.c++ Q&A |
|
Subscribe to RSS feed For email notification, please click here ยป |
For all you CodeWarrior users working on S60 v3.0 apps, here's an advance copy of a screencast on how to configure CodeWarrior for on-device debugging of released/publically available S60 v3.0 phones (e.g., E70, E80, etc). The screencast isn't available via Forum Nokia just yet, but should be there in the next few days. Remember, you saw it here first! :-)
To get started, download the screencast and an updated version of the on-device debug agent (AppTRK v2.6) from below. Apologies for the .exe format; an AVI update is in the works.
A couple of things to note before you start... The screencast is missing a few tidbits of information that will make the setup easier. If you're importing your app, make sure the "Use SIS Installation Process (TRK debugging only)" option is checked...
Alternatively, if you've already imported your app into CodeWarrior, go to your target preferences, select Debugger --> Symbian TRK Debugging and check "Use SIS Installation Process".
![]()
That should do it. Let me know if it worked!
As we prepare to release Carbide.c++ v1.1, now is a good time to go over some questions that have been popping up in various forums. There'll be an official FAQ posted on this topic, but I figured I could cover some relevant questions right away. Let me know if something is not covered.
Continue reading "Migrating from CodeWarrior to Carbide.c++ Q&A" »