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
August 01, 2008 That's a little too large Posted by L. Frank Turovich at 11:51 AM | Categories:

One of the known problems when debugging programs on a device is simply the amount of time one spends waiting for things to happen. You have to wait for a build to complete, you have to wait for the program to be downloaded to the device, then wait for it to start, then wait for it to hit a breakpoint so you can actually begin debugging. And if the program is large, whew, does it take awhile to download.

Well, we can't solve all of these issues but if you routinely download large SIS/SISX files to devices to debug, we may have a solution for you.

In Carbide 2.0M1 we've added support for the Symbian partial upgrade feature. This is a flag (PU) that tells the compiler to build an abbreviated SIS/SISX file based only upon the sources that have changed since the last build. These sources are compiled into their own little patch file and stored alongside the full SIS file. If the SIS file is stored in the project, the patch SIS file is stored along with it in the Project Explorer view. If the SIS file is stored in a directory outside the project, the patch SIS file is also stored there and a link added to the project in the Project Explorer view pointing to it.

Carbide actually builds both the full SIS file and the patch SIS file to keep both in sync, but then only downloads the patch SIS file to the device.

properties_pu.jpg

How do you know if you should use it or not? Well, to begin, a dialog appears that informs you of this new feature if the SIS file being downloaded exceeds 250k in size. If points you to the SIS Builder tab in the project's Properties dialog where you simply enable the Partial upgrade checkbox for the files that should have patch files created.

After you've done that, simple resume your normal debugging activities as before and enjoy the reduced download time of your project.


Permalink |


Post a comment







«Back to previous page