# HG changeset patch # User fturovic # Date 1283313489 18000 # Node ID 4f0cd256d26c23b7a844201055b6c0e9b6ddadb6 # Parent a77f12f0a6315b96c720de671066f475a6a8a84b BUG 11531 - fixed reported issues from Rooney and Stephen for SDK section diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm Tue Aug 31 22:58:09 2010 -0500 @@ -15,11 +15,11 @@
  • The debugger will target any executable not already started whenever a "process load" event occurs, resolving its breakpoints as well.

    • Debugging DLLs

    -

    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 OS 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 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.

    Other References
    diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/html/concepts/build_targets.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/build_targets.htm Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/build_targets.htm Tue Aug 31 22:58:09 2010 -0500 @@ -15,7 +15,7 @@

    Supported Target Types

    Carbide.c++ supports a variety of build targets based upon the SDKs and which version of the Carbide tools used by the project. The table below identifies which build targets are possible for a specific SDK.

    -

    NOTE Check the SDK Preferences page to see if an SDK you have installed and whether its build configurations are supported.

    +

    NOTE Check the SDK Preferences page to see if an SDK you have installed and whether its build configurations are supported.

    Table 1. Supported target types for all versions of Carbide.c++
    @@ -61,7 +61,6 @@
    Related tasks
    diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/registers.htm Tue Aug 31 22:58:09 2010 -0500 @@ -43,8 +43,7 @@ diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/html/concepts/tour.html --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/tour.html Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/tour.html Tue Aug 31 22:58:09 2010 -0500 @@ -52,32 +52,19 @@

  • - Add scalable graphics (MIF) and Symbian OS bitmaps (MBM) to projects, and edit these resources. You can add these using the New command, which is available on the File menu, and on the pop-up menus of the Project Explorer and Symbian Project Navigator views. MBM and MIF editors are provided to modify + Add scalable graphics (MIF) and Symbian OS bitmaps (MBM) to projects, and edit these resources. You can add these using the New command, which is available on the File menu, and on the pop-up menus of the Project Explorer and Symbian Project Navigator views. MBM and MIF editors are provided to modify the resources.

    For more information, see Creating an MBM File.

    • -
  • -

    - Build programs for multiple SDKs and targets. The standard CDT build - commands such as Build Project and Build All Configurations, - which are available in the Project menu, are used.

    -

    +

  • +

    + Build programs for multiple SDKs and targets. The standard CDT build commands such as Build Project and Build All Configurations, + which are available in the Project menu, are used.

    +

    For more information, see Building Projects.

    • - - - - - - diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_debugger.htm Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_debugger.htm Tue Aug 31 22:58:09 2010 -0500 @@ -21,8 +21,8 @@
  • Restarting the debugger
    • -
  • Variable information in the Variables view—see the variables in the executing code, their values, and their types
    • -
  • Breakpoint information in the Breakpoints view—see the breakpoints, conditional breakpoints, and breakpoint actions
    • +
  • Variable information in the Variables view—see the variables in the executing code, their values, and their types
    • +
  • Breakpoint information in the Breakpoints view—see the breakpoints, conditional breakpoints, and breakpoint actions
  • Source code—see the source code under debugger control
    • Related concepts
    diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/working_with_programs.htm Tue Aug 31 22:58:09 2010 -0500 @@ -12,7 +12,7 @@

    This section explains how to use breakpoints, breakpoint actions, and watchpoints to manipulate execution of your program in the Carbide™ IDE:

    Related references

    Follow the steps to successfully create the HelloCarbide program and debug it on the S60 Emulator.

    -

    NOTE There must be at least one recognized SDK installed before you can create a project. See the Symbian SDKs panel to determine if the installed SDKs are recognized by Carbide.c++ IDE. If the SDK you have installed is not recognized, you may still be able to add it to the Discovered Symbian OS SDK list.

    +

    NOTE There must be at least one recognized SDK installed before you can create a project. See the Symbian SDKs panel to determine if the installed SDKs are recognized by Carbide.c++ IDE. If the SDK you have installed is not recognized, you may still be able to add it to the Discovered Symbian OS SDK list.

    diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm Tue Aug 31 22:58:09 2010 -0500 @@ -13,7 +13,7 @@

    This example shows how to create and build an application and debug it on a device using the Application TRK on-device debug agent. Click this link to the HelloCarbide cheatsheet that provides links to detailed steps. The majority of steps are identical to the ones used to create a program and debug in an emulator, with some minor variations.

    See the Run Mode Debug Example for a walkthrough of the following steps which include:

      -
    1. Verify that your SDK or customer kit is recognized in the Symbian SDKs panel.
      2. +
    2. Verify that your SDK or customer kit is recognized in the Symbian SDKs panel.
    3. Create a project by importing a Bld.inf
    4. Verify that all the symbolics for the binaries are visible in the Executables view
    5. Manage the project's PKG file, being sure to: diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm Tue Aug 31 22:58:09 2010 -0500 @@ -25,7 +25,7 @@

      An SDK or OS developer kit (DevKit) including:

      • 9.x or higher for Platform Security
      -

      Targets: Symbian ^3, S60 5th Ed., Qt

      +

      Targets: Symbian ^3, Symbian ^4, Nokia Qt SDK, S60 5th Ed.

      Debugger: Emulators, on-device debugging

      diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/index.xml --- a/core/com.nokia.carbide.cpp.doc.user/index.xml Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/index.xml Tue Aug 31 22:58:09 2010 -0500 @@ -104,8 +104,8 @@ - - + + @@ -571,7 +571,6 @@ - @@ -585,7 +584,6 @@ - diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/intro/carbide.css --- a/core/com.nokia.carbide.cpp.doc.user/intro/carbide.css Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/intro/carbide.css Tue Aug 31 22:58:09 2010 -0500 @@ -1,21 +1,21 @@ - -a#carbide img { background-image : url(images/carbide.png); } -a#carbide:hover img { background-image : url(images/carbide_hov.png); } - -a#carbide-whatsnew img { background-image : url(images/carbide_new.png); } -a#carbide-whatsnew :hover img { background-image : url(images/carbide_new_hov.png); } - -a#carbide-sample img { background-image : url(images/carbide_sample.png); } -a#carbide-sample:hover img { background-image : url(../images/carbide_sample_hov.png); } - -a#carbide-tutorial img { background-image : url(images/carbide_tutorial.png); } -a#carbide-tutorial:hover img { background-image : url(images/carbide_tutorial_hov.png); } - -a#carbide-keys img { background-image : url(images/carbide_keys.png); } -a#carbide-keys:hover img { background-image : url(images/carbide_keys_hov.png); } - -a#carbide-web img { background-image : url(images/carbide_web.png); } -a#carbide-web:hover img { background-image : url(images/carbide_web_hov.png); } - -a#carbide-people img { background-image : url(images/carbide_people.png); } -a#carbide-people:hover img { background-image : url(images/carbide_people_hov.png); } + +a#carbide img { background-image : url(images/carbide.png); } +a#carbide:hover img { background-image : url(images/carbide_hov.png); } + +a#carbide-whatsnew img { background-image : url(images/carbide_new.png); } +a#carbide-whatsnew :hover img { background-image : url(images/carbide_new_hov.png); } + +a#carbide-sample img { background-image : url(images/carbide_sample.png); } +a#carbide-sample:hover img { background-image : url(images/carbide_sample_hov.png); } + +a#carbide-tutorial img { background-image : url(images/carbide_tutorial.png); } +a#carbide-tutorial:hover img { background-image : url(images/carbide_tutorial_hov.png); } + +a#carbide-keys img { background-image : url(images/carbide_keys.png); } +a#carbide-keys:hover img { background-image : url(images/carbide_keys_hov.png); } + +a#carbide-web img { background-image : url(images/carbide_web.png); } +a#carbide-web:hover img { background-image : url(images/carbide_web_hov.png); } + +a#carbide-people img { background-image : url(images/carbide_people.png); } +a#carbide-people:hover img { background-image : url(images/carbide_people_hov.png); } diff -r a77f12f0a631 -r 4f0cd256d26c core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml --- a/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Aug 31 16:18:02 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Aug 31 22:58:09 2010 -0500 @@ -107,7 +107,6 @@ - @@ -117,13 +116,10 @@ - - - + + - - @@ -133,7 +129,7 @@ - + @@ -143,8 +139,8 @@ - - + +