Carbide.c++ updated to v1.2.2

Keywords:

carbide.jpgForum Nokia has just released an update of Carbide.c++. The new version 1.2.2 is a maintenance release with no real new features but several bugfixes. Only a few minutes are required to do the full update. Here are detailed instructions....

Update Instructions


Updating to Carbide.c++ 1.2.2 can be done directly from the IDE if you use Carbide.c++ 1.2 (either the 1.2 or 1.2.1 version). User of Carbide.c++ 1.0 or 1.1 must migrate to Carbide.c++ 1.2 (and thus need to uninstall their version and download and install the full v1.2 package, see also Forum Nokia Wiki).

For user of Carbide.c++ 1.2: first open the Help menu then Software Updates and Find and Install:

CarbideUpdate1.png

This should open up the Install/Update window shown below. At this point, I advise you to select Search for new features to install, then press Next:

CarbideUpdate2.png

Another window pops-up with the list of update server that are configured in your installation (the list ay be slightly different than mine). Just select the Carbide.c++ Update Site and select Finish:

CarbideUpdate3.png

Carbide.c++ will connect to the update server and after a few seconds will display the list of available updates. Just select all of them and continue:

CarbideUpdate4.png

The updates will now be downloaded and installed automatically. You will see a few warning about unsigned package that are to be installed. You must accept them all. Once this is completed, Carbide.c++ will restart and the new version is now ready for use. Happy coding!

Change log


IDE


  • 2421 - Changing the SDK ID no longer creates a second entry in the devices.xml file
  • 2562 - The UIQ version of TRK now correctly updates information in the UI
  • 3855 - Breakpoints are no longer reached once they are removed.
  • 4032 - Errors are now correctly removed from the Errors view when the source line containing the error is deleted
  • 4056 - A new option for Freeze Symbian Component has been added that freezes only the selected MMP file and not the entire project
  • 4075 - The internal error "Computing hasChildren" should no longer occur due to a float reference type being incorrectly treated as a pointer type
  • 4106 - You can now import a bld.inf that does not reference any MMP or MAK files
  • 4115 - Fixed problem where certain resource errors like "label not found" were treated as warnings in the problems view
  • 4118 - The CDT macros __EXE__ and __DLL__ are now correctly added to the command line when there is only one MMP file in the bld.inf for a given build config, or if there are multiple MMP files but they all have the same target type macro. Otherwise, nothing is added
  • 4119 - Fixed an issue where Carbide would close when an array out of bounds error occurred
  • 4140 - Corrected a deadlock issue that could cause Carbide to hang on startup
  • 4147 - Copying text from a source editor and pasting it into an external editor like Word, will no longer copy and paste the background color as well
  • 4165 - Using "Open File" on a BAT file now correctly opens the file in an editor instead of executing it
  • 4168 - The default project root directory is now correctly calculated for prj_exports and prj_testexport source paths, just like the bld.inf, mmp, make, source and include paths
  • 4196 - Fixed an issue that caused a NullPointerException when creating emulator launch configuration that did not contain a TARGET in the MMP file
  • 4197 - Fixed an issue that could cause the PI Function tab to hang when zooming to the entire selection
  • 4198 - Source files in imported executables can now be mapped to new locations
  • 4200 - Carbide now respects the clean andreallyclean settings when "Clean Project" is chosen
  • 4410 - Freezing exports no longer passes the "-r" flag to abld with EKA1 kits

Debugger


  • 3855 - Breakpoints are no longer reached once they are removed
  • 4075 - The internal error "Computing hasChildren" should no longer occur due to a float reference type being incorrectly treated as a pointer type
  • 4198 - Source files in imported executables can now be mapped to new locations

Performance Investigator


  • 4197 - Fixed an issue that could cause the PI Function tab to hang when zooming to the entire selection
  • 4206 - Corrected a syntax reading error in OBY files that incorrectly resolved the ROFS path and prevented analysis of binaries and functions
  • 4333 - Contextual menus now correctly appear as inactive when tables in the Function Calls tab are blank
  • 4335 - Selecting an empty time period now correctly clears all tables in the Function Calls tab
  • 4336 - Closing an error dialog will no longer cause an exception after attempting to open a source file for the selected function


Re: Carbide.c++ updated to v1.2.2

The instructions here seem to be slightly at odds with those posted by MikeT on the FN Forum at http://discussion.forum.nokia.com/forum/showthread.php?t=113303 where he suggests using Search for updates of the currently install features instead of searching for new features.

Also, in the Release Notes posted there I found a warning about not updating the CDT feature. Does this mean unchecking the Eclipse C/C++ Development Tools 3.9.11.5 option?

Re: Carbide.c++ updated to v1.2.2

The problem I found with the Search for updates of the currently installed features is that it doesn't ask you the update server you want to interrogate. And thus, you can finish upgrading with modules from the standard Eclipse branch and not from the Carbide.c++ branch.

Upgrading to Eclipse C/C++ Development Tools 3.9.11.5 should be safe as it comes from Nokia server, not standard Eclipse one. (At least I have upgraded like described above this morning and I don't think that I have broken anything so far!).

Re: Carbide.c++ updated to v1.2.2

I have to laugh, if you goto the Help|Carbide.c++ release notes command there is a big red text block saying "WARNING: Updating the CDT feature in Carbide.c++/Eclipse will wipe out our changes making the tools unusable"

So I for one declined to update the CDT

Re: Carbide.c++ updated to v1.2.2

That is definitely true if you update the CDT from the Eclipse Project Updates (I know, I experienced it!).
I doubt this is true if you update it from the Carbide.c++ update site as this one delivers the changes from Nokia. This worked like a charm for me, it did not break my workspace nor anything so far (but I am in a coding day, so I did not check for the emulator, otd, or ui designer).

Re: Carbide.c++ updated to v1.2.2

In fact, it now seems to me that you need to check the Eclipse C/C++ Development Tools 3.9.11.5 from Nokia's server, because otherwise I am getting an error saying "An error occurred while automatically activating bundle com.nokia.cdt.debug.launch (358)" in the Error Log while starting up, as well as a whole host of follow-up errors, and the Debug button no longer works.

So right now I am a bit confused about the CDT warning in the Release Notes...

Re: Carbide.c++ updated to v1.2.2

Lately its a little scary to even update small patches which dont make any major changes, knowing that there is every possibility that in the middle of development and coding, you could break down something and then end up hanging for quite sometime wasting precious time.
All said and done, it was pretty safe to just update from the Carbide.c++ update site like described by eric!! Thanks