# HG changeset patch # User timkelly # Date 1287073644 18000 # Node ID ac14826aa14b0104e1b930c6d9a668cb37fc23cc # Parent 90c82caa691853793c3e4482c99e4747fddbc170# Parent 76029713f5704fbf7d9a7d2637ab8943c65ac254 merge commit diff -r 90c82caa6918 -r ac14826aa14b core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm Thu Oct 14 11:26:55 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm Thu Oct 14 11:27:24 2010 -0500 @@ -15,7 +15,7 @@
One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view. See Attaching to a Process for more details.
+One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you don't know which process to attach to or start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view. See Attaching to a Process for more details.
The Carbide.c++ > Build page in the Preferences window provides global preferences to control general build options like clean, test components, dependency tracking, concurrent build jobs, build behavior, and emulator options.
+NOTE Based on which SDKs the project uses, one or both of the SBSvX tabs are shown.
Figure 1 - Build workspace preferences page
The following options are available in both the global Build preference panel and the project Properties > Carbide.c++ > Project Settings panel.
diff -r 90c82caa6918 -r ac14826aa14b core/com.nokia.carbide.cpp.doc.user/html/tasks/images/new_proj_step2.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/images/new_proj_step2.png has changed diff -r 90c82caa6918 -r ac14826aa14b core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_to_process.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_to_process.htm Thu Oct 14 11:26:55 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_to_process.htm Thu Oct 14 11:27:24 2010 -0500 @@ -9,11 +9,10 @@Use a Symbian Attach to Process launch configuration to attach the debugger to an already running Symbian process or thread on a target device. This is useful for debugging DLLs where the main process is unknown or for servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate.
-One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view.
+Use a Symbian Attach to Process launch configuration to attach the debugger to an already running Symbian process or thread on a target device or simulator. This is useful for debugging DLLs where the main process is unknown or for servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate. +One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view.
You can also attach to a process in the Symbian Data view when debugging.
-NOTE You cannot attach to a process running on the emulator. It must be a target device running the Symbian and the CODA software.
+NOTE You cannot attach to a process running on an emulator. It must be a target device or simulator running the Symbian and the CODA software.
When attempting to find a process the debugger uses the UID3 to locate the process.
Use the Build Configuration Filtering preference panel in the Preferences window to select which platforms are visible when creating new projects or build configurations.
+NOTE Based on which SDKs the project uses, one or both of the SBSvX tabs are shown.
Use the SBSv2 tab to select configurations for the build system. SBSv2 is the prefered build system for the most current SDKs.
The SBSv2 configurations and variants available on this page represent the pool of all available configurations for discovered Symbian SDKs. Not all configurations apply to all SDKs; Carbide will filter configurations appropriate for each SDK in the SDK/Configuration tree selection.
diff -r 90c82caa6918 -r ac14826aa14b core/com.nokia.carbide.cpp/plugin.properties --- a/core/com.nokia.carbide.cpp/plugin.properties Thu Oct 14 11:26:55 2010 -0500 +++ b/core/com.nokia.carbide.cpp/plugin.properties Thu Oct 14 11:27:24 2010 -0500 @@ -6,7 +6,7 @@ CHEAT_SHEETS = Cheat Sheets CHEAT_SHEETS_MENU = &Cheat Sheets... -productBlurb=\nCarbide.c++ Version 3.0.0\n\ +productBlurb=\nCarbide.c++ Version 3.1.0\n\ Build {0} {1}\n\n\n\ Copyright (c) 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.\n\ Visit http://developer.symbian.org/\n\ diff -r 90c82caa6918 -r ac14826aa14b core/com.nokia.carbide.cpp/plugin.xml --- a/core/com.nokia.carbide.cpp/plugin.xml Thu Oct 14 11:26:55 2010 -0500 +++ b/core/com.nokia.carbide.cpp/plugin.xml Thu Oct 14 11:27:24 2010 -0500 @@ -34,7 +34,7 @@