38 <h3><a name="whatsNew" id="whatsNew"></a>What's New in 2.6.0 </h3> |
38 <h3><a name="whatsNew" id="whatsNew"></a>What's New in 2.6.0 </h3> |
39 <p>The following features for Symbian development are provided within Carbide.c++:</p> |
39 <p>The following features for Symbian development are provided within Carbide.c++:</p> |
40 <ul> |
40 <ul> |
41 <li><b>GCCE 4.0 </b> supported — required for future SBSv2 releases.</li> |
41 <li><b>GCCE 4.0 </b> supported — required for future SBSv2 releases.</li> |
42 <li><b>Symbian^3 </b>supported — new templates and improvements required for the public Symbian^3 SDK.</li> |
42 <li><b>Symbian^3 </b>supported — new templates and improvements required for the public Symbian^3 SDK.</li> |
43 <li><b>SBSv2 variants </b> supported — you can now both build and debug SBSv2 variants.</li> |
43 <li><b>Known Issues in v2.6.0</b>: |
|
44 <ul> |
|
45 <li>GCCE4 support requires using a SBSv2 build alias (<span class="code">-c</span> parameter) of <span class="code">armv5_udeb_gcce</span> or <span class="code">armv5_urel_gcce</span>. As of this writing, these aliases were not available in the SDK or SBSv2, but will appear in some future version. Carbide versions prior to 2.6 do not support GCCE4.</li> |
|
46 <li>Users should consult the SDK documentation for GCCE and SBSv2 issues and installation requirements.</li> |
|
47 <li>TRK: If you install the TRK app onto your phone's flash memory (Mass Storage) a Remote Connection may not find the TRK-service even though TRK is already connected to your PC. Workaround: Uninstall TRK then reinstall it onto your PHONE memory (C-drive). The TRK service should now be "Available".</li> |
|
48 </ul> |
|
49 </li> |
44 </ul> |
50 </ul> |
45 <h4><a name="new250" id="new"></a>2.5.0</h4> |
51 <h4><a name="new250" id="new"></a>2.5.0</h4> |
46 <ul> |
52 <ul> |
47 <li><b>Plug-and-Play (PnP) On-device Debugging </b> supported — debugging a target device just got easier. Using a USB cable, connect the PC to the target device, then launch Carbide.c++. Carbide locates the connected device and creates a remote connection setup to communicate with it. Build the program and launch it on the device to start the debugging session. Refer to <a href="#pnpIssues">Known PnP Issues</a> for details if you experience problems.</li> |
53 <li><b>Plug-and-Play (PnP) On-device Debugging </b> supported — debugging a target device just got easier. Using a USB cable, connect the PC to the target device, then launch Carbide.c++. Carbide locates the connected device and creates a remote connection setup to communicate with it. Build the program and launch it on the device to start the debugging session. Refer to <a href="#pnpIssues">Known PnP Issues</a> for details if you experience problems.</li> |
48 <li><b>PnP Phone Launch Wizard</b> - If the project does not already have a launch configuration, the PnP Launch Wizard makes it easy to create one for <a href="projects/launch/launch_phone.htm">phones</a>. In addition the new <a href="projects/launch/wnd_config_launch_config.htm">Configure Launch Configuration</a> dialog provides a quick summary of the remote connection for easy review and modification.</li> |
54 <li><b>PnP Phone Launch Wizard</b> - If the project does not already have a launch configuration, the PnP Launch Wizard makes it easy to create one for <a href="projects/launch/launch_phone.htm">phones</a>. In addition the new <a href="projects/launch/wnd_config_launch_config.htm">Configure Launch Configuration</a> dialog provides a quick summary of the remote connection for easy review and modification.</li> |