|
» 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 (10) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (24) » General (47) » Off-topic (4) » On-device debugging (13) » Performance Investigator (2) » Product features (18) » Product releases (16) » Screencast (13) » Support (35) » Tool setup (6) » UI Designer (8) » Usability (17) » Work in Progress (14) » Write-build-debug (4) |
|
» Adding DLLs while Debugging » Executables » Regular Expressions Help » License for v2.0 M1 downloads » View Memory on Variables |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Code Navigation tips illustrated! | Main | Austin Eclipse DemoCamp »
In Carbide 1.3.1 we revamped the wording and internal code for the generation of console output. Mainly this was done to unify the option's wording and make it easy identify which console program and error output was sent to. Remember, the Console view has several default pages associated with it.
However, an additional step was overlooked in the Carbide manual, the editing of the epoc.ini file, which must be made for a couple of these options to work. Here's how to correct that.
The options I'm speaking of are seen in Symbian OS Emulation launch configurations on the Debugger page. Look there and you'll see these options:
All well and good so far. However, to really make these work you also need to set a couple of options in your SDKs epoc.ini file you are using. Locate and open the epoc.ini file, then set the following options:
Save the changes.
Finally, verify that you have Carbide.c++ Build 36 installed by checking the Help > About Carbide.c++ dialog. If you have an earlier 1.3.1 build, click Help > Software Updates > Find and Install... to grab the latest build from the Carbide.c++ Update Site. The next time you want to view the above mentioned console pages you'll see the output you expect.
Comments
Thanks. Sadly, today, spent searching for this information, is a day of my life I will never get back.... :-(
Posted by: gummibear | August 27, 2008 06:34 PMSorry to hear it was so hard to find. It is in the v2.0M1 version of the manual now. One of my hopes was that placing this information on the blog would make it more easily found via a Google search.
Posted by: L. Frank Turovich | August 28, 2008 10:21 AM