See into S60
» 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)
» Tommi's Reports from Wonderland
» Voice of S60
» Creating Carbide C++
» S60 Multimedia Blog
» The Convergence Zone
» Web Browser for S60 Blog
» Consumed by S60
» Java for S60
» Mobile Web Server
» Mobile Security
» See into S60
» Business2GO
» Nokia Podcasting Application Blog
» New Remote Connections View
» Terminating Multiple Processes
» Agile Tuning of the Austin Team
» Introduction to the workspace screencast
» Adding DLLs while Debugging
» September 2008
» August 2008
» July 2008
» June 2008
» May 2008
» April 2008
» March 2008
» February 2008
» August 2007
» May 2007
» April 2007
» March 2007
» February 2007
» January 2007
» December 2006
» November 2006
» October 2006
» September 2006
» August 2006
» July 2006
» June 2006
Subscribe
Links
April 25, 2007 RELEASED: Carbide.c++ 1.2 Posted by Markus Ahonen at 09:54 PM | Categories: Carbide.c++ 1.2, FAQ, General, Product features, Product releases

Read the press release...

It took longer than expected, but I think you'll agree that it was good of us to take our time: Carbide.c++ 1.2 is now ready and available for download.

Let me share with you the key features about this release. It introduces new features that ease Symbian development; but it also improves on a set of existing features that I think you'll find make your job easier.

(All) Build system - in many ways, the Symbian build system is a source of a lot of tooling problems for us, so for 1.1 we introduced a managed make -type system that was supposed to allow for better overall flexibility. However, the build system didn't provide us with the quick responsiveness a tool needs in order to address new reference designs as they become available, so we went back to the drawing board and implemented a build system that takes a very different approach: It simply calls into the command line tools. Although this brings some new issues, the result as a whole is an order of magnitude faster (think 10x for complex projects), and we offer a few new features as well - single file build, abld target to name a few. Oh, and importing is faster -- in fact, the more complex the project, the bigger the improvement.

(All) MMP editor - possibly the best-liked new feature by our beta group, the MMP editor provides a visual interface to the MMP file, as well as direct access to the file. It makes operations less error-prone, yet gives you full flexibility to customize the MMP. See the MMP Editor screencast for more information.

(All) Code browsing & navigation - Eclipse's C++ Development Tools project (CDT) gives us all our C/C++ specific features that we can't live without. Carbide.c++ 1.1 was based on 3.1, and as the product project went on, it turned out that we could fix a lot of long-standing bugs by migrating to CDT MS5 release, which mostly contained fixes to e.g. the indexer, which has been a thorn in the side of CDT for a while. What we didn't count on was the success of the code browsing and navigation features that came with the update. If there ever was a stealth feature that ended up being a success, this would be it.

(PRO) Power consumption analysis - Newer Nokia phones support power tracing. Install thethe Performance Investigator, run your favorite use case, and then view the CPU and power consumption profile for the use case. A "jump to source" feature means you can now jump to the line of code that was being executed at a given point in time -- so finding the code resulting in power drain is easier than ever.

(OEM) Stop-mode debugging - Those familiar with CodeWarrior OEM Edition know that an IDE is a great thing to have when working with reference hardware -- but configuring an in-circuit emulator can be tedious. With the help of Eclipse launch configurations (customized to work with Carbide.c++ & Lauterbach / Sophia ICEs), connecting to a TI H4 or an OEM wingboard is easy stuff.

(OEM) Crash debugger view - Another easier-to-use feature: If your phone has crashed, you can now dial into the crash debugger, and view the system state in the actual debugger view - no need to scroll through a long text file. ´

+ last but not least - Carbide.c++ Plug-in SDK - Time will tell the value of this one - but I expect this to be a long-term success. The plug-in SDK allows other developers to write custom tools that use APIs we've exposed in our build system and elsewhere in the tool. Tool extension writers like Macrobug will probably make good use of it. Perhaps you can, too?

Aside from the new features, we also worked hard to fix bugs. We had an awesome beta group and with their assistance and enthusiasm, were able to improve on critical areas to make the product that much better.

I'll post instructions on how to get your hands on the product separately.


Permalink |

Comments

Congratulations... Keep the good work.

Posted by: Antony Pranata | April 26, 2007 01:39 AM

If I understand well, in Carbide 1.2 you have to switch off emulator every time you build project even when you do NOT change resources.
It's VERY uncomfortable!! :((

Posted by: c. | May 26, 2007 05:58 AM

http://blogs.s60.com/mt/mt-comments.cgi

Posted by: farshad | June 11, 2007 12:50 AM

Is it possible to:

- Debug the project on device
- Make a simple change to a source file
- And debug the project on device again

without regenerating the makefiles?

For my project regenerating the makefiles takes 7-10 minutes, and this is done every time I make a change to a file and run the debugger by doing:

Run->Debug...
Symbian OS App TRK->My Debug Config
Debug (in lower right)

i.e. How can I get it to invoke:

C:\WINDOWS\system32\cmd.exe /c abld target ARMV5 UREL -v

instead of:

C:\WINDOWS\system32\cmd.exe /c abld build ARMV5 UREL -v

Thanks

Posted by: Michael Marcin | July 12, 2007 11:18 PM

How can I change the grouping order in "C/C++ Projects" view? I want files to group by name, not by type. Right now view groups files by type (headers/source), so all source files (sorted by name) come first and then come all headers. I want to disable grouping by name, to have MyFile.h right before MyFile.cpp.

Posted by: Dmitry | September 29, 2007 01:48 AM

Is it possible to emulate a device crash scenario on the emulator ?

Posted by: Anoop C | February 20, 2008 03:27 AM


Post a comment







«Back to previous page