|
» 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) |
|
» Getting started screencast.. » Version Control and Carbide » Screencast: On-device debugging with Carbide.c++ 1.1 » CodeWarrior on-device debugging screencast » C++ tutorial templates |
|
Subscribe to RSS feed For email notification, please click here ยป |
Since some customers have encountered problems in setting up the build environment for Carbide.c++, we created a screencast to demonstrate this process:
You can find this and other videos at: http://wiki.forum.nokia.com/index.php/Carbide_Training_Videos
Got ideas for screencasts you'd like to see? Leave us some feedback here and we'll get on it!
Without doubt, besides the eclipse editor, the Team features (version control) are the most often used features in my daily development grind. Given that, I am doing mostly java development these days writing Carbide plugins and test suites. For java development, version control is pretty straight forward. It's not quite so simple for Carbide development, but it can be done with just a little more effort. So at the risk of over simplifying or generalizing I'll give you a couple of ways of working with version controls systems and some things to look out for. I can't speak for all version control systems (we use CVS) but I think once you get version control going under an eclipse environment you'll wonder how you lived without it.
After some initial troubles, a screencast about how to do on-device debugging with Carbide.c++ is available on Forum Nokia. As always, let me know what you think, and what is missing.
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!
Previously C++ project tutorials (that ship with the SDK or are available on Forum Nokia) have consisted of a separate doc and zip file containing the project that required you to import the MMP and open the instructions in a PDF reader. In order to make learning about S60 a little easier, one of our developers is investigating a more convenient way of accessing programming examples, to be delivered in v1.2 (or 1.1 if we're lucky). Take a look...
