diff --git a/.github/workflows/build-test.yml b/.github/workflows/build-test.yml index 98dd09712da..d24f7434279 100644 --- a/.github/workflows/build-test.yml +++ b/.github/workflows/build-test.yml @@ -47,7 +47,6 @@ jobs: clean verify -B -V \ -Dmaven.test.failure.ignore=true \ -DexcludedGroups=flakyTest,slowTest \ - -P build-standalone-debugger-rcp \ -Ddsf.gdb.tests.timeout.multiplier=50 \ -Ddsf-gdb.skip.tests=$(test ${{ steps.filter.outputs.dsf }} == 'false' && echo 'true' || echo 'false') \ -Dindexer.timeout=300 diff --git a/BUILDING.md b/BUILDING.md index 9a9a8f01703..d8b0d979080 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -38,11 +38,6 @@ Individual p2 repos can be turned on and off to allow building CDT, or parts of - test CDT against a pre-built CDT by using the cdtRepo profile. - build the standalone rcp debugger against the latest simrel `mvn verify -DuseSimrelRepo -f debug/org.eclipse.cdt.debug.application.product` -#### build-standalone-debugger-rcp - -Using the `build-standalone-debugger-rcp` profile will include the standalone debugger, located -in `debug/org.eclipse.cdt.debug.application.product` - #### skip-all-tests, skip-tests-except-cdt-ui, skip-tests-except-dsf-gdb, skip-tests-except-cdt-other Using any of the above profiles can skip large sets of tests. The CI build uses this to parallelize tests. See https://ci.eclipse.org/cdt/view/Gerrit/ diff --git a/Jenkinsfile b/Jenkinsfile index 878e1f2121b..ca99350d270 100644 --- a/Jenkinsfile +++ b/Jenkinsfile @@ -48,7 +48,6 @@ pipeline { -Ddsf.gdb.tests.timeout.multiplier=50 \ -Dindexer.timeout=300 \ -P production \ - -P build-standalone-debugger-rcp \ -Ddsf.gdb.tests.gdbPath=/shared/common/gdb/gdb-all/bin \ -Dcdt.tests.dsf.gdb.versions=gdb.10,gdbserver.10 \ -Dmaven.repo.local=/home/jenkins/.m2/repository \ diff --git a/debug/org.eclipse.cdt.debug.application.doc/.gitignore b/debug/org.eclipse.cdt.debug.application.doc/.gitignore deleted file mode 100644 index 9e440c00d03..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/.gitignore +++ /dev/null @@ -1 +0,0 @@ -/workspace/ diff --git a/debug/org.eclipse.cdt.debug.application.doc/.project b/debug/org.eclipse.cdt.debug.application.doc/.project deleted file mode 100644 index af73cd146b5..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/.project +++ /dev/null @@ -1,22 +0,0 @@ - - - org.eclipse.cdt.debug.application.doc - - - - - - org.eclipse.pde.ManifestBuilder - - - - - org.eclipse.pde.SchemaBuilder - - - - - - org.eclipse.pde.PluginNature - - diff --git a/debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.core.resources.prefs b/debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.core.resources.prefs deleted file mode 100644 index 99f26c0203a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.core.resources.prefs +++ /dev/null @@ -1,2 +0,0 @@ -eclipse.preferences.version=1 -encoding/=UTF-8 diff --git a/debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.pde.api.tools.prefs b/debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.pde.api.tools.prefs deleted file mode 100644 index ec9fbf321d0..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.pde.api.tools.prefs +++ /dev/null @@ -1,184 +0,0 @@ -ANNOTATION_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error -ANNOTATION_ELEMENT_TYPE_ADDED_FIELD=Error -ANNOTATION_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error -ANNOTATION_ELEMENT_TYPE_ADDED_INTERFACE_BOUNDS=Error -ANNOTATION_ELEMENT_TYPE_ADDED_METHOD=Error -ANNOTATION_ELEMENT_TYPE_ADDED_METHOD_WITHOUT_DEFAULT_VALUE=Error -ANNOTATION_ELEMENT_TYPE_ADDED_TYPE_MEMBER=Error -ANNOTATION_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error -ANNOTATION_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error -ANNOTATION_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error -ANNOTATION_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error -ANNOTATION_ELEMENT_TYPE_CHANGED_INTERFACE_BOUNDS=Error -ANNOTATION_ELEMENT_TYPE_CHANGED_RESTRICTIONS=Error -ANNOTATION_ELEMENT_TYPE_CHANGED_TO_CLASS=Error -ANNOTATION_ELEMENT_TYPE_CHANGED_TO_ENUM=Error -ANNOTATION_ELEMENT_TYPE_CHANGED_TO_INTERFACE=Error -ANNOTATION_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error -ANNOTATION_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error -ANNOTATION_ELEMENT_TYPE_REMOVED_FIELD=Error -ANNOTATION_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error -ANNOTATION_ELEMENT_TYPE_REMOVED_METHOD=Error -ANNOTATION_ELEMENT_TYPE_REMOVED_METHOD_WITHOUT_DEFAULT_VALUE=Error -ANNOTATION_ELEMENT_TYPE_REMOVED_METHOD_WITH_DEFAULT_VALUE=Error -ANNOTATION_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error -ANNOTATION_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error -ANNOTATION_ELEMENT_TYPE_REMOVED_TYPE_PARAMETERS=Error -API_COMPONENT_ELEMENT_TYPE_REMOVED_API_TYPE=Error -API_COMPONENT_ELEMENT_TYPE_REMOVED_REEXPORTED_API_TYPE=Error -API_COMPONENT_ELEMENT_TYPE_REMOVED_REEXPORTED_TYPE=Error -API_COMPONENT_ELEMENT_TYPE_REMOVED_TYPE=Error -API_USE_SCAN_FIELD_SEVERITY=Error -API_USE_SCAN_METHOD_SEVERITY=Error -API_USE_SCAN_TYPE_SEVERITY=Error -CLASS_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error -CLASS_ELEMENT_TYPE_ADDED_FIELD=Error -CLASS_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error -CLASS_ELEMENT_TYPE_ADDED_INTERFACE_BOUNDS=Error -CLASS_ELEMENT_TYPE_ADDED_METHOD=Error -CLASS_ELEMENT_TYPE_ADDED_RESTRICTIONS=Error -CLASS_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error -CLASS_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error -CLASS_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERCLASS_SET=Error -CLASS_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error -CLASS_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error -CLASS_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error -CLASS_ELEMENT_TYPE_CHANGED_NON_ABSTRACT_TO_ABSTRACT=Error -CLASS_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error -CLASS_ELEMENT_TYPE_CHANGED_RESTRICTIONS=Error -CLASS_ELEMENT_TYPE_CHANGED_SUPERCLASS=Error -CLASS_ELEMENT_TYPE_CHANGED_TO_ANNOTATION=Error -CLASS_ELEMENT_TYPE_CHANGED_TO_ENUM=Error -CLASS_ELEMENT_TYPE_CHANGED_TO_INTERFACE=Error -CLASS_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error -CLASS_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error -CLASS_ELEMENT_TYPE_REMOVED_CONSTRUCTOR=Error -CLASS_ELEMENT_TYPE_REMOVED_FIELD=Error -CLASS_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error -CLASS_ELEMENT_TYPE_REMOVED_INTERFACE_BOUNDS=Error -CLASS_ELEMENT_TYPE_REMOVED_METHOD=Error -CLASS_ELEMENT_TYPE_REMOVED_SUPERCLASS=Error -CLASS_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error -CLASS_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error -CLASS_ELEMENT_TYPE_REMOVED_TYPE_PARAMETERS=Error -CONSTRUCTOR_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error -CONSTRUCTOR_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error -CONSTRUCTOR_ELEMENT_TYPE_ADDED_INTERFACE_BOUNDS=Error -CONSTRUCTOR_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error -CONSTRUCTOR_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error -CONSTRUCTOR_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error -CONSTRUCTOR_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error -CONSTRUCTOR_ELEMENT_TYPE_CHANGED_NON_ABSTRACT_TO_ABSTRACT=Error -CONSTRUCTOR_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error -CONSTRUCTOR_ELEMENT_TYPE_CHANGED_NON_STATIC_TO_STATIC=Error -CONSTRUCTOR_ELEMENT_TYPE_CHANGED_STATIC_TO_NON_STATIC=Error -CONSTRUCTOR_ELEMENT_TYPE_CHANGED_TYPE_PARAMETER=Error -CONSTRUCTOR_ELEMENT_TYPE_CHANGED_VARARGS_TO_ARRAY=Error -CONSTRUCTOR_ELEMENT_TYPE_REMOVED_ANNOTATION_DEFAULT_VALUE=Error -CONSTRUCTOR_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error -CONSTRUCTOR_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error -CONSTRUCTOR_ELEMENT_TYPE_REMOVED_INTERFACE_BOUNDS=Error -CONSTRUCTOR_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error -CONSTRUCTOR_ELEMENT_TYPE_REMOVED_TYPE_PARAMETERS=Error -ENUM_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error -ENUM_ELEMENT_TYPE_CHANGED_RESTRICTIONS=Error -ENUM_ELEMENT_TYPE_CHANGED_TO_ANNOTATION=Error -ENUM_ELEMENT_TYPE_CHANGED_TO_CLASS=Error -ENUM_ELEMENT_TYPE_CHANGED_TO_INTERFACE=Error -ENUM_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error -ENUM_ELEMENT_TYPE_REMOVED_ENUM_CONSTANT=Error -ENUM_ELEMENT_TYPE_REMOVED_FIELD=Error -ENUM_ELEMENT_TYPE_REMOVED_METHOD=Error -ENUM_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error -FIELD_ELEMENT_TYPE_ADDED_VALUE=Error -FIELD_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error -FIELD_ELEMENT_TYPE_CHANGED_FINAL_TO_NON_FINAL_STATIC_CONSTANT=Error -FIELD_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error -FIELD_ELEMENT_TYPE_CHANGED_NON_STATIC_TO_STATIC=Error -FIELD_ELEMENT_TYPE_CHANGED_STATIC_TO_NON_STATIC=Error -FIELD_ELEMENT_TYPE_CHANGED_TYPE=Error -FIELD_ELEMENT_TYPE_CHANGED_VALUE=Error -FIELD_ELEMENT_TYPE_REMOVED_TYPE_ARGUMENT=Error -FIELD_ELEMENT_TYPE_REMOVED_TYPE_ARGUMENTS=Error -FIELD_ELEMENT_TYPE_REMOVED_VALUE=Error -ILLEGAL_EXTEND=Warning -ILLEGAL_IMPLEMENT=Warning -ILLEGAL_INSTANTIATE=Warning -ILLEGAL_OVERRIDE=Warning -ILLEGAL_REFERENCE=Warning -INTERFACE_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error -INTERFACE_ELEMENT_TYPE_ADDED_DEFAULT_METHOD=Error -INTERFACE_ELEMENT_TYPE_ADDED_FIELD=Error -INTERFACE_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error -INTERFACE_ELEMENT_TYPE_ADDED_INTERFACE_BOUNDS=Error -INTERFACE_ELEMENT_TYPE_ADDED_METHOD=Error -INTERFACE_ELEMENT_TYPE_ADDED_RESTRICTIONS=Error -INTERFACE_ELEMENT_TYPE_ADDED_SUPER_INTERFACE_WITH_METHODS=Error -INTERFACE_ELEMENT_TYPE_ADDED_TYPE_MEMBER=Error -INTERFACE_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error -INTERFACE_ELEMENT_TYPE_ADDED_TYPE_PARAMETERS=Error -INTERFACE_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error -INTERFACE_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error -INTERFACE_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error -INTERFACE_ELEMENT_TYPE_CHANGED_INTERFACE_BOUNDS=Error -INTERFACE_ELEMENT_TYPE_CHANGED_RESTRICTIONS=Error -INTERFACE_ELEMENT_TYPE_CHANGED_TO_ANNOTATION=Error -INTERFACE_ELEMENT_TYPE_CHANGED_TO_CLASS=Error -INTERFACE_ELEMENT_TYPE_CHANGED_TO_ENUM=Error -INTERFACE_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error -INTERFACE_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error -INTERFACE_ELEMENT_TYPE_REMOVED_FIELD=Error -INTERFACE_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error -INTERFACE_ELEMENT_TYPE_REMOVED_INTERFACE_BOUNDS=Error -INTERFACE_ELEMENT_TYPE_REMOVED_METHOD=Error -INTERFACE_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error -INTERFACE_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error -INVALID_ANNOTATION=Ignore -INVALID_JAVADOC_TAG=Error -INVALID_REFERENCE_IN_SYSTEM_LIBRARIES=Warning -LEAK_EXTEND=Warning -LEAK_FIELD_DECL=Warning -LEAK_IMPLEMENT=Warning -LEAK_METHOD_PARAM=Warning -LEAK_METHOD_RETURN_TYPE=Warning -METHOD_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error -METHOD_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error -METHOD_ELEMENT_TYPE_ADDED_INTERFACE_BOUNDS=Error -METHOD_ELEMENT_TYPE_ADDED_RESTRICTIONS=Error -METHOD_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error -METHOD_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error -METHOD_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error -METHOD_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error -METHOD_ELEMENT_TYPE_CHANGED_NON_ABSTRACT_TO_ABSTRACT=Error -METHOD_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error -METHOD_ELEMENT_TYPE_CHANGED_NON_STATIC_TO_STATIC=Error -METHOD_ELEMENT_TYPE_CHANGED_STATIC_TO_NON_STATIC=Error -METHOD_ELEMENT_TYPE_CHANGED_TYPE_PARAMETER=Error -METHOD_ELEMENT_TYPE_CHANGED_VARARGS_TO_ARRAY=Error -METHOD_ELEMENT_TYPE_REMOVED_ANNOTATION_DEFAULT_VALUE=Error -METHOD_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error -METHOD_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error -METHOD_ELEMENT_TYPE_REMOVED_INTERFACE_BOUNDS=Error -METHOD_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error -METHOD_ELEMENT_TYPE_REMOVED_TYPE_PARAMETERS=Error -MISSING_EE_DESCRIPTIONS=Warning -TYPE_PARAMETER_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error -TYPE_PARAMETER_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error -TYPE_PARAMETER_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error -TYPE_PARAMETER_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error -TYPE_PARAMETER_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error -TYPE_PARAMETER_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error -UNUSED_PROBLEM_FILTERS=Warning -automatically_removed_unused_problem_filters=false -changed_execution_env=Error -eclipse.preferences.version=1 -incompatible_api_component_version=Error -incompatible_api_component_version_include_major_without_breaking_change=Disabled -incompatible_api_component_version_include_minor_without_api_change=Disabled -incompatible_api_component_version_report_major_without_breaking_change=Warning -incompatible_api_component_version_report_minor_without_api_change=Warning -invalid_since_tag_version=Error -malformed_since_tag=Error -missing_since_tag=Error -report_api_breakage_when_major_version_incremented=Disabled -report_resolution_errors_api_component=Warning diff --git a/debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.pde.prefs b/debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.pde.prefs deleted file mode 100644 index 8142f730075..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.pde.prefs +++ /dev/null @@ -1,36 +0,0 @@ -compilers.f.unresolved-features=1 -compilers.f.unresolved-plugins=1 -compilers.incompatible-environment=1 -compilers.p.build=1 -compilers.p.build.bin.includes=1 -compilers.p.build.encodings=2 -compilers.p.build.java.compiler=2 -compilers.p.build.java.compliance=1 -compilers.p.build.missing.output=2 -compilers.p.build.output.library=1 -compilers.p.build.source.library=1 -compilers.p.build.src.includes=0 -compilers.p.deprecated=1 -compilers.p.discouraged-class=1 -compilers.p.exec-env-too-low=1 -compilers.p.internal=1 -compilers.p.missing-packages=2 -compilers.p.missing-version-export-package=2 -compilers.p.missing-version-import-package=2 -compilers.p.missing-version-require-bundle=2 -compilers.p.no-required-att=0 -compilers.p.no.automatic.module=1 -compilers.p.not-externalized-att=1 -compilers.p.service.component.without.lazyactivation=1 -compilers.p.unknown-attribute=1 -compilers.p.unknown-class=0 -compilers.p.unknown-element=1 -compilers.p.unknown-identifier=0 -compilers.p.unknown-resource=0 -compilers.p.unresolved-ex-points=0 -compilers.p.unresolved-import=0 -compilers.s.create-docs=false -compilers.s.doc-folder=doc -compilers.s.open-tags=1 -compilers.use-project=true -eclipse.preferences.version=1 diff --git a/debug/org.eclipse.cdt.debug.application.doc/META-INF/MANIFEST.MF b/debug/org.eclipse.cdt.debug.application.doc/META-INF/MANIFEST.MF deleted file mode 100644 index d835b16335b..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/META-INF/MANIFEST.MF +++ /dev/null @@ -1,7 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %bundleName -Bundle-SymbolicName: org.eclipse.cdt.debug.application.doc;singleton:=true -Bundle-Version: 11.6.0.qualifier -Bundle-Vendor: %provider -Bundle-Localization: plugin diff --git a/debug/org.eclipse.cdt.debug.application.doc/about.html b/debug/org.eclipse.cdt.debug.application.doc/about.html deleted file mode 100644 index b3134865230..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/about.html +++ /dev/null @@ -1,38 +0,0 @@ - - - - - - About - - - -

About This Content

- -

November 30, 2017

-

License

- -

- The Eclipse Foundation makes available all content in this plug-in - ("Content"). Unless otherwise indicated below, the Content - is provided to you under the terms and conditions of the Eclipse - Public License Version 2.0 ("EPL"). A copy of the EPL is - available at https://www.eclipse.org/legal/epl-2.0. - For purposes of the EPL, "Program" will mean the Content. -

- -

- If you did not receive this Content directly from the Eclipse - Foundation, the Content is being redistributed by another party - ("Redistributor") and different terms and conditions may - apply to your use of any object code in the Content. Check the - Redistributor's license that was provided with the Content. If no such - license exists, contact the Redistributor. Unless otherwise indicated - below, the terms and conditions of the EPL still apply to any source - code in the Content and such source code may be obtained at https://www.eclipse.org. -

- - - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/book.css b/debug/org.eclipse.cdt.debug.application.doc/book.css deleted file mode 100644 index cb69589fb20..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/book.css +++ /dev/null @@ -1,61 +0,0 @@ -/* following font face declarations need to be removed for DBCS */ - - -body, h1, h2, h3, h4, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-family: Arial, sans-serif; color: #000000} -pre { font-family: Courier, monospace} - -/* end font face declarations */ - -/* following font size declarations should be OK for DBCS */ -body, h1, h2, h3, h4, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-size: 12pt; } -pre { font-size: 12pt} - -/* end font size declarations */ - -body { background: #FFFFFF} -h1 { font-size: 18pt; margin-top: 5; margin-bottom: 1 } -h2 { font-size: 14pt; margin-top: 25; margin-bottom: 3 } -h3 { font-size: 12pt; margin-top: 20; margin-bottom: 3 } -h4 { font-size: 10pt; margin-top: 20; margin-bottom: 3; font-style: italic } -p { font-size: 12pt; } -pre { margin-left: 6; font-size: 9pt } - -a:link { color: #006699 } -a:visited { color: #996699 } -a:hover { color: #006699 } - -ul { margin-top: 0; margin-bottom: 10 } -li { margin-top: 0; margin-bottom: 0 } -li p { margin-top: 0; margin-bottom: 0 } -ol { margin-top: 0; margin-bottom: 10 } -dl { margin-top: 0; margin-bottom: 10 } -dt { margin-top: 0; margin-bottom: 0; font-weight: bold } -dd { margin-top: 0; margin-bottom: 0 } -strong { font-weight: bold} -em { font-style: italic} -var { font-style: italic} -div.revision { border-left-style: solid; border-left-width: thin; - border-left-color: #7B68EE; padding-left:5 } -th { font-weight: bold } - -.title { - font-size: 20px; font-weight: bold; -} - - -/* Mike Behm's addition to the style sheet */ -.userinput { font-family: monospace; } -.guitab, .important, .guibutton, .selectblue, .guimenu, .guilabel, -.notetitle { - color: #000000; - font-family: helvetica, arial, sans-serif; - font-weight: bold; - } -div.linux {display:none;} -.firsterm {font-style:italic;} - -.typewriter {font-family:monospace;} -.bold {font-weight:600;} -.linethrough {text-decoration: line-through;} -.underline {text-decoration: underline;} - diff --git a/debug/org.eclipse.cdt.debug.application.doc/build.properties b/debug/org.eclipse.cdt.debug.application.doc/build.properties deleted file mode 100644 index d49611525ef..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/build.properties +++ /dev/null @@ -1,15 +0,0 @@ -bin.includes = plugin.xml,\ - META-INF/,\ - html/,\ - images/,\ - reference/,\ - concepts/,\ - book.css,\ - notices.html,\ - tasks/,\ - about.html,\ - testToc.xml,\ - toc.xml,\ - index/,\ - plugin.properties -src.includes = about.html diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_before_you_begin.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_before_you_begin.htm deleted file mode 100644 index ceedc3ac684..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_before_you_begin.htm +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - - Before you begin - - - -
-

Before you begin

- -

Depending on how you obtained the Stand-alone Debugger, you might have also received -a toolchain. -However, if you downloaded the Stand-alone Debugger from the Eclipse web site, then you will require a toolchain before -you can debug any projects.

- -

The Stand-alone Debugger uses plug-ins from the CDT (C/C++ Development Tools) project pertaining to -debugging an application. These CDT debugging components require some GNU toolchain elements such as -the gdb debugger and gcc compiler. The Stand-alone Debugger does allow editing files but does not support rebuilding -a project; a user can do that outside of the Stand-alone Debugger either either from the command line or using -the full CDT IDE which supports edit/compile/build/debug. - -

Each platform that runs the Stand-alone Debugger requires different steps to acquire the GNU toolchain.

- -

Windows

-

For windows, MinGW and Cygwin are the two main platform choices for acquiring the GNU toolchain. -It is important to understand the difference between them. -Cygwin produces executables that use the Cygwin POSIX runtime. Note that this runtime is GPL licensed. -MinGW produces native Windows executables that do not require a separate runtime.

- - - -

Linux

-

All Linux distributions include the GNU toolchain. They may not, however, be installed by default. -For instructions about installing the GNU toolchain for Linux, see the instructions for your particular distribution.

- -

Mac OS X

-The Stand-alone Debugger supports the Apple GNU toolchain that is included in with the Xcode IDE. It can be downloaded -from the Apple's developer site, https://developer.apple.com - -

Other Platforms

-

The GNU toolchain is supported on all platforms that the Stand-alone Debugger supports. For instructions about installing the GNU toolchain -on your platform, see your platform vendor.

- -

QNX Copyright Statement -

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_brkpnts.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_brkpnts.htm deleted file mode 100644 index c2cae29339e..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_brkpnts.htm +++ /dev/null @@ -1,63 +0,0 @@ - - - - - - -Breakpoints - - - - -
-

Breakpoints

- -

A breakpoint suspends the execution of a program at the location where the breakpoint is set. -To set a line breakpoint, right-click in the marker bar area on the left side of an editor beside -the line where you want the program to be suspended, then choose Toggle Breakpoint. You can -also double-click on the marker bar next to the source code line. A new breakpoint marker appears -on the marker bar, directly to the left of the line where you added the breakpoint. Also, the new -breakpoint appears in the Breakpoints view list. -

-

Once set, a breakpoint can be enabled and disabled by right-clicking on its icon or by -right-clicking on its description in the Breakpoints view. -

- - - - - -

Note: Execution will also suspend -if Stop at main() on startup is enabled -on the Launch Configuration dialog. -To access the Launch Configuration dialog, -from the menu bar choose Run > Debug. -

- -
- -

Related reference -
-Run menu
-Breakpoints view -

- -

-Red Hat Statement
-IBM Copyright Statement -

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_build_over.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_build_over.htm deleted file mode 100644 index e95b6ebfe67..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_build_over.htm +++ /dev/null @@ -1,162 +0,0 @@ - - - - - - Building C/C++ projects - - - -
-

Building C/C++ projects

-

The CDT relies on an external make utility, such as GNU make, to -build a project. The CDT can generate makefiles automatically when you -create a Managed Make C project or a Managed Make C++ project. You have -the option of creating a Standard Make C project or a Standard Make C++ -project and providing the makefile yourself.

-

Required utilities

-

You must install and configure the following utilities: -

- -Note: while make, gcc and gdb are the examples used in the -documentation, virtually any similar set of tools or utilities could be -used. -

-

Tip: Cygwin contains these utilities (make, gcc and gdb) for -a Windows environment.  While running the cygwin installation, -ensure gcc and make are selected since they are not -installed by default. For more information, see https://www.cygwin.com. If you are a -Red Hat user, all that you need to do to build your project is included -in the Red Hat Linux installation. -For other operating systems, please refer to your installation -documentation.

-

-

Build terminology

-

The CDT uses a number of terms to describe the scope of the build.

-

Build Project

-

This is an incremental build (make all, assuming all is defined in -your makefile). Only the components affected by modified files in that -particular project are built.

-

Rebuild Project

-

Builds every file in the project whether or not a file has been -modified since the last build. A rebuild is a clean followed by a build.

-

For more information on builds, see:

- -

Build-related information is displayed as follows:

- -

For more information about the Problems view, see Workbench User -Guide > Reference > User interface information > Views and -editors > Problems view.

- -

Getting a makefile

-

You can either create a C/C++ project for which you supply the makefile -or create a C/C++ project for which the CDT generates makefiles -automatically.

-

To create a new project, from the menu bar choose File > New -> Project. In the dialog that appears, expand the C/C++ group -and choose e.g. C Project

- -

Setting build preferences

-

You can set build preferences in Eclipse:

-
-
Build order
-
If certain projects must be built before others, you can set the build -order. If your project refers to another project, the CDT must -build the other project first. To set the build order, from the menu -bar select Window > Preferences and choose General > Preferences > Build Order. -

When you set the build order, the CDT does not rebuild projects -that depend on a project; you must rebuild all projects to ensure all -changes are propagated.

-
-
Automatic save
-
You can set the CDT to perform an automatic save of all -modified resources when you perform a manual build. In the preferences dialog, -select General > Workspace and check Save automatically before build. -By default, -this feature is not enabled.
-
- -

Controlling the building of your project

-

For a Makefile project, the C/C++ compiler that a project uses -is controlled by the project's Properties setting. -To view a project's properties, right-click on the project and select Properties. -In the dialog that appears, the C/C++ Build -page enables you to control a variety of settings, including:

-
-
Build Command
-
On the Builder Settings tab, this controls which make is used. To change it, uncheck Use - default build command and change it or add arguments to the make command.
- -
Build Setting
-
On the Behaviour tab, this controls whether the compiler will Stop on first build error or not - (keep going). Unchecking Stop on first build error will force the compiler to attempt to build all referenced - projects even if the current project has errors.
- -
Workbench Build Behavior
-
On the Behaviour tab, this controls which makefile target will be built depending on the scope of the - build, e.g. all or clean.
-
-

For a standard (non-Makefile) project (often called "Managed Build" or "Managed Make" project from -earlier CDT version), the project properties dialog enables -you to manage the build configurations of your project. For additional -information see:

- -

Viewing build information

-

Build-related information is displayed as follows:

- -

Related concepts -
-CDT Projects
-Project file views

-

Related tasks -
-Building projects

-

Related reference -
-Project Properties

-  -

Red Hat Copyright Statement
-IBM Copyright Statement -

-
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_comments.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_comments.htm deleted file mode 100644 index 96a45629250..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_comments.htm +++ /dev/null @@ -1,66 +0,0 @@ - - - - - - -Comments - - - - -
-

Comments

-

Comments are lines in a source file that have been marked to be ignored by the compiler. -Two styles of comments are supported by current C/C++ compilers:

- - -

Comment

-

You can quickly comment out one or more lines of code by inserting the leading -characters // at the beginning of the line. To do so, select the line -(or lines) of code you want to comment out and press CTRL+/ (slash).

- -

Uncomment

-

To uncomment select the line (or lines) of code, and press CTRL+\ -(backslash). - -

Tip: The characters /* */ on lines that are -already commented out, are not affected when you comment and uncomment code.

- -

Multiline comment

-

You can use the Content Assist feature to insert a multi-line comment before a function. -Type com+Ctrl+Space, and the following code is entered at the cursor location: -

-/*
- * author userid
- *
- * To change this generated comment edit the template variable "comment":
- * Window > Preferences > C/C++ > Editor > Templates.
- */
- 
- - To change the default comment click Window > Preferences > C > Templates. For more information see the - Content Assist section. - -

Related concepts -
-Content Assist and code completion

-

Related tasks -
-Customizing the C++ editor
-Commenting out code

-

Related reference -
-C/C++ editor preferences

- -

-Red Hat Copyright Statement
- IBM Copyright Statement -

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_content_assist.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_content_assist.htm deleted file mode 100644 index 714d7094d69..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_content_assist.htm +++ /dev/null @@ -1,98 +0,0 @@ - - - - - - - Content Assist - - - - -
-

Content Assist

- -

Content Assist is a set of tools built into the CDT that can reduce the number of keystrokes you must -type to create your code. The Content Assist plug-in consists of several components that forecast what -a developer will type, based on the current context, scope, and prefix.

- -

Code completion

- -

Content assist provides code completion anywhere in the document. For the current project a list is -displayed of the elements that begin with the letter combination you entered, and -the relevance of each proposal is determined in the following order:

- - - -You trigger the Code completion feature when you call Content Assist (such as when you type Ctrl+Space), but it is auto-activated when you type -., -> or ::.

- -

C++ example showing Code Assist popup

- -

You can view the signature of each item on the list in a pop-up by pointing to it. You can then select an item in the list to insert it directly into your code.

- -

Templates

- -

You can create and save templates for frequently used sections of code, which will be inserted according to scope. The Content Assist feature also provides quick access to code -templates.

- -

When you enter a letter combination in the C/C++ editor, and type CTRL+SPACE (or right-click and click Content Assist), a -list of code elements and templates that start with the letter combination that you typed is displayed.

- -

You can then select a template from the list and it is inserted directly into your code.

- -C++ example showing Code Assist popup

- -

For example, the template do while statement contains the following code:

- -

Code Template showing do-while example

- -

When you select the do template from the list, you insert the following code:

- -

do {
-} while (condition);

- - -

If the completion engine finds only one proposal in your templates, that proposal is inserted at the current cursor position. -For example if you create a new .cpp file and type mai+CTRL+SPACE the following code is inserted at the cursor location:

-

int
-main(int argc, char **argv) {
-	
-}

- -

No Completions

- -

If you invoke Content Assist, but no completions are found a message will be displayed on the status to inform you that the Content Assist parser has timed out.

- -

Content Assist No completions available message

- - -

Related concepts -
-Code entry

-

Related tasks -
-Using Content Assist
-Creating and editing templates
-Importing and exporting templates

-

Related reference -
-C/C++ perspective icons

- -

- -IBM Copyright Statement

-
- - - diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_dbg_info.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_dbg_info.htm deleted file mode 100644 index e65eaa89f6e..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_dbg_info.htm +++ /dev/null @@ -1,89 +0,0 @@ - - - - - - - - -Debug information - - - - -
-

Debug information

- -

When using the Stand-alone Debugger, you will be using the Debug -perspective. The Debug perspective lets you manage the debugging or running of a program -in the Eclipse Workbench. You can control the execution of your program by setting -breakpoints, suspending launched programs, stepping through your code, and -examining the contents of variables.

-

 The Debug perspective displays the following information:

- - -

The Debug perspective also drives the C/C++ Editor. As you step -through your program, the C/C++ Editor highlights the location of the -execution pointer.

- -

Variables

- -

You can view information about the variables in a selected stack frame in the -Variables view. When execution stops, the changed values are -by default highlighted in red. Like the other debug-related views, the Variables view does -not refresh as you run your executable. A refresh occurs when execution stops.

- -

Expressions

- -

An expression is a snippet of code that can be evaluated to produce a result. -The context for an expression depends on the particular debug model. Some -expressions may need to be evaluated at a specific location in the program so -that the variables can be referenced. You can view information about expressions -in the Expressions view.

- -

Registers

- -

You can view information about the registers in a selected stack frame. -Values that have changed are highlighted in the Registers view when your program -stops.

- -

Memory

- -

You can inspect and change your process memory.

- -

Disassembly

- -

You can view disassembled code mixed with source information.

- -

Modules

- -

You can view information about the modules (executables and shared libraries) loaded -in the current debug session.

- -

Signals

- -

You can view the signals defined on the selected debug target and how the -debugger handles each one.

-

Related concepts -
-Overview of the CDT
-Debug overview

-

Related tasks -
-Debugging

-

Related reference -
-Run and Debug dialog box
-Debug views

- -IBM Copyright Statement

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_discovery_options.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_discovery_options.htm deleted file mode 100644 index 7e466d64120..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_discovery_options.htm +++ /dev/null @@ -1,54 +0,0 @@ - - - - - - - Views in the C/C++ perspective - - - - -
-

Discovery options

- -

For projects where the IDE generates a makefile to build the project automatically, the IDE has more information about the internal build state of the make project compared to those projects where you provide a makefile to build the project. - -

For example, a makefile includes build information and other settings, such as include file paths (-I) and macro definitions (-D), which are standard to the build tools (such as the compiler and linker). When the makefile is automatically created for you, this information is known to Eclipse to a greater extent then when you create and manage the makefile for a project yourself. The type of information affects the search capabilities and Code Assist abilities of Eclipse. Therefore, in this example, the purpose of Discovery Options is for improved search and Code Assist capability for projects where Eclipse does not manage the makefile for you. For example, in an open source file of an editor view, to see the declaration for a function that the code calls, you select the function, right click, and select Open Declaration from the context menu. If the location of the include file (that was coded in the makefile for the project) containing the function declaration was in some directory, the CDT would not find the declaration because it has no visibility for that include path. Consequently, you can use Discovery Options in the CDT to enhance the IDE build state by parsing the build process output to extract build path information that the CDT searching mechanism uses to locate and open the include file. By default, the CDT uses GNU* tools (gcc, etc.). If you want to build your projects using another compiler, use the settings described here.

- -

Scanner configuration discovery is tightly linked to project's build process. The first part of scanner discovery begins during the make build for make projects where you provide the makefile. The Eclipse CDT parses the build output for compiler commands with options that specify the definition of the preprocessor symbols and include search paths (for the gcc compiler, -D and -I), and then it stores the information as the project's discovered scanner configuration. - -

Next, after the build process completes, it is implemented as a separate Eclipse builder where it runs a generate scanner info command, and then parses the output (properties specified on the Discover Options tab for Builds in the Project Properties window). - -

For C++, the default generate scanner information command is gcc -E -P -v myfile.c | myfile.cpp. This command reads the compiler's configuration file and prints the information that includes compiler's internally defined preprocessor symbols and include search paths. - -

A single scanner configuration is applicable to all the files in a project. Although Eclipse discovers the information for each compilation unit, it stores the scanner configuration on a per project basis. This means that Eclipse applies a single, cumulative scanner configuration to all files in a project. - -

The following situations identify circumstances when certain parts of the scanner configuration are in conflict: -

-

- -

Note: Only basic command line options are supported. In addition, only basic scanner configuration related command line options are recognized (for example, -D and -I for gcc). For some of the commands, their relative position in the command line is important. For information about these options, see the documentation for the utilities you are using. - -

Related concepts -
CDT Overview -
C/C++ perspectives -

- - -

Related reference -
Views -

- -

-Red Hat Copyright Statement
- IBM Copyright Statement -

-
- - - diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_editor.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_editor.htm deleted file mode 100644 index 40c43c1d453..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_editor.htm +++ /dev/null @@ -1,53 +0,0 @@ - - - - - - -C/C++ editor - - - -
-

C/C++ editor

- -

The Stand-alone Debugger provides an editor that gives you specific support for editing C/C++ code. -This C/C++ editor is invoked automatically when you open a C/C++ source file. While you are able -to modify the contents of a file, if you save those changes, you will need to rebuild the project outside of the Stand-alone Debugger -to synchronize the debug information in the executable with the source files used.

- -

The C/C++ editor includes the following features:

- - -

You can customize some of the operation of the Editor view from the Window > Preferences > C/C++ > Editor preferences dialog.

- - - - - -

Related concepts -
CDT Overview -

- -

Related tasks -
Using Content Assist -

- -

Related reference -
C/C++ editor preferences -
Outline view for C/C++ -
Views and editors -

- -

-Red Hat Copyright Statement
- IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer.htm deleted file mode 100644 index 4c1005a43b6..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer.htm +++ /dev/null @@ -1,59 +0,0 @@ - - - - - - C/C++ Indexer - - - -
-

C/C++ Indexer

-

The C/C++ indexer uses the parser to create a database of your -source and header files that provides the basis for C/C++ search, -navigation features and parts of content assist.

-

The indexer runs on a background thread and reacts to resource -change events such as: -

- -

It is possible to customize the behavior of the indexer through the -use of source folders or even turn it off completely. This customizable -behavior is available on a per-project basis (i.e. it is possible to -have different indexer settings for each project in your workspace).
-

-

CDT supports the contribution of additional indexers, with 2 -indexers being provided with the default CDT release:
-

- -

Related concepts
-C/C++ search
-C/C++ Indexer Progress Bar
-Scanner Discovery
-

-

Related tasks
-Selection Searching for C/C++ elements
-Setting Source Folders
-

-

Related reference
-C/C++ search page, Search dialog box
-C/C++ Project Properties, Indexer
-

- -

 

-IBM Copyright Statement -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer_fullindexer.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer_fullindexer.htm deleted file mode 100644 index c2ce9f3f0cd..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer_fullindexer.htm +++ /dev/null @@ -1,47 +0,0 @@ - - - - - - Full C/C++ Indexer - - - -
-

Full C/C++ Indexer

-

The Full C/C++ Indexer is a new indexer for CDT 3.0 which makes use -of the new DOM. It creates a full index of the project's source -providing both declaration and cross reference information to the -various clients that make use of the index. In comparison with the -previous versions of the indexer, the new C/C++ indexer provides -quicker and more accurate results.
-

-

This indexer provides the most complete set of information but can -be potentially long running, especially on larger projects.
-

-

Related concepts
-C/C++ Indexer
-C/C++ search
-C/C++ Indexer Progress Bar

-

Related tasks
-Selection Searching for C/C++ -elements
- -Setting Source Folders
-

-

Related reference -
-C/C++ search page, Search -dialog box -
-C/C++ Project Properties, Indexer -

-

 

-IBM Copyright Statement -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer_prog_bar.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer_prog_bar.htm deleted file mode 100644 index 6bc6fce8233..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer_prog_bar.htm +++ /dev/null @@ -1,46 +0,0 @@ - - - - - - C/C++ Indexer Progress Bar - - - -
-

C/C++ Indexer Progress Bar

-

The indexer progress bar shows the progress status of the indexing -jobs in the progress views.

-

The indexing jobs can be temporarily paused by pressing the stop -button on the progress bar. This will cause the indexer to wait until -the next time the user runs a search job or makes a change to an -indexed element (by such actions as modifying an existing source file, -deleting a file, creating a new file, moving file and so on). The -indexer at this point will resume with the previously postponed -indexing job before moving on to the new one.

-

If you wish to cease indexing all together, you can cancel an -indexing job and disable the indexer through the properties.

-

Related concepts -
-C/C++ search
-C/C++ Indexer
-

Related tasks
-Selection Searching for C/C++ -elements
-Setting Source Folders
-

-

Related reference -
-C/C++ search page, Search -dialog box -
-C/C++ Project Properties, Indexer -

-

 

-IBM Copyright Statement -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_makefile.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_makefile.htm deleted file mode 100644 index 50279d69968..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_makefile.htm +++ /dev/null @@ -1,187 +0,0 @@ - - - - - - -Makefile - - - - -
-

Makefile

-

A makefile is a text file that is referenced by the make command that describes the building of targets, and contains information such as source-level dependencies and build-order dependencies.

-

The CDT can generate a makefile for you, such projects are called Managed Make projects. Some projects, known as Standard Make projects, allow you to define your own makefile.

- -

Sample Makefile

-
-# A sample Makefile
-# This Makefile demonstrates and explains 
-# Make Macros, Macro Expansions,
-# Rules, Targets, Dependencies, Commands, Goals
-# Artificial Targets, Pattern Rule, Dependency Rule.
-
-# Comments start with a # and go to the end of the line.
-
-# Here is a simple Make Macro.
-LINK_TARGET = test_me.exe
-
-# Here is a Make Macro that uses the backslash to extend to multiple lines.
-# This allows quick modification of more object files.
-OBJS =  \
- Test1.o \
- Test2.o \
- Main.o
-
-# Here is a Make Macro defined by two Macro Expansions.
-# A Macro Expansion may be treated as a textual replacement of the Make Macro.
-# Macro Expansions are introduced with $ and enclosed in (parentheses).
-REBUILDABLES = $(OBJS) $(LINK_TARGET)
-
-# Make Macros do not need to be defined before their Macro Expansions,
-# but they normally should be defined before they appear in any Rules.
-# Consequently Make Macros often appear first in a Makefile.
-
-# Here is a simple Rule (used for "cleaning" your build environment).
-# It has a Target named "clean" (left of the colon ":" on the first line),
-# no Dependencies (right of the colon),
-# and two Commands (indented by tabs on the lines that follow).
-# The space before the colon is not required but added here for clarity.
-clean : 
- rm -f $(REBUILDABLES)
- echo Clean done
-
-# There are two standard Targets your Makefile should probably have:
-# "all" and "clean", because they are often command-line Goals.
-# Also, these are both typically Artificial Targets, because they don't typically
-# correspond to real files named "all" or "clean".  
-
-# The rule for "all" is used to incrementally build your system.
-# It does this by expressing a dependency on the results of that system,
-# which in turn have their own rules and dependencies.
-all : $(LINK_TARGET)
- echo All done
-
-# There is no required order to the list of rules as they appear in the Makefile.
-# Make will build its own dependency tree and only execute each rule only once
-# its dependencies' rules have been executed successfully.
-
-# Here is a Rule that uses some built-in Make Macros in its command:
-# $@ expands to the rule's target, in this case "test_me.exe".
-# $^ expands to the rule's dependencies, in this case the three files
-# main.o, test1.o, and  test2.o.
-$(LINK_TARGET) : $(OBJS)
- g++ -g -o $@ $^
-
-# Here is a Pattern Rule, often used for compile-line.
-# It says how to create a file with a .o suffix, given a file with a .cpp suffix.
-# The rule's command uses some built-in Make Macros:
-# $@ for the pattern-matched target
-# $lt; for the pattern-matched dependency
-%.o : %.cpp
- g++ -g -o $@ -c $<
-
-# These are Dependency Rules, which are rules without any command.
-# Dependency Rules indicate that if any file to the right of the colon changes,
-# the target to the left of the colon should be considered out-of-date.
-# The commands for making an out-of-date target up-to-date may be found elsewhere
-# (in this case, by the Pattern Rule above).
-# Dependency Rules are often used to capture header file dependencies.
-Main.o : Main.h Test1.h Test2.h
-Test1.o : Test1.h Test2.h
-Test2.o : Test2.h
-
-# Alternatively to manually capturing dependencies, several automated
-# dependency generators exist.  Here is one possibility (commented out)...
-# %.dep : %.cpp
-#        g++ -M $(FLAGS) $< > $@
-# include $(OBJS:.o=.dep)
-
- - -

Frequently Asked Questions:

-Your Console view can be very useful for debugging a build. - -

Q1. My Console view says Error launching builder. What does that mean?

-
-Error launching builder (make -k clean all )
-(Exec error:Launching failed)
-
- -

Most probably, the build command (by default "make") is not on your path. You can put it on your path and restart Eclipse.
-You can also change the build command to something that is on your path. If you are using MinGW tools to compile, you should replace the build command with "mingw32-make".

- -

Q2. My Console view says No rule to make target 'X'.

-
-make -k clean all 
-make: *** No rule to make target 'clean'.
-make: *** No rule to make target 'all'.
-
- -

By default, the make program looks for a file most commonly called "Makefile" or "makefile". -If it cannot find such a file in the working directory, or if that file is empty or the file does not -contain rules for the command line goals ("clean" and "all" in this case), it will normally fail -with an error message similar to those shown.

- -

If you already have a valid Makefile, you may need to change the working directory of your build. The default working directory for the build command is the project's root directory. You can change this by specifying an alternate Build Directory in the Make Project properties. -Or, if your Makefile is named something else (eg. buildFile.mk), you can specify the name by setting the default Build command to make -f buildFile.mk.

- -

If you do not have a valid Makefile, create a new file named Makefile in the root directory. You can then add the contents of the sample Makefile (above), and modify it as appropriate.

- -

Q3. My Console view says "missing separator".

-
-make -k clean all 
-makefile:12: *** missing separator.  Stop.
-
-

The standard syntax of Makefiles dictates that every line in a build rule must be preceded by a Tab character. -This Tab character is often accidentally replaced with spaces, and because both result in white-space indentation, -this problem is easily overlooked. In the sample provided, the error message can be pinpointed to line 12 of the -file "makefile"; to fix the problem, insert a tab at the beginning of that line.

- -

Q4. My Console view says Target 'all' not remade because of errors.

-
-make -k clean all 
-make: *** [clean] Error 255
-rm -f Test1.o Test2.o Main.o test_me.exe
-g++ -g -o Test1.o -c Test1.cpp
-make: *** [Test1.o] Error 255
-make: *** [Test2.o] Error 255
-make: *** [Main.o] Error 255
-g++ -g -o Test2.o -c Test2.cpp
-g++ -g -o Main.o -c Main.cpp
-make: Target 'all' not remade because of errors.
-
-

The likely culprit here is that g++ is not on your Path.
-

The Error 255 is produced by make as a result of its command shell not being able to find a command for a particular rule.
-Messages from the standard error stream (the lines saying Error 255) and standard output stream (all the other lines) are merged in the Console view here.

- -

Q5. What's with the -k flag?

- -

The -k flag tells make to continue making other independent rules even when one rule fails. -This is helpful for build large projects.

-

You can remove the -k flag by turning on Project Properties > C/C++ Make Project > Make Builder > Stop on first build error

- -

Q6. My Console view looks like:

-
-mingw32-make clean all 
-process_begin: CreateProcess((null), rm -f Test1.o Test2.o Main.o test_me.exe, ...) failed.
-make (e=2): The system cannot find the file specified.
-
-mingw32-make: *** [clean] Error 2
-rm -f Test1.o Test2.o Main.o test_me.exe
-
- -

This means that mingw32-make was unable to find the utility "rm". Unfortunately, MinGW does not come with "rm". To correct this, replace the clean rule in your Makefile with:

-

-clean : 
-	-del $(REBUILDABLES)
-	echo Clean done
-

-

The leading minus sign tells make to consider the clean rule to be successful even if the del command returns failure. This may be acceptable since the del command will fail if the specified files to be deleted do not exist yet (or anymore).

- - -

IBM Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_open_declarations.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_open_declarations.htm deleted file mode 100644 index 583b72b891e..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_open_declarations.htm +++ /dev/null @@ -1,40 +0,0 @@ - - - - - - -Open Declaration - - - - -
-

Open Declaration

- -

You can select an element name in your code and quickly navigate to its declaration.

- -Editor View showing Open Declaration option - -

Open declaration will attempt to navigate to the exact definition of the selected element if the selected element is a reference or a declaration. -Otherwise, it will attempt to navigate to a declaration of the selected element. -Open declaration requires your file to have the proper include paths set up to the declaration. -If for any reason open declaration cannot find the declaration, it will display the following message in the status line:

- -No declaration was found message. - -

For more information see Setting up include paths and macros for C/C++ indexer.

- -

Related concepts
-C/C++ Projects
-C/C++ search

-

Related tasks
-Setting up include paths and macros for C/C++ indexer
-Navigate to a C or C++ element's declaration
-Searching for C/C++ elements

- -

IBM Copyright Statement

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_outlineview.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_outlineview.htm deleted file mode 100644 index 28b23746941..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_outlineview.htm +++ /dev/null @@ -1,131 +0,0 @@ - - - - - - - Outline view - - - - -
-

Outline view

- -

The Outline view displays an outline of a structured C/C++ file that is currently -open in the editor area, by listing the structural elements.

- -Editor View highlighting corresponding element in the Outline View - -

The Outline view shows the following elements in the source file in the order -in which they occur:

- - - -

You can also sort the list -alphabetically. When you select an element in the Outline view, the C/C++ -editor highlights both the selected item and the marker bar (left margin). For example, to move -to the start of main() in the C/C++ editor, click main() in the Outline -view.

- -

For more information about the marker bar, see Workbench User Guide > Reference > User interface -information > Views and editors > Editor area.

- -

Filtering the Outline View

- -

You can filter the Outline view by choosing to display or hide the following -items:

- - - -

You can select an element in the Outline view, and perform the following actions:

- - -

Icons

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconDescription
Collapse All IconCollapse All
Sort items alphabetically IconSort items alphabetically
Hide Fields IconHide Fields
Hide Static Members IconHide Static Members
Hide Non-Public Members IconHide Non-Public Members
Hide Inactive Elements IconHide Inactive Elements

- -

For more information about the Eclipse workbench, see Workbench User Guide > Tasks > Upgrading Eclipse.

-

For more information about Working sets, see Workbench User Guide > Concepts > Working sets.

- - -

Related concepts -
-Comments
-Content Assist and code completion
-C/C++ search
-Open Declaration

-

Related tasks -
-Displaying C/C++ file components in the -Project Explorer view
-Searching for C/C++ elements

-

Related reference -
-Outline view

- -IBM Copyright Statement -
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_over_cdt.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_over_cdt.htm deleted file mode 100644 index b4133f6ad9f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_over_cdt.htm +++ /dev/null @@ -1,92 +0,0 @@ - - - - - - CDT overview - - - -
-

CDT Overview

-

The C/C++ Development Toolkit (CDT) is a set of Eclipse plug-ins that provide -C and C++ extensions to the Eclipse workbench. For more information about -Eclipse, see Workbench User Guide > Concepts > Workbench.

- -

The full CDT provides a C/C++ IDE that simplifies many of the same tools that you can use from the command line. The CDT can also communicate with many external utilities and interpret their responses, for example: -

-Note: while make, gcc and gdb are the examples used in the documentation, virtually any similar set of tools or utilities could be used.

- -

The Stand-alone Debugger application is built from various Eclipse plug-ins from the CDT pertaining to Debug and Edit. Plug-ins associated -with Build and Compile are not included. Though it is possible to edit files within the Stand-alone Debugger, any changes -will require a rebuild which will have to be performed outside of the Debugger. If you want a full C/C++ IDE, then it is suggested to use the full CDT -instead which incorporates the C/C++ Debugger within it.

- - - -

Additional information

- -

For more information on the Eclipse CDT project, -refer to https://www.eclipse.org/cdt/: -

- - - - - -

License

-

The CDT is an open source project and is licensed under the Eclipse Public License. - - - -

Related reference -
-Views

- -IBM Copyright Statement -
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_over_dbg.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_over_dbg.htm deleted file mode 100644 index a7f0489d55a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_over_dbg.htm +++ /dev/null @@ -1,46 +0,0 @@ - - - - - - - - -Debug overview - - - - -
-

Debug overview

- -

The debugger lets you see what's going on "inside" a program while it -executes.

-

In order to debug your application, you must use executables compiled for -debugging. These executables contain additional debug information that lets the -debugger make direct associations between the source code and the binaries -generated from that original source.

-

The Stand-alone debugger uses GDB as the underlying debug engine. It translates each -user interface action into a sequence of GDB commands and processes the output from GDB to -display the current state of the program being debugged.

-

Tip: Editing the source after compiling causes the line numbering to be out of -step because the debug information is tied directly to the source. Similarly, -debugging optimized binaries can also cause unexpected jumps in the execution -trace.

-

Related concepts -
-Overview of the CDT
-Debug information

-

Related tasks -
-Debugging

-

Related reference -
-Run and Debug dialog box

- -IBM Copyright Statement

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_perspectives.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_perspectives.htm deleted file mode 100644 index 9d452fad811..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_perspectives.htm +++ /dev/null @@ -1,76 +0,0 @@ - - - - - - -Perspectives available to C/C++ developers - - - -
-

Perspective

- -

A perspective is a layout of views (development tools) in the Workbench window. -Each type of perspective is a combination of views, menus, and toolbars that enable you to perform a particular task. -In the Stand-alone Debugger, you only have the choice of the Debug perspective which has views that -enable you to debug programs. When ever you use the Stand-alone Debugger, you will be placed into the Debug -perspective. -

- -
-Selecting / Opening Views: -
    -
  • You can add views to the perspective. From the menu bar choose Window > Show View and open a category then select a new view from the Show View dialog.
  • -
  • To reset the Debug perspective to its original layout, from the menu bar choose Window > Reset Perspective.
  • -
-
- -

The C/C++ development tools contribute the following perspectives to the workbench: -

- - -

There a several additional views that may be useful during a debug session. You can add them by clicking Window > Show View > C/C++ to show them in the C/C++ perspective.

-

Debug perspective views

- -

The Debug perspective is tuned for debugging your C/C++ program. -By default it includes an editor area and the following views: -

- - -

There a several additional views that may be useful during a debug session. You can add them by clicking Window > Show View > Debug to show them in the Debug perspective.

- -

Additional C/C++ views

- -

There are some additional C/C++ views that are provided that may be accessed using Window > Show View > C/C++. -These will normally not be needed for debugging but may be helpful if there are problems and the user has an understanding -of the full CDT IDE. The additional views are: -

- - -

Related reference -
-C/C++ Views and Editors

- -

-Red Hat Copyright Statement
- IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_proj_file_views.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_proj_file_views.htm deleted file mode 100644 index f0d9c0219a1..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_proj_file_views.htm +++ /dev/null @@ -1,66 +0,0 @@ - - - - - - -Project file views - - - - -
-

Project file views

- -

Projects files and elements are displayed in the C/C++ Projects view and in the ProjectExplorer view.

- -

C/C++ Projects view

-

Displays, in a tree structure, only elements relevant to C and C++ projects. In this view you can do the following: -

- -Files that you select in the C/C++ Projects view affect the information that is displayed in other views.

- -C/C++ Projects View - -

Project Explorer view

- -

The Project Explorer view provides a hierarchical view of all the resources in the workbench, not just your C/C++ resources. -From this view, you can open files for editing or select resources for operations such as exporting.

- -

Right-click any resource in the Project Explorer view to open a pop-up menu from which you can perform operations such as -copy, move, create new resources, compare resources, or perform team operations. For a description of what each menu -item does, select an item and press F1.

- -

The Project Explorer view is provided by the Eclipse Platform. - - -C/C++ perspective icons

-

- -IBM Corporation Statement

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_projects.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_projects.htm deleted file mode 100644 index 57f965eef7a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_projects.htm +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - CDT projects - - - -
-

C/C++ projects

- -

Normally, before you can work with plug-ins provided by the CDT, you must create an Eclipse project to store your -source code, makefiles, binaries, and related files. However, when you use the Stand-alone Debugger, a project is created -for your executable automatically (usually the Executables project if only dealing with one executable). -The project created on your behalf just contains the executable and links to the source files specified in the debug -info. In most cases, you do not need to know about the project to debug, but if you wish to see the various files used -and browse them directly with the editor, you can find the project in the C/C++ Projects view. While you are allowed to import -files into the C/C++ project, this action is normally used for adding files to a project that can build. Since the Stand-alone -Debugger does not contain CDT (C/C++ Developer Tools) build capability, adding files does nothing to aid in debugging and can -confuse the indexer if the source has errors in it.

- - -

Related concepts -
-Project file views
-

Related tasks -
-Working with C/C++ project files
-

-

Related reference -
-Project properties
-Views

- - -IBM Copyright Statement -
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_scanner_discovery.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_scanner_discovery.htm deleted file mode 100644 index 889fec4e3c1..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_scanner_discovery.htm +++ /dev/null @@ -1,108 +0,0 @@ - - - - - - - Scanner Discovery - - - -
-

Scanner Discovery

-

- -

General

-Scanner Discovery (sometimes called Autodiscovery) is a method of finding include paths and predefined preprocessor macros which the compiler uses during compilation of the code. -

- -

-Even a simplest C/C++ program just printing "Hello World" needs to include system headers. Consider: -

-
-#include <stdio.h>
-#include <stdlib.h>
-
-int main(void) {
-  puts("!!!Hello World!!!");
-  return EXIT_SUCCESS;
-}
-
- -

-Indexer needs to be able to find headers stdio.h and stdlib.h and parse them to provide accurate index. -In this example, the headers define prototype of function puts and macro EXIT_SUCCESS. -

- - -

-The Stand-alone Debugger will try to discover include paths and preprocessor symbols automatically. -There are 2 main ways to discover those: -

-
    -
  1. Built-in Settings. -The debugger will try to detect built-in compiler symbols and include paths running the compiler with special options and parse the output of this special run. -Most compilers provide such an option to print built-in include paths and symbols. Built-in settings are implied and do not get passed to the compiler during regular compilation. -
  2. -
  3. Build Output Parser (BOP). -Another method that the debugger employs is to analyze build output you provide to its Build Output Parser. -Often, include paths are supplied to the compiler with -I options, and macros with -D options -and BOP will try to find those in the output. -That method relies on verbose build output of your build where all these options are actually printed by make. To -specify build output either use the -b command-line option or else specify the location of the -build log when using the File > New Executable... dialog. -
  4. -
- -

-The debugger uses Language Settings Providers to discover the settings (starting with version CDT 8.1). Typically Language settings Providers are specialized. -One will provide built-in compiler settings and another one settings detected by Build output Parser. -

- -

-The setting entries found by Scanner Discovery can be inspected in project properties on "Preprocessor Include Paths, Macros etc." page. -Each Language Settings Provider can be expanded to show the entries it discovered. -

- -

-Preprocessor Include Paths and Macros Entries -

- - -

-If information retrieved by auto-discovery is insufficient a user can enter additional include paths and macros manually under "User Settings Entries". -

- - -

Console View

-

-The output of built-in compiler specs detectors can be inspected to troubleshoot problems running the command. -To do so, enable checkbox "Allocate console in the Console View". -

-

-Spec Detectors Properties -

- -

-When checkbox "Allocate console in the Console View" is enabled, output of each run of the provider will be directed to a special console in the Console View. -

-

-Console View -

- -

Related concepts
-C/C++ Indexer
-

- -

Related tasks
-Setting up include paths and macros for C/C++ indexer
-

- -

Related reference
-C/C++ Preferences: Scanner Discovery
-C/C++ Project properties: Preprocessor Include Paths, Macros, etc.
-

- -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_search.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_search.htm deleted file mode 100644 index 18cec23ac66..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_search.htm +++ /dev/null @@ -1,275 +0,0 @@ - - - - - - -C/C++ search - - - - -
-

C/C++ search

- -

You can conduct a fully or partially qualified name search. Further -qualifying a search increases the accuracy and relevance of search results. The -sections below provide guidance on how to control the scope of your search -through the use of search delimiters, correct syntax, and wildcards.

- -

You can search for:
-

-

- -For information on working sets, see Workbench User Guide > Concepts > Workbench > Working sets
- - -

What you can search for

-

The table below lists the element types that you can search for and special - considerations to note when searching for a given element type. You can search - for some or all of the element types matching a search string that you - specify. If you choose to search for matching elements, all types, macros, and typdefs are included in the search.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ElementNote
 Class/StructSearches for classes and structs.

You can further qualify - the search by specifying "class" or "struct" in front of the name - that you are - searching for. Specifying "class" or "struct" also allows you to - search for anonymous classes and structures.

 FunctionSearches for global functions or functions in a namespace - (functions that are not members of a class, struct, or union).

You can - specify parameters to further qualify your search. When specifying a - parameter list, everything between the parentheses should be valid C/C++ - syntax.

-

Do not specify the return type of the function.

 VariableSearches for variables that are not members of a class, - struct, or union.
 UnionSearches for unions.

Anonymous unions can be searched for by - specifying "union" as the search pattern.

 MethodSearches for methods that are members of a class, struct, or - union.

Searching for methods also finds constructors and destructors. See - above note for functions.

 Field Searches for fields that are members of a class, struct, or - union. -
 EnumerationSearches for enumerations.
 EnumeratorSearches for enumerators.
 NamespaceSearches for namespaces.
- -

How you can limit your search

- -

You can limit your search to one or all of the following:

- - - -

You can control the scope of the search by specifying which of the following -is to be searched:

- - -

Wildcard characters

-

You can use wildcard characters to further refine your search.

- - - - - - - - - - - - - - - - - -
Use this wildcard characterTo search for this
 *Any string

Tip:
-
Use the character sequence \* to search for - operators that begin with *. See syntax examples in the table below.

 ?A single character
 ::Nested elements
- -

Syntax examples

-

The table below provides syntax examples and an explanation for each example -to help you conduct an effective search.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SyntaxSearches for this
  ::*::*::AA nested element two levels deep
  ::*::*::A?Any two-letter name that begins with A and is two levels - deep
  ::A Searches for A not nested in anything
 operator \*Finds only operator *
 operator \*=Finds only operator *=
 operator *Finds all operators
 classSearches for anonymous classes
 structSearches for anonymous structs
 unionSearches for anonymous unions
-

Search results

-

Search results are displayed in the Search view. You can sort your search by Name, Parent Name and Path. You can also repeat -your last search.

- -

Search Concepts

- -

Declarations

-

According to the ANSI C++ Spec, a declaration is a statement that introduces a name into a translation unit or re-declares a name that has been previously introduced by a previous declaration.

-

All C/C++ search elements can be searched for declarations.

- -

Definitions

-

Most declarations are also definitions; in other words, they also define the entity for they declare the name for. However there are some elements that can have separate definitions from their declarations.

-

For C/C++ search the following elements can be searched for definitions: -

- -

References

-

By selecting references, C/C++ search will return all of the places the selected element is used.

- -

All Occurrences

-

Selecting 'All Occurrences' in the Limit To section will result in a search for declarations, definitions (if applicable) and references for whatever element or elements have been selected.

- -

Any Element

-

Selecting 'Any Element' in the Search For section will result in a search for all of the listed elements plus macros and typedefs.

- - -

For more information, see:

-

Related concepts
-C/C++ Indexer
-C/C++ Projects
-Open Declaration
-

-

Related tasks -
-Searching for C/C++ elements
-Navigating to C/C++ declarations
-

-

Related reference
-C/C++ search page, Search dialog box
-C/C++ perspective icons

- -IBM Copyright Statement

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_standalone_intro.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_standalone_intro.htm deleted file mode 100644 index db7b6cf90e4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_standalone_intro.htm +++ /dev/null @@ -1,47 +0,0 @@ - - - - - - - Introduction - - - -
-

Introduction

-

The Stand-alone Debugger is an Eclipse application which packages the -Eclipse plug-ins from the CDT (C/C++ Development Tools) project into an -application that can be started from a command-line script. The debugger -removes some of the plug-ins that would be found in the full CDT set that -are related to building and project set-up. This simplifies the UI for -the end-user who is only interested in debugging and is not interested in -using Eclipse to build the application itself.

-

In addition, the Stand-alone debugger helps to simplify debugging in that -it hides Eclipse-specific concepts such as the Eclipse project and launch -configuration. While these concepts are hidden, they still are used underneath -and an experienced Eclipse user can still access them. Subsequent documentation -here will attempt to point out where such concepts are being automated by the -Stand-alone Debugger and how they can still be accessed.

- - -

Related concepts
-CDT Overview
-C/C++ Projects
-C/C++ Perspectives
-C/C++ Indexer
-C/C++ Search

-

Related reference -
-Views
-

Related tasks -
-Starting the debugger
- -Intel Copyright Statement - -

- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_templates.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_templates.htm deleted file mode 100644 index ab72db5d9c6..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_templates.htm +++ /dev/null @@ -1,66 +0,0 @@ - - - - - -Templates - - - - -
-

Templates

- -

- Templates are sections of code that occur frequently enough that you - would like to be able to insert them with a few keystrokes. This - function is known as Content Assist; the sections of - code that are inserted are known as templates. -

-

- To insert an existing Content Assist template into a file, such as - one for an if statement, type the initial character - ("i" in this case), then press Ctrl+Space. - The templates that begin with that character appear. Double-click on - a template to insert it into a file. -

- -

- You can edit the existing Content Assist templates or create new - ones using the C/C++ - > Editor > Templates preference pane. -

- -

- Related concepts
CDT Overview -

- -

- Related tasks
Creating and editing - templates
Using - templates
Importing - and exporting templates -

- -

- Related reference
Edit - menu
Content - Assist page
Templates - page -

- -

- Red Hat Copyright Statement
- IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_views.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_views.htm deleted file mode 100644 index 77a6fd1d8c3..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_views.htm +++ /dev/null @@ -1,55 +0,0 @@ - - - - - - - Views in the C/C++ perspective - - - - -
-

C/C++ Views

- -

The C/C++ views are panels that help you perform the tasks involved in managing C/C++ programs. -These views can be added to the perspective for your Eclipse window.

- -Changing Views: - - -

The following views are commonly used in the C/C++ perspective:

- -
-
Project Explorer
Shows all of the file system's files under your workspace directory.
-
Console
Displays your program's output, as well as the output from your build tools.
-
Editor
The C/C++ editor view provides specialized features for editing C/C++ related files.
-
Outline
Displays the structure of the file currently open in an editor.
-
Problems
-
If you encounter any errors during a build they will be displayed in the Problems view.
-
Properties
Shows the attributes of the item currently selected in a view or an editor.
-
Tasks
Lists tasks that want to keep track of, either as a schedule of things to do or a history of things that have been done.
-
- -

Related concepts -
CDT Overview -
Perspectives -

- - -

Related reference -
Views -

- -

-Red Hat Copyright Statement
- IBM Copyright Statement -

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew.htm deleted file mode 100644 index 4c095542ecf..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew.htm +++ /dev/null @@ -1,23 +0,0 @@ - - - - - - - - CDT New and Noteworthy - - - -
-

CDT - New and Noteworthy

-

See What's new in CDT - which contains the most recent information. -

- -

Back to Top

- -

 

-
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_build_conc.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_build_conc.htm deleted file mode 100644 index 580c7b9c639..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_build_conc.htm +++ /dev/null @@ -1,24 +0,0 @@ - - - - - - -Build - - - - -
-

Build

-

This section describes the build views and terminology.

- -Building C/C++ Projects
-Scanner Discovery of include paths and preprocessor macros
- - -

IBM Copyright Statement

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_code_entry.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_code_entry.htm deleted file mode 100644 index d3b80448f14..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_code_entry.htm +++ /dev/null @@ -1,23 +0,0 @@ - - - - - - -Coding aids - - - - -
-

Coding aids

-

This section provides information on code entry aids.

- -Comments
-Content Assist
-Templates
- -

IBM Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_concepts.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_concepts.htm deleted file mode 100644 index 90f35b4e3a4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_concepts.htm +++ /dev/null @@ -1,60 +0,0 @@ - - - - - - - Concepts - - - - -
-

Concepts

- -

Provides background information for CDT components, tasks and objectives.

- - -CDT Overview
-CDT Projects
-Perspectives available to C/C++ developers
-Views in the C/C++ perspective
-Coding aids
- Comments
- Content Assist
- Templates
-Editing C/C++ Files
- C/C++ editor
- Makefile
-Navigation aids
- Outline View
- Project File views
- C/C++ Search
- Open Declaration
- -Build
- Building C/C++ Projects
- Scanner Discovery of include paths and preprocessor macros
-Debug
- Breakpoints
- Debug overview
- Debug information
- -C/C++ search
- C/C++ Indexer
- C/C++ Indexer Progress Bar
- -

IBM Corporation Statement

-
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_dbg_concepts.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_dbg_concepts.htm deleted file mode 100644 index c447f3d0038..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_dbg_concepts.htm +++ /dev/null @@ -1,23 +0,0 @@ - - - - - - -Debug - - - - -
-

Debug

- -

This section describes C/C++ debug concepts.

-Breakpoints
-Debug overview
-Debug information
- -

IBM Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_edit.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_edit.htm deleted file mode 100644 index 3f8d1f0cbe9..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_edit.htm +++ /dev/null @@ -1,20 +0,0 @@ - - - - - - -Editing C/C++ Files - - - - -
-

Editing C/C++ Files

-

This section provides information on editing C/C++ files.

- C/C++ editor
- -

IBM Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_home.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_home.htm deleted file mode 100644 index ea5e422bc4d..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_home.htm +++ /dev/null @@ -1,36 +0,0 @@ - - - - - - - C/C++ Development User Guide - - - -
-

C/C++ Development User Guide

- -

The C/C++ Development Toolkit (CDT) is a collection of Eclipse-based features that provides the capability -to create, edit, navigate, build, and debug projects that use C and/or C++ as a programming language.

- -

The CDT does not include the necessary compilers and debuggers to convert C/C++ code into executable -programs and to debug those programs, but it does provide the frameworks that allow such tools to -be integrated in a consistent fashion. -This allows you to mix and match such tools depending on your project requirements.

- -

Often, commercial distributions of the CDT include the necessary tools and integrations. If yours does -not, the base CDT does provide support for integration with the GNU tools for build and debug. Please see the -Before you begin section for installation instructions

- -Before you begin
-
-Getting Started
-Concepts
-Tasks
-Reference
-
-What's new
-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_nav.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_nav.htm deleted file mode 100644 index 7d02f027365..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_nav.htm +++ /dev/null @@ -1,29 +0,0 @@ - - - - - - -Navigation Aids - - - - -
-

Navigation Aids

-

This section provides information on navigating through the C/C++ Perspective.

- Outline View
- Project File views
- C/C++ Search
- Open Declaration
- -

IBM Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/customBuildCallbacks.xml b/debug/org.eclipse.cdt.debug.application.doc/customBuildCallbacks.xml deleted file mode 100644 index 53a5bbd0435..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/customBuildCallbacks.xml +++ /dev/null @@ -1,163 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/debug/org.eclipse.cdt.debug.application.doc/html/maintopic.html b/debug/org.eclipse.cdt.debug.application.doc/html/maintopic.html deleted file mode 100644 index a476078ace4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/html/maintopic.html +++ /dev/null @@ -1,13 +0,0 @@ - - - - - - Main Topic - - - -

Main Topic

-Please enter your text here. - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/html/subtopic.html b/debug/org.eclipse.cdt.debug.application.doc/html/subtopic.html deleted file mode 100644 index 8a61c501d6a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/html/subtopic.html +++ /dev/null @@ -1,13 +0,0 @@ - - - - - - Sub Topic - - - -

Sub Topic

-Please enter your text here. - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/html/toc.html b/debug/org.eclipse.cdt.debug.application.doc/html/toc.html deleted file mode 100644 index 326f0a9ff3c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/html/toc.html +++ /dev/null @@ -1,13 +0,0 @@ - - - - - - Table of Contents - - - -

Table of Contents

-Please enter your text here. - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/add_breakpoint.png b/debug/org.eclipse.cdt.debug.application.doc/images/add_breakpoint.png deleted file mode 100644 index f8196f53020..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/add_breakpoint.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/alphab_sort_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/alphab_sort_co.gif deleted file mode 100644 index 6d772441d0d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/alphab_sort_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/btn_columns.png b/debug/org.eclipse.cdt.debug.application.doc/images/btn_columns.png deleted file mode 100644 index 3833e627033..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/btn_columns.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/btn_import_executables.png b/debug/org.eclipse.cdt.debug.application.doc/images/btn_import_executables.png deleted file mode 100644 index ae639c2fa1e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/btn_import_executables.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/btn_restart.png b/debug/org.eclipse.cdt.debug.application.doc/images/btn_restart.png deleted file mode 100644 index a161f8522f0..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/btn_restart.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/builder_settings.png b/debug/org.eclipse.cdt.debug.application.doc/images/builder_settings.png deleted file mode 100644 index 526e58fe3f9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/builder_settings.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/c_cpp_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/c_cpp_preferences.png deleted file mode 100644 index d744b925748..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/c_cpp_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/c_element_filters.png b/debug/org.eclipse.cdt.debug.application.doc/images/c_element_filters.png deleted file mode 100644 index f282d48e112..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/c_element_filters.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/c_exe_obj.png b/debug/org.eclipse.cdt.debug.application.doc/images/c_exe_obj.png deleted file mode 100644 index 9f89f36da17..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/c_exe_obj.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/c_file_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/c_file_obj.gif deleted file mode 100644 index bd603cff7a2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/c_file_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/c_object_file.png b/debug/org.eclipse.cdt.debug.application.doc/images/c_object_file.png deleted file mode 100644 index 29c5bb72797..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/c_object_file.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/c_ovr.gif b/debug/org.eclipse.cdt.debug.application.doc/images/c_ovr.gif deleted file mode 100644 index f4496021a73..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/c_ovr.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/c_paths.png b/debug/org.eclipse.cdt.debug.application.doc/images/c_paths.png deleted file mode 100644 index 3c1d51c7ade..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/c_paths.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_autobuild.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_autobuild.png deleted file mode 100644 index 85e53202698..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_autobuild.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_buildenv_newenvvar.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_buildenv_newenvvar.png deleted file mode 100644 index 0bec0a2f6af..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_buildenv_newenvvar.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_buildenv_selectvar.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_buildenv_selectvar.png deleted file mode 100644 index f18ef803c7b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_buildenv_selectvar.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_ca_no_completions.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_ca_no_completions.png deleted file mode 100644 index 623e2005595..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_ca_no_completions.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_bp_filter.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_bp_filter.png deleted file mode 100644 index ce5f16c7392..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_bp_filter.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes01.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes01.png deleted file mode 100644 index 16cb90d5eca..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes01.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes02.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes02.png deleted file mode 100644 index f1854831ac2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes02.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes03.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes03.png deleted file mode 100644 index 615a4d7dea2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes03.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes04.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes04.png deleted file mode 100644 index 057916c770b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes04.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes05.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes05.png deleted file mode 100644 index b6c958213ff..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes05.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_hover_modes.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_hover_modes.png deleted file mode 100644 index 3b3b885a6d2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_hover_modes.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_run01.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_run01.png deleted file mode 100644 index a208560ce3d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_run01.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_dlg_define_build_var.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_dlg_define_build_var.png deleted file mode 100644 index 9190d6ea25a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_dlg_define_build_var.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_dlg_edit_build_var.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_dlg_edit_build_var.png deleted file mode 100644 index 049a6e3cc52..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_dlg_edit_build_var.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_dsfgdb_preferences_page.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_dsfgdb_preferences_page.png deleted file mode 100644 index 0d2ec5e54c0..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_dsfgdb_preferences_page.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_error_workbench.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_error_workbench.png deleted file mode 100644 index f2b1f8e9267..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_error_workbench.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_inc.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_inc.png deleted file mode 100644 index 34064a3ce34..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_inc.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_steps.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_steps.png deleted file mode 100644 index 373e77abd02..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_steps.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_sym.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_sym.png deleted file mode 100644 index 5106e6c7fcc..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_sym.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_toolsett.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_toolsett.png deleted file mode 100644 index 4f635421f7e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_toolsett.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_fold_resource.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_fold_resource.png deleted file mode 100644 index 7f6a74e59ee..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_fold_resource.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_fold_toolsett.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_fold_toolsett.png deleted file mode 100644 index 9d2c58addf5..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_fold_toolsett.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_inline_rename.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_inline_rename.png deleted file mode 100644 index 44047e88db8..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_inline_rename.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_menu_toggle_comments.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_menu_toggle_comments.png deleted file mode 100644 index 524c13a74ec..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_menu_toggle_comments.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_menubar.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_menubar.png deleted file mode 100644 index 44a91de3a73..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_menubar.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_new_brk_action.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_new_brk_action.png deleted file mode 100644 index 7d186805056..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_new_brk_action.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_open_element.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_open_element.png deleted file mode 100644 index 4f6307c519a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_open_element.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-multi-cfg.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-multi-cfg.png deleted file mode 100644 index ad7a53afb5a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-multi-cfg.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-prop-pages.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-prop-pages.png deleted file mode 100644 index e6312702060..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-prop-pages.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-wizard-defaults.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-wizard-defaults.png deleted file mode 100644 index dfbbd0516e9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-wizard-defaults.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-wizard-toolchains.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-wizard-toolchains.png deleted file mode 100644 index f8d4aa698f5..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-wizard-toolchains.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_brk_action.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_brk_action.png deleted file mode 100644 index 2ce105461ed..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_brk_action.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_brk_action_properties.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_brk_action_properties.png deleted file mode 100644 index 7f113aadb1d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_brk_action_properties.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_build_console.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_build_console.png deleted file mode 100644 index c254fff19ab..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_build_console.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_build_vars.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_build_vars.png deleted file mode 100644 index 850d2eb2de2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_build_vars.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_file_types.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_file_types.png deleted file mode 100644 index e65ff03cd9e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_file_types.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_new_task_tag_dlg.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_new_task_tag_dlg.png deleted file mode 100644 index 2235581638e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_new_task_tag_dlg.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_task_tags.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_task_tags.png deleted file mode 100644 index e7299985c19..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_task_tags.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_refactor.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_refactor.png deleted file mode 100644 index 22a4375c9ca..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_refactor.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_rename_dialog.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_rename_dialog.png deleted file mode 100644 index 4be0a7d5ff5..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_rename_dialog.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_select_type.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_select_type.png deleted file mode 100644 index c143d88b76d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_select_type.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_set_src_folder.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_set_src_folder.png deleted file mode 100644 index 406a2df6538..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_set_src_folder.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_1.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_1.png deleted file mode 100644 index 08c9d7dbca3..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_1.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_2.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_2.png deleted file mode 100644 index 3fe998ade0a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_2.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_3.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_3.png deleted file mode 100644 index 0850083f0c7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_3.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_4.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_4.png deleted file mode 100644 index f67b3352fe3..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_4.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_5.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_5.png deleted file mode 100644 index 4918ac1d02f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_5.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_6.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_6.png deleted file mode 100644 index ba3fd341ebc..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_proj_new_with_template_6.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_toggle_selection.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_toggle_selection.png deleted file mode 100644 index 5f68cbc0aee..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_toggle_selection.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_toggle_selection2.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_toggle_selection2.png deleted file mode 100644 index 1831f1f276d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_toggle_selection2.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_toggle_selection3.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_toggle_selection3.png deleted file mode 100644 index 00a6913dedd..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_t_toggle_selection3.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_toolbar.png b/debug/org.eclipse.cdt.debug.application.doc/images/cdt_toolbar.png deleted file mode 100644 index 4c23103af2d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/cdt_toolbar.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/class_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/class_obj.gif deleted file mode 100644 index 6279478c51b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/class_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/code_style_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/code_style_preferences.png deleted file mode 100644 index 333d16d75a3..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/code_style_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/code_templates.png b/debug/org.eclipse.cdt.debug.application.doc/images/code_templates.png deleted file mode 100644 index eae5d39f033..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/code_templates.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/code_templates_new.png b/debug/org.eclipse.cdt.debug.application.doc/images/code_templates_new.png deleted file mode 100644 index 622b125f0f8..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/code_templates_new.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/codetemplates_example.png b/debug/org.eclipse.cdt.debug.application.doc/images/codetemplates_example.png deleted file mode 100644 index 8cb7ff0d044..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/codetemplates_example.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/command_link.png b/debug/org.eclipse.cdt.debug.application.doc/images/command_link.png deleted file mode 100644 index 28ced874ea8..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/command_link.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/console_build.png b/debug/org.eclipse.cdt.debug.application.doc/images/console_build.png deleted file mode 100644 index 00442e80653..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/console_build.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/container_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/container_obj.gif deleted file mode 100644 index d90a51c0220..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/container_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/contentAssist_adv_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/contentAssist_adv_preferences.png deleted file mode 100644 index a16a70165ee..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/contentAssist_adv_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/contentAssist_example.png b/debug/org.eclipse.cdt.debug.application.doc/images/contentAssist_example.png deleted file mode 100644 index 61021414b28..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/contentAssist_example.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/contentAssist_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/contentAssist_preferences.png deleted file mode 100644 index e82399fc0e1..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/contentAssist_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/convert_proj.png b/debug/org.eclipse.cdt.debug.application.doc/images/convert_proj.png deleted file mode 100644 index 10de9a70363..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/convert_proj.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/create_make_target.png b/debug/org.eclipse.cdt.debug.application.doc/images/create_make_target.png deleted file mode 100644 index 929061a8c24..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/create_make_target.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/create_make_target_win.png b/debug/org.eclipse.cdt.debug.application.doc/images/create_make_target_win.png deleted file mode 100644 index d47c50532a5..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/create_make_target_win.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/customize_perspective.png b/debug/org.eclipse.cdt.debug.application.doc/images/customize_perspective.png deleted file mode 100644 index cc8e556fd5f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/customize_perspective.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/debug_pref.png b/debug/org.eclipse.cdt.debug.application.doc/images/debug_pref.png deleted file mode 100644 index 45cfa3d7bf7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/debug_pref.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/debug_src_path_mapping.png b/debug/org.eclipse.cdt.debug.application.doc/images/debug_src_path_mapping.png deleted file mode 100644 index 2aec2603279..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/debug_src_path_mapping.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/debug_src_pref.png b/debug/org.eclipse.cdt.debug.application.doc/images/debug_src_pref.png deleted file mode 100644 index ad7730a482a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/debug_src_pref.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/define_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/define_obj.gif deleted file mode 100644 index 87d583e1dd3..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/define_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/discovery_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/discovery_preferences.png deleted file mode 100644 index 7efe392b4d9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/discovery_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/dprop_make_discovery_file.png b/debug/org.eclipse.cdt.debug.application.doc/images/dprop_make_discovery_file.png deleted file mode 100644 index 8cc935e77d7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/dprop_make_discovery_file.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/edited_ovr.gif b/debug/org.eclipse.cdt.debug.application.doc/images/edited_ovr.gif deleted file mode 100644 index f272e8c7321..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/edited_ovr.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/editor_c_codetemplates_use.png b/debug/org.eclipse.cdt.debug.application.doc/images/editor_c_codetemplates_use.png deleted file mode 100644 index 06a03fc2c30..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/editor_c_codetemplates_use.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/editor_color_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/editor_color_preferences.png deleted file mode 100644 index 888b89f7f71..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/editor_color_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/editor_folding_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/editor_folding_preferences.png deleted file mode 100644 index c3eb6e98e2b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/editor_folding_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/editor_general_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/editor_general_preferences.png deleted file mode 100644 index 1ebb1bea8b0..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/editor_general_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/editor_hover_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/editor_hover_preferences.png deleted file mode 100644 index d33d29295ef..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/editor_hover_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/editor_mark_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/editor_mark_preferences.png deleted file mode 100644 index 5ec7a3b77bd..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/editor_mark_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/editor_save_actions_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/editor_save_actions_preferences.png deleted file mode 100644 index 90391346f16..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/editor_save_actions_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/editor_scalability_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/editor_scalability_preferences.png deleted file mode 100644 index 529f94196c8..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/editor_scalability_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/editor_typing_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/editor_typing_preferences.png deleted file mode 100644 index 5da772cfde0..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/editor_typing_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/enum_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/enum_obj.gif deleted file mode 100644 index a441bef7dc2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/enum_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/enumerator_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/enumerator_obj.gif deleted file mode 100644 index ec911412eff..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/enumerator_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/error_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/error_co.gif deleted file mode 100644 index 119dcccd5a7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/error_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/field_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/field_obj.gif deleted file mode 100644 index 240749472c6..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/field_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/field_private_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/field_private_obj.gif deleted file mode 100644 index 567c7786e3c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/field_private_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/field_protected_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/field_protected_obj.gif deleted file mode 100644 index 4234e04bba6..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/field_protected_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/field_public_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/field_public_obj.gif deleted file mode 100644 index 63a390c8326..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/field_public_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/fields_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/fields_co.gif deleted file mode 100644 index e14ce565b4f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/fields_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/file_menu.png b/debug/org.eclipse.cdt.debug.application.doc/images/file_menu.png deleted file mode 100644 index 85972352369..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/file_menu.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/file_new_conv.png b/debug/org.eclipse.cdt.debug.application.doc/images/file_new_conv.png deleted file mode 100644 index e6d4efd513a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/file_new_conv.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/fileprop_language_mappings.png b/debug/org.eclipse.cdt.debug.application.doc/images/fileprop_language_mappings.png deleted file mode 100644 index 141cca65290..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/fileprop_language_mappings.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/find_replace_dialog.png b/debug/org.eclipse.cdt.debug.application.doc/images/find_replace_dialog.png deleted file mode 100644 index 97e73ca6942..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/find_replace_dialog.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/function_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/function_obj.gif deleted file mode 100644 index 92075a8a352..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/function_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/hierarchy_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/hierarchy_co.gif deleted file mode 100644 index 45b6b132268..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/hierarchy_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/history_list.gif b/debug/org.eclipse.cdt.debug.application.doc/images/history_list.gif deleted file mode 100644 index 364c0e70b1d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/history_list.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_add_mem_monitor.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_add_mem_monitor.png deleted file mode 100644 index 1f9218ccfea..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_add_mem_monitor.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_annotation_next.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_annotation_next.png deleted file mode 100644 index 69c09556f06..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_annotation_next.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_annotation_prev.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_annotation_prev.png deleted file mode 100644 index ff1378e80e5..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_annotation_prev.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_back.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_back.png deleted file mode 100644 index a64dbbc19e4..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_back.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_breakpoint_disable.gif b/debug/org.eclipse.cdt.debug.application.doc/images/icon_breakpoint_disable.gif deleted file mode 100644 index 7d190f165d0..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_breakpoint_disable.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_breakpoint_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/icon_breakpoint_obj.gif deleted file mode 100644 index 06d007905b2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_breakpoint_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_build_make_target.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_build_make_target.png deleted file mode 100644 index acc6050601d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_build_make_target.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_clear_console.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_clear_console.png deleted file mode 100644 index 12fc6d11bae..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_clear_console.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_collapse_all.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_collapse_all.png deleted file mode 100644 index 349d4ead802..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_collapse_all.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_disp_console.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_disp_console.png deleted file mode 100644 index 4f5bf01ddf3..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_disp_console.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_max.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_max.png deleted file mode 100644 index 748b94f9975..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_max.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_min.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_min.png deleted file mode 100644 index 23f67fc0049..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_min.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_pin.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_pin.png deleted file mode 100644 index 20a31aae06f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_pin.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_rem_all_term.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_rem_all_term.png deleted file mode 100644 index 8b85f300b47..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_rem_all_term.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_scroll_lock.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_scroll_lock.png deleted file mode 100644 index 61266355b14..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_scroll_lock.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_terminate.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_terminate.png deleted file mode 100644 index 6b0c4a414fb..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_con_terminate.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_copy_to_clipboard.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_copy_to_clipboard.png deleted file mode 100644 index 177d228de90..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_copy_to_clipboard.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_copy_stack.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_copy_stack.png deleted file mode 100644 index 4c018d1ed10..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_copy_stack.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_debug.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_debug.png deleted file mode 100644 index 2637d2a1976..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_debug.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_drop_to_frame.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_drop_to_frame.png deleted file mode 100644 index d5c9d707fda..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_drop_to_frame.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_launch_instance.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_launch_instance.png deleted file mode 100644 index 1c3b22f55eb..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_launch_instance.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_restart.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_restart.png deleted file mode 100644 index 6af462ebb80..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_restart.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_resume.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_resume.png deleted file mode 100644 index 2b2372eba58..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_resume.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stack_frame.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stack_frame.png deleted file mode 100644 index e5ffd063e9e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stack_frame.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_step_mode.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_step_mode.png deleted file mode 100644 index 23104c5795b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_step_mode.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stepinto.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stepinto.png deleted file mode 100644 index 839bd1f2ee9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stepinto.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stepover.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stepover.png deleted file mode 100644 index 4498b2f4d1d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stepover.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stepreturn.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stepreturn.png deleted file mode 100644 index ae4e0428fda..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_stepreturn.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_suspend.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_suspend.png deleted file mode 100644 index 882c8c4a44f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_suspend.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate.png deleted file mode 100644 index 4679b93757a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_all.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_all.png deleted file mode 100644 index ae8f92c79b8..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_all.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_all2.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_all2.png deleted file mode 100644 index b10ae9d3ca5..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_all2.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_relaunch.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_relaunch.png deleted file mode 100644 index 88712aa9e72..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_relaunch.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_remove.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_remove.png deleted file mode 100644 index 592ae953956..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_terminate_remove.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_use_step_filters.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_use_step_filters.png deleted file mode 100644 index 7940cd9a65b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_db_use_step_filters.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_debug.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_debug.png deleted file mode 100644 index 7228e2c3fe2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_debug.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_debugt_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/icon_debugt_obj.gif deleted file mode 100644 index d139cde9dd4..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_debugt_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_disconnect.gif b/debug/org.eclipse.cdt.debug.application.doc/images/icon_disconnect.gif deleted file mode 100644 index f1d5fb31e51..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_disconnect.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_edit_make_target.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_edit_make_target.png deleted file mode 100644 index 6107ff02908..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_edit_make_target.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_error.gif b/debug/org.eclipse.cdt.debug.application.doc/images/icon_error.gif deleted file mode 100644 index 2cd37c2548e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_error.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_expand_all.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_expand_all.png deleted file mode 100644 index ce2626a43bd..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_expand_all.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_forward.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_forward.png deleted file mode 100644 index 00f4fcbd2fc..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_forward.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_inactive_includes.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_inactive_includes.png deleted file mode 100644 index 8725dfe1ab5..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_inactive_includes.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_make_targets.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_make_targets.png deleted file mode 100644 index 41c10268273..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_make_targets.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_sys_includes.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_sys_includes.png deleted file mode 100644 index 05902bf3986..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_sys_includes.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_variables_more.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_variables_more.png deleted file mode 100644 index 2fa91d342ec..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_hide_variables_more.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_home.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_home.png deleted file mode 100644 index 4dde23152d1..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_home.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_info.gif b/debug/org.eclipse.cdt.debug.application.doc/images/icon_info.gif deleted file mode 100644 index 745b884ff03..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_info.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_last_edit_loc.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_last_edit_loc.png deleted file mode 100644 index 37afeaf07c9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_last_edit_loc.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_link_mem_rendering.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_link_mem_rendering.png deleted file mode 100644 index 7e56e3059a9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_link_mem_rendering.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_link_with_editor.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_link_with_editor.png deleted file mode 100644 index 229b72b7c1e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_link_with_editor.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_load_all_modules.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_load_all_modules.png deleted file mode 100644 index 86d532ddfb7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_load_all_modules.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_menu.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_menu.png deleted file mode 100644 index 2309096651a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_menu.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_menu_white.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_menu_white.png deleted file mode 100644 index 43bf94ae0c1..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_menu_white.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_new_make_target.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_new_make_target.png deleted file mode 100644 index e813698f13a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_new_make_target.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_new_memory_view.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_new_memory_view.png deleted file mode 100644 index 2ceac484b32..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_new_memory_view.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_next.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_next.png deleted file mode 100644 index ffe567acea5..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_next.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_next_error.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_next_error.png deleted file mode 100644 index bc8f3d7273b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_next_error.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_open_console.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_open_console.png deleted file mode 100644 index 5e6881240ef..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_open_console.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_open_element.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_open_element.png deleted file mode 100644 index 2a81e195c57..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_open_element.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_pin.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_pin.png deleted file mode 100644 index 1125cde1181..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_pin.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_pin_memory.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_pin_memory.png deleted file mode 100644 index 4e061e0bcea..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_pin_memory.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_prev_error.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_prev_error.png deleted file mode 100644 index 5008ac79867..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_prev_error.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_previous.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_previous.png deleted file mode 100644 index a28d38a8463..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_previous.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_refresh_view_contents.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_refresh_view_contents.png deleted file mode 100644 index f38eecc63f4..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_refresh_view_contents.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_cast_to_type.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_cast_to_type.png deleted file mode 100644 index 1c212946f4e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_cast_to_type.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_change_value.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_change_value.png deleted file mode 100644 index f48aab8884c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_change_value.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_copy_registers.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_copy_registers.png deleted file mode 100644 index 01b5f3e2860..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_copy_registers.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_create_watch_expr.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_create_watch_expr.png deleted file mode 100644 index 9498b71aa69..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_create_watch_expr.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_disable.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_disable.png deleted file mode 100644 index 54fd32b7a3f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_disable.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_display_array.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_display_array.png deleted file mode 100644 index 6610c96f57e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_display_array.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_enable.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_enable.png deleted file mode 100644 index dc35833e1a2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reg_enable.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_remove.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_remove.png deleted file mode 100644 index b18352b718f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_remove.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_repeat_search.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_repeat_search.png deleted file mode 100644 index dde5909d205..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_repeat_search.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reset_mem_monitor.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_reset_mem_monitor.png deleted file mode 100644 index 6b959506a2d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_reset_mem_monitor.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_resume_at_line.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_resume_at_line.png deleted file mode 100644 index 7d6ecfc8384..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_resume_at_line.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_resume_signal.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_resume_signal.png deleted file mode 100644 index b38dede9c7d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_resume_signal.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_run.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_run.png deleted file mode 100644 index 53bdc58a96c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_run.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_run_to_line.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_run_to_line.png deleted file mode 100644 index 38b038d1926..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_run_to_line.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_save_output_file.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_save_output_file.png deleted file mode 100644 index e0142150fc4..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_save_output_file.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_search.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_search.png deleted file mode 100644 index a5612ded300..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_search.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_callees.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_callees.png deleted file mode 100644 index b2d60af4864..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_callees.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_callers.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_callers.png deleted file mode 100644 index d01117ed579..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_callers.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_error.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_error.png deleted file mode 100644 index a2e6b313fe0..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_error.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_history_list.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_history_list.png deleted file mode 100644 index 09f66df68ff..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_history_list.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_logical_struct.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_logical_struct.png deleted file mode 100644 index d15fc83e792..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_logical_struct.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_next_reference.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_next_reference.png deleted file mode 100644 index 688ca3fde99..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_next_reference.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_prev_reference.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_prev_reference.png deleted file mode 100644 index 1de1ccd3aca..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_prev_reference.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_prev_search.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_prev_search.png deleted file mode 100644 index f8026985901..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_prev_search.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_type_names.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_type_names.png deleted file mode 100644 index d5f12fb7772..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_show_type_names.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_switch_mem_monitor.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_switch_mem_monitor.png deleted file mode 100644 index dcaa093081c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_switch_mem_monitor.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_thread1.gif b/debug/org.eclipse.cdt.debug.application.doc/images/icon_thread1.gif deleted file mode 100644 index 7e4a43cd78c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_thread1.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_thread2.gif b/debug/org.eclipse.cdt.debug.application.doc/images/icon_thread2.gif deleted file mode 100644 index fb5175f5c68..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_thread2.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_thread3.gif b/debug/org.eclipse.cdt.debug.application.doc/images/icon_thread3.gif deleted file mode 100644 index f2a16394e6d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_thread3.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_toggle_memory_monitor.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_toggle_memory_monitor.png deleted file mode 100644 index 1c5983aee67..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_toggle_memory_monitor.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_toggle_split_pane.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_toggle_split_pane.png deleted file mode 100644 index bfea8457511..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_toggle_split_pane.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_up.png b/debug/org.eclipse.cdt.debug.application.doc/images/icon_up.png deleted file mode 100644 index d1869d2b5a9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_up.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/icon_warning.gif b/debug/org.eclipse.cdt.debug.application.doc/images/icon_warning.gif deleted file mode 100644 index 1e5f5eb367c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/icon_warning.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/inactive_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/inactive_co.gif deleted file mode 100644 index d03b6a99d68..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/inactive_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/include_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/include_obj.gif deleted file mode 100644 index 1855ca9e20e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/include_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/indexedFile.gif b/debug/org.eclipse.cdt.debug.application.doc/images/indexedFile.gif deleted file mode 100644 index 9b4c11c4572..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/indexedFile.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/indexer_preference_page.png b/debug/org.eclipse.cdt.debug.application.doc/images/indexer_preference_page.png deleted file mode 100644 index 19b9b3e660b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/indexer_preference_page.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/installed_ovr.gif b/debug/org.eclipse.cdt.debug.application.doc/images/installed_ovr.gif deleted file mode 100644 index 899610a858b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/installed_ovr.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/intl_05.gif b/debug/org.eclipse.cdt.debug.application.doc/images/intl_05.gif deleted file mode 100644 index 7399ac410d1..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/intl_05.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/intl_07.gif b/debug/org.eclipse.cdt.debug.application.doc/images/intl_07.gif deleted file mode 100644 index dfa08425906..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/intl_07.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/make_settings_prefs.png b/debug/org.eclipse.cdt.debug.application.doc/images/make_settings_prefs.png deleted file mode 100644 index 5fe338c8596..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/make_settings_prefs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/make_targets.png b/debug/org.eclipse.cdt.debug.application.doc/images/make_targets.png deleted file mode 100644 index 9875ceb6a32..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/make_targets.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/makefile.gif b/debug/org.eclipse.cdt.debug.application.doc/images/makefile.gif deleted file mode 100644 index 7afb4948ba7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/makefile.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/makefile_editor_folding_prefs.png b/debug/org.eclipse.cdt.debug.application.doc/images/makefile_editor_folding_prefs.png deleted file mode 100644 index 57362ecd77f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/makefile_editor_folding_prefs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/makefile_editor_prefs.png b/debug/org.eclipse.cdt.debug.application.doc/images/makefile_editor_prefs.png deleted file mode 100644 index baaa0a5f617..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/makefile_editor_prefs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/manage_defined_symbols.png b/debug/org.eclipse.cdt.debug.application.doc/images/manage_defined_symbols.png deleted file mode 100644 index 649d56e384c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/manage_defined_symbols.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/mark_occurrences.png b/debug/org.eclipse.cdt.debug.application.doc/images/mark_occurrences.png deleted file mode 100644 index 6cef6c72c3e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/mark_occurrences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/method_private_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/method_private_obj.gif deleted file mode 100644 index 75bfeb8cfa6..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/method_private_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/method_protected_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/method_protected_obj.gif deleted file mode 100644 index 563743d393f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/method_protected_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/method_public_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/method_public_obj.gif deleted file mode 100644 index 7d24707ee82..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/method_public_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/mfile_build.PNG b/debug/org.eclipse.cdt.debug.application.doc/images/mfile_build.PNG deleted file mode 100644 index 2efed6e7869..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/mfile_build.PNG and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/mfile_build_rcbs.png b/debug/org.eclipse.cdt.debug.application.doc/images/mfile_build_rcbs.png deleted file mode 100644 index cc6ba2cfd92..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/mfile_build_rcbs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/mfile_info.PNG b/debug/org.eclipse.cdt.debug.application.doc/images/mfile_info.PNG deleted file mode 100644 index aef7171ac6d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/mfile_info.PNG and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/mpref.png b/debug/org.eclipse.cdt.debug.application.doc/images/mpref.png deleted file mode 100644 index ecc5cf7ec9d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/mpref.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/mpref_discovopts.png b/debug/org.eclipse.cdt.debug.application.doc/images/mpref_discovopts.png deleted file mode 100644 index caf74ec2129..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/mpref_discovopts.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/mpref_macro.PNG b/debug/org.eclipse.cdt.debug.application.doc/images/mpref_macro.PNG deleted file mode 100644 index 2e8941a8b9e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/mpref_macro.PNG and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/mpref_toolchain.png b/debug/org.eclipse.cdt.debug.application.doc/images/mpref_toolchain.png deleted file mode 100644 index 62d82208e63..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/mpref_toolchain.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/mprop_refactoring_history.png b/debug/org.eclipse.cdt.debug.application.doc/images/mprop_refactoring_history.png deleted file mode 100644 index 506915f6758..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/mprop_refactoring_history.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/namespace_declared_obj.png b/debug/org.eclipse.cdt.debug.application.doc/images/namespace_declared_obj.png deleted file mode 100644 index 0dd626ecc25..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/namespace_declared_obj.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/namespace_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/namespace_obj.gif deleted file mode 100644 index c70cce0ecdf..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/namespace_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_make-behavior.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_make-behavior.png deleted file mode 100644 index a88c7719ee2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_make-behavior.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_make-binary_parser.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_make-binary_parser.png deleted file mode 100644 index 4ac3fd615a7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_make-binary_parser.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_make-builder.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_make-builder.png deleted file mode 100644 index f00244c9bec..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_make-builder.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_make-error_parser.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_make-error_parser.png deleted file mode 100644 index 55c487cdb9d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_make-error_parser.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_make_disc_options.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_make_disc_options.png deleted file mode 100644 index 9ea934786ee..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_make_disc_options.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_convert.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_convert.png deleted file mode 100644 index 32b6dab45ce..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_convert.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_convert_candidate.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_convert_candidate.png deleted file mode 100644 index 2b9dd856496..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_convert_candidate.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_config.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_config.png deleted file mode 100644 index ad81aea0d7f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_config.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_name.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_name.png deleted file mode 100644 index 2f0c46eea14..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_name.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_toolchain.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_toolchain.png deleted file mode 100644 index aa0b1ee7ac6..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_toolchain.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_type.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_type.png deleted file mode 100644 index f6d3cecbb89..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_proj_wz_type.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/new_project_wizard.png b/debug/org.eclipse.cdt.debug.application.doc/images/new_project_wizard.png deleted file mode 100644 index 68ba7e97b51..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/new_project_wizard.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/ng00_04a.gif b/debug/org.eclipse.cdt.debug.application.doc/images/ng00_04a.gif deleted file mode 100644 index c5ebdbf97cd..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/ng00_04a.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/ng00_05a.gif b/debug/org.eclipse.cdt.debug.application.doc/images/ng00_05a.gif deleted file mode 100644 index aaaab23c08c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/ng00_05a.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/ng00_07.gif b/debug/org.eclipse.cdt.debug.application.doc/images/ng00_07.gif deleted file mode 100644 index 6a0de57b071..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/ng00_07.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/ng03_04.gif b/debug/org.eclipse.cdt.debug.application.doc/images/ng03_04.gif deleted file mode 100644 index df5c0a3b5df..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/ng03_04.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/ngconcepts.gif b/debug/org.eclipse.cdt.debug.application.doc/images/ngconcepts.gif deleted file mode 100644 index c304d54745a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/ngconcepts.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/ngref.gif b/debug/org.eclipse.cdt.debug.application.doc/images/ngref.gif deleted file mode 100644 index c113299234b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/ngref.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/ngtasks.gif b/debug/org.eclipse.cdt.debug.application.doc/images/ngtasks.gif deleted file mode 100644 index 2a3a7110634..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/ngtasks.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/nokiaCopyright.png b/debug/org.eclipse.cdt.debug.application.doc/images/nokiaCopyright.png deleted file mode 100644 index 4a7958868ee..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/nokiaCopyright.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/openDeclaration.png b/debug/org.eclipse.cdt.debug.application.doc/images/openDeclaration.png deleted file mode 100644 index ee3d69ec82e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/openDeclaration.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/open_declaration_error.png b/debug/org.eclipse.cdt.debug.application.doc/images/open_declaration_error.png deleted file mode 100644 index 5860b37e15f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/open_declaration_error.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/outlineView.png b/debug/org.eclipse.cdt.debug.application.doc/images/outlineView.png deleted file mode 100644 index 6a2c58c667b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/outlineView.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/path_inherit_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/path_inherit_co.gif deleted file mode 100644 index 85e21898780..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/path_inherit_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/pref_panel_build.png b/debug/org.eclipse.cdt.debug.application.doc/images/pref_panel_build.png deleted file mode 100644 index e035b7aca87..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/pref_panel_build.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/pref_panel_code_templates.png b/debug/org.eclipse.cdt.debug.application.doc/images/pref_panel_code_templates.png deleted file mode 100644 index 6715294bc23..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/pref_panel_code_templates.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/pref_panel_edit_template_dlg.png b/debug/org.eclipse.cdt.debug.application.doc/images/pref_panel_edit_template_dlg.png deleted file mode 100644 index e04f709e1c4..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/pref_panel_edit_template_dlg.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/pref_traditional_memory_prefs.png b/debug/org.eclipse.cdt.debug.application.doc/images/pref_traditional_memory_prefs.png deleted file mode 100644 index 17a1783ab6d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/pref_traditional_memory_prefs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/progress_stop.gif b/debug/org.eclipse.cdt.debug.application.doc/images/progress_stop.gif deleted file mode 100644 index dc47edf0695..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/progress_stop.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/project_new_cppfile.png b/debug/org.eclipse.cdt.debug.application.doc/images/project_new_cppfile.png deleted file mode 100644 index b267152b34b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/project_new_cppfile.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/project_new_file.png b/debug/org.eclipse.cdt.debug.application.doc/images/project_new_file.png deleted file mode 100644 index 300f29fbf8e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/project_new_file.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/project_new_file_name.png b/debug/org.eclipse.cdt.debug.application.doc/images/project_new_file_name.png deleted file mode 100644 index 5fb029e387d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/project_new_file_name.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/project_new_makefile.png b/debug/org.eclipse.cdt.debug.application.doc/images/project_new_makefile.png deleted file mode 100644 index 0795992740c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/project_new_makefile.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/project_rename.png b/debug/org.eclipse.cdt.debug.application.doc/images/project_rename.png deleted file mode 100644 index e998ae1feef..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/project_rename.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/projects_filters.png b/debug/org.eclipse.cdt.debug.application.doc/images/projects_filters.png deleted file mode 100644 index 4c30f0287d8..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/projects_filters.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/projects_properties.png b/debug/org.eclipse.cdt.debug.application.doc/images/projects_properties.png deleted file mode 100644 index e3ee4388ca4..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/projects_properties.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_artifact.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_artifact.png deleted file mode 100644 index 08833ad29b0..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_artifact.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_bin.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_bin.png deleted file mode 100644 index 9dec92f9223..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_bin.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders.png deleted file mode 100644 index b13c0870088..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders_editbldr.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders_editbldr.png deleted file mode 100644 index 487fcc37be6..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders_editbldr.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders_imprtlnchcnfg.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders_imprtlnchcnfg.png deleted file mode 100644 index 8872fd0a930..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders_imprtlnchcnfg.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders_newbldr.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders_newbldr.png deleted file mode 100644 index cdd5c1b7ef8..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_builders_newbldr.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_cbuild.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_cbuild.png deleted file mode 100644 index dd3a7a477fa..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_cbuild.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_cbuild2.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_cbuild2.png deleted file mode 100644 index a8734b24818..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_cbuild2.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_cbuild_selbldvar.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_cbuild_selbldvar.png deleted file mode 100644 index d0e1407751b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_cbuild_selbldvar.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_cfgs.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_cfgs.png deleted file mode 100644 index 3f3f965ab19..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_cfgs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_crefs.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_crefs.png deleted file mode 100644 index 8b00965c192..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_crefs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_doc.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_doc.png deleted file mode 100644 index c4f7570208e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_doc.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_environment.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_environment.png deleted file mode 100644 index 86d4672794e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_environment.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_error.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_error.png deleted file mode 100644 index 9daaa437d09..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_error.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_exp.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_exp.png deleted file mode 100644 index 3055c05d5fd..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_exp.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_file_lang.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_file_lang.png deleted file mode 100644 index d4955157278..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_file_lang.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_ftypes.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_ftypes.png deleted file mode 100644 index 8f156b84ca9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_ftypes.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_general.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_general.png deleted file mode 100644 index 38335cf416e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_general.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_inc.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_inc.png deleted file mode 100644 index 4a1e1e593fd..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_inc.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_index.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_index.png deleted file mode 100644 index 5ebe8a627f2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_index.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_lang.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_lang.png deleted file mode 100644 index b842fc6060c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_lang.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_lib.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_lib.png deleted file mode 100644 index accc73cf82c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_lib.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_libpath.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_libpath.png deleted file mode 100644 index 200d6f11a43..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_libpath.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_mng_add.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_mng_add.png deleted file mode 100644 index b530fe04423..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_mng_add.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_mng_dialog.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_mng_dialog.png deleted file mode 100644 index a706473b5d5..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_mng_dialog.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_mng_rename.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_mng_rename.png deleted file mode 100644 index 92f43f4205c..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_mng_rename.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_outloc.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_outloc.png deleted file mode 100644 index 430de894cfb..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_outloc.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_refs.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_refs.png deleted file mode 100644 index 4f081afd1b9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_refs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_resource.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_resource.png deleted file mode 100644 index 96139bd17ec..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_resource.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_rundeb.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_rundeb.png deleted file mode 100644 index 3541515aa39..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_rundeb.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_srcloc.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_srcloc.png deleted file mode 100644 index 80eac73c05a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_srcloc.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_steps.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_steps.png deleted file mode 100644 index 3b68d33bade..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_steps.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_symb.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_symb.png deleted file mode 100644 index df2d72f8d0d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_symb.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_tool.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_tool.png deleted file mode 100644 index 42650d6c51e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_tool.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_tree.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_tree.png deleted file mode 100644 index 6edf8991a89..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_tree.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/prop_variables.png b/debug/org.eclipse.cdt.debug.application.doc/images/prop_variables.png deleted file mode 100644 index da12969851e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/prop_variables.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/public_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/public_co.gif deleted file mode 100644 index 18103b11fc7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/public_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/ref-79.gif b/debug/org.eclipse.cdt.debug.application.doc/images/ref-79.gif deleted file mode 100644 index 7ef1a62ba7d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/ref-79.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/refresh_nav.gif b/debug/org.eclipse.cdt.debug.application.doc/images/refresh_nav.gif deleted file mode 100644 index 3ca04d06ff9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/refresh_nav.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/rh03_04.gif b/debug/org.eclipse.cdt.debug.application.doc/images/rh03_04.gif deleted file mode 100644 index 5a49b645267..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/rh03_04.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_arguments.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_arguments.png deleted file mode 100644 index 9c3e28422af..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_arguments.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_common.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_common.png deleted file mode 100644 index 3de5b7bd39b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_common.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_common_folder.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_common_folder.png deleted file mode 100644 index 017bd390987..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_common_folder.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_config.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_config.png deleted file mode 100644 index 20b25d19757..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_config.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_arguments.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_arguments.png deleted file mode 100644 index f7049ffcb98..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_arguments.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_common.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_common.png deleted file mode 100644 index c9b4b6da5f7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_common.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_debugger.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_debugger.png deleted file mode 100644 index 80420ed2bda..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_debugger.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_debugger_advopt.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_debugger_advopt.png deleted file mode 100644 index 9beda0ef400..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_debugger_advopt.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_environment.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_environment.png deleted file mode 100644 index 8ab6cffde07..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_environment.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_launch_group.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_launch_group.png deleted file mode 100644 index 0ee298125a7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_launch_group.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_launch_group_edit.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_launch_group_edit.png deleted file mode 100644 index d047c6cbfc9..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_launch_group_edit.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_main.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_main.png deleted file mode 100644 index c35be7b5de3..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_main.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_source.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_source.png deleted file mode 100644 index b72c14175eb..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_debug_source.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_debugger.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_debugger.png deleted file mode 100644 index b7fc2bb5c01..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_debugger.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/run_environment.png b/debug/org.eclipse.cdt.debug.application.doc/images/run_environment.png deleted file mode 100644 index 5459d7d5319..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/run_environment.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_cfg_disc.png b/debug/org.eclipse.cdt.debug.application.doc/images/scanner_cfg_disc.png deleted file mode 100644 index 96963a4723f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_cfg_disc.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_bop_options.png b/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_bop_options.png deleted file mode 100644 index 925e1420ba7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_bop_options.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_console_view.png b/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_console_view.png deleted file mode 100644 index f308a2a1318..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_console_view.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_preferences.png b/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_preferences.png deleted file mode 100644 index ca563394d86..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_preferences.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_add_include.png b/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_add_include.png deleted file mode 100644 index e604bdcee40..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_add_include.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_add_lse_kinds_dropdown.png b/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_add_lse_kinds_dropdown.png deleted file mode 100644 index a580d3c044a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_add_lse_kinds_dropdown.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_add_lse_paths_dropdown.png b/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_add_lse_paths_dropdown.png deleted file mode 100644 index 42f7a0f42e3..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_add_lse_paths_dropdown.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_entries.png b/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_entries.png deleted file mode 100644 index c7468381b10..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_entries.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_providers.png b/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_providers.png deleted file mode 100644 index b6033f76069..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_prop_providers.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_specs_detector_options.png b/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_specs_detector_options.png deleted file mode 100644 index 8e74aeb5460..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/scanner_discovery/sd_specs_detector_options.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/search.png b/debug/org.eclipse.cdt.debug.application.doc/images/search.png deleted file mode 100644 index dd79fdecc9e..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/search.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/searchView.png b/debug/org.eclipse.cdt.debug.application.doc/images/searchView.png deleted file mode 100644 index 8b5f16252d8..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/searchView.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/selection_search.png b/debug/org.eclipse.cdt.debug.application.doc/images/selection_search.png deleted file mode 100644 index 0f603136dd3..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/selection_search.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/setting_nav.gif b/debug/org.eclipse.cdt.debug.application.doc/images/setting_nav.gif deleted file mode 100644 index f25aa532b1f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/setting_nav.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/show_view.png b/debug/org.eclipse.cdt.debug.application.doc/images/show_view.png deleted file mode 100644 index 6796eaa7b7b..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/show_view.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/standalone_debugger.png b/debug/org.eclipse.cdt.debug.application.doc/images/standalone_debugger.png deleted file mode 100644 index 11cb8e88d6f..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/standalone_debugger.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/static_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/static_co.gif deleted file mode 100644 index 10d08aeff73..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/static_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/struct_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/struct_obj.gif deleted file mode 100644 index 5db2efa2516..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/struct_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/sub_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/sub_co.gif deleted file mode 100644 index 54871df5aa6..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/sub_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/super_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/super_co.gif deleted file mode 100644 index 59ac11633f2..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/super_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/task_binary_parser.png b/debug/org.eclipse.cdt.debug.application.doc/images/task_binary_parser.png deleted file mode 100644 index b55a5a74644..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/task_binary_parser.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/task_binary_pref.png b/debug/org.eclipse.cdt.debug.application.doc/images/task_binary_pref.png deleted file mode 100644 index fdd8fc45e44..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/task_binary_pref.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/template_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/template_obj.gif deleted file mode 100644 index c0d9d95c268..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/template_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/trans.gif b/debug/org.eclipse.cdt.debug.application.doc/images/trans.gif deleted file mode 100644 index 16d98433d00..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/trans.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/typedef_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/typedef_obj.gif deleted file mode 100644 index 9d6df6acc62..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/typedef_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/union_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/union_obj.gif deleted file mode 100644 index df0f59fdf10..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/union_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/update_managed_build.png b/debug/org.eclipse.cdt.debug.application.doc/images/update_managed_build.png deleted file mode 100644 index 1b4b6395405..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/update_managed_build.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/update_managed_build20.png b/debug/org.eclipse.cdt.debug.application.doc/images/update_managed_build20.png deleted file mode 100644 index 0008109113a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/update_managed_build20.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/var_declaration_obj.gif b/debug/org.eclipse.cdt.debug.application.doc/images/var_declaration_obj.gif deleted file mode 100644 index 91c4c93ab51..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/var_declaration_obj.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_add_mapping.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_add_mapping.png deleted file mode 100644 index 9908b8cf5d6..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_add_mapping.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_appearance_prefs.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_appearance_prefs.png deleted file mode 100644 index a9fabf38b1d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_appearance_prefs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_call_hierarchy.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_call_hierarchy.png deleted file mode 100644 index 5e7d19ae682..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_call_hierarchy.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_console.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_console.png deleted file mode 100644 index e9e37b978b4..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_console.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_debug.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_debug.png deleted file mode 100644 index a458dad1550..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_debug.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_debug_breadcrumb.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_debug_breadcrumb.png deleted file mode 100644 index 90d7fea278a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_debug_breadcrumb.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_debug_prefs.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_debug_prefs.png deleted file mode 100644 index f7b4f3e43f6..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_debug_prefs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_dissassembly.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_dissassembly.png deleted file mode 100644 index c8f4f8474fa..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_dissassembly.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_editor.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_editor.png deleted file mode 100644 index 9374ea8ffba..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_editor.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_environment_prefs.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_environment_prefs.png deleted file mode 100644 index e1aa99d7535..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_environment_prefs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_executables.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_executables.png deleted file mode 100644 index ab178e5c633..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_executables.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_include_browser.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_include_browser.png deleted file mode 100644 index 8c7179e66d7..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_include_browser.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_language_mappings_prefs.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_language_mappings_prefs.png deleted file mode 100644 index 55f871307fc..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_language_mappings_prefs.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_make_targets.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_make_targets.png deleted file mode 100644 index 4ea803abcaa..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_make_targets.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_memory.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_memory.png deleted file mode 100644 index b7dc77c0297..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_memory.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_modules.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_modules.png deleted file mode 100644 index 004fa6e3d13..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_modules.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_navigator.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_navigator.png deleted file mode 100644 index 59f9611d083..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_navigator.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_problem.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_problem.png deleted file mode 100644 index 4b4b383df3d..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_problem.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_project_explorer.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_project_explorer.png deleted file mode 100644 index ca205622fb4..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_project_explorer.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_projects.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_projects.png deleted file mode 100644 index edb26a269b4..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_projects.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_properties.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_properties.png deleted file mode 100644 index 2504de730e4..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_properties.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_registers.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_registers.png deleted file mode 100644 index 1554f0a8b99..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_registers.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_signals.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_signals.png deleted file mode 100644 index 66836489150..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_signals.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/view_table_rendering.png b/debug/org.eclipse.cdt.debug.application.doc/images/view_table_rendering.png deleted file mode 100644 index d085966e167..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/view_table_rendering.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/warning_co.gif b/debug/org.eclipse.cdt.debug.application.doc/images/warning_co.gif deleted file mode 100644 index ee2dac4a90a..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/warning_co.gif and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/window_customize_perspective.png b/debug/org.eclipse.cdt.debug.application.doc/images/window_customize_perspective.png deleted file mode 100644 index add42681d49..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/window_customize_perspective.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/images/workbench_prop.png b/debug/org.eclipse.cdt.debug.application.doc/images/workbench_prop.png deleted file mode 100644 index e7105692af3..00000000000 Binary files a/debug/org.eclipse.cdt.debug.application.doc/images/workbench_prop.png and /dev/null differ diff --git a/debug/org.eclipse.cdt.debug.application.doc/notices.html b/debug/org.eclipse.cdt.debug.application.doc/notices.html deleted file mode 100644 index af4b9ab03cd..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/notices.html +++ /dev/null @@ -1,24 +0,0 @@ - - - - - - Legal Notices - - -
-

-Notices

-

-The material in this guide is Copyright (c) IBM Corporation and others -2004, 2010. -

-

-Terms and conditions regarding the use of this -guide. -

-
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/plugin.properties b/debug/org.eclipse.cdt.debug.application.doc/plugin.properties deleted file mode 100644 index 20f43afd2ca..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/plugin.properties +++ /dev/null @@ -1,15 +0,0 @@ -################################################################################# -# Copyright (c) 2014 Red Hat, Inc. -# -# This program and the accompanying materials -# are made available under the terms of the Eclipse Public License 2.0 -# which accompanies this distribution, and is available at -# https://www.eclipse.org/legal/epl-2.0/ -# -# SPDX-License-Identifier: EPL-2.0 -# -# Contributors: -# Red Hat Incorporated - initial API and implementation -################################################################################# -bundleName=C/C++ Stand-alone Debugger Documentation -provider=Eclipse CDT diff --git a/debug/org.eclipse.cdt.debug.application.doc/plugin.xml b/debug/org.eclipse.cdt.debug.application.doc/plugin.xml deleted file mode 100644 index 38affa2bb32..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/plugin.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - - - - - - - - diff --git a/debug/org.eclipse.cdt.debug.application.doc/pom.xml b/debug/org.eclipse.cdt.debug.application.doc/pom.xml deleted file mode 100644 index 968e51288af..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/pom.xml +++ /dev/null @@ -1,124 +0,0 @@ - - - - 4.0.0 - - - org.eclipse.cdt - cdt-parent - 11.6.0-SNAPSHOT - ../../pom.xml - - - 11.6.0-SNAPSHOT - org.eclipse.cdt.debug.application.doc - eclipse-plugin - - - - - org.eclipse.tycho - tycho-source-plugin - - - plugin-source - none - - - attach-source - none - - - - - - - - - build-doc - - - !skipDoc - - - - - - org.eclipse.tycho.extras - tycho-eclipserun-plugin - - - -application - org.eclipse.ant.core.antRunner - -buildfile - customBuildCallbacks.xml - build.index - - - - org.apache.ant - eclipse-plugin - - - org.eclipse.help.base - eclipse-plugin - - - org.eclipse.ant.core - eclipse-plugin - - - - - - - eclipse-run - - compile - - - - - - - - fake-doc - - - skipDoc - - - - - - maven-antrun-plugin - - - compile - - - - - - - run - - - - - - - - - - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_ceditor_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_ceditor_pref.htm deleted file mode 100644 index 7606aa07820..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_ceditor_pref.htm +++ /dev/null @@ -1,33 +0,0 @@ - - - - - - - C/C++ editor preferences - - - - - -

C/C++ editor preferences

- -

This section describes how to set preferences for the C/C++ editor.

- - General preferences
- Content Assist preferences
-     Advanced preferences
- Folding preferences
- Hovers preferences
- Mark Occurrences preferences
- Save Actions preferences
- Scalability preferences
- Syntax Coloring preferences
- Templates preferences
- Typing preferences - -

IBM Copyright Statement

- - -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_dbg_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_dbg_view.htm deleted file mode 100644 index dcfda0acf28..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_dbg_view.htm +++ /dev/null @@ -1,30 +0,0 @@ - - - - - - -Debug views - - - - - -

Debug views

- -

This section describes debug views.

- - Registers view
- Memory view
- Traditional Memory Rendering preferences
- Disassembly view
- Modules view
- Signals view
- Debug view
- Debug preferences
- -

IBM Copyright Statement

- -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_menu.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_menu.htm deleted file mode 100644 index cf8c06c8508..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_menu.htm +++ /dev/null @@ -1,22 +0,0 @@ - - - - - - -C/C++ Menubar - - - - -

Menubar

-

This section describes the menubar options available from the Stand-alone Debugger.

-

-

- - -

IBM Copyright Statement -

-
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_mproj_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_mproj_pref.htm deleted file mode 100644 index 60eb5fd6a68..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_mproj_pref.htm +++ /dev/null @@ -1,26 +0,0 @@ - - - - - - -Project properties - - - - - -

Managed Make Project preferences

-

Customizes the managed make project settings for the -entire workspace.

-

-Managed Build preference page

-

The following settings may be customized:

- -

Intel Copyright Statement

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_mproj_pref_macro.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_mproj_pref_macro.htm deleted file mode 100644 index c5692a16222..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_mproj_pref_macro.htm +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - -Project properties - - - - - -

Managed Make Project preferences, Build Macros

-

Customizes the build macros for all managed make projects in the workspace.

-

-Managed Build Macros Preference page

-

You can add, remove and edit build macros that apply to all managed make projects in the workspace.  -Two tables are displayed - one for user-defined build macros and one for non user-defined build macros.  -Each table contains three columns:

-

Name of the build macro

-

Type of value contained in the build macro (see below)

-

Value of the build macro. 

-

You can view all build macros that are not user-defined in the System - Macros table.

-

You can view all user-defined macros in the User - Macros table. A user-defined macro overrides a non user-defined macro of the same - name.  Overridden macros are displayed in bold in - the System Macros table.

-

Intel Copyright Statement

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_new_mproj.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_new_mproj.htm deleted file mode 100644 index 893fe8ede21..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_new_mproj.htm +++ /dev/null @@ -1,25 +0,0 @@ - - - - - - -C/C++ New Project Wizard, Managed Make Project - - - - - -

C/C++ New Project Wizard, Managed Make Project

-

This section describes properties for creating a Managed make project in the C/C++ New Project Wizard.

- Name
- Select a -Project Type
- Referenced Projects
- C/C++ Indexer
- - -

IBM Copyright Statement

- -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_new_sproj.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_new_sproj.htm deleted file mode 100644 index 4f6d95f3b21..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_new_sproj.htm +++ /dev/null @@ -1,26 +0,0 @@ - - - - - - -C/C++ New Project Wizard, Standard Make Project - - - - - -

C/C++ New Project Wizard, Standard Make Project

-

This section describes properties for creating a Standard make project in the C/C++ New Project Wizard.

- Name
- Referenced Projects
- Make Builder
- Error Parsers
- Binary Parser
- Discovery Options
- C/C++ Indexer
- -

IBM Copyright Statement

- -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_proj_prop_pages.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_proj_prop_pages.htm deleted file mode 100644 index c9950c52934..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_proj_prop_pages.htm +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - -New CDT Project Wizard - - - - - -

New CDT Project Wizard

-

In this section, learn about the C/C++ New CDT Project Wizard.

- -

New CDT Project Wizard preferences
- Makefile Project preferences
- Binary Parsers preferences
- Error Parsers preferences
- Discovery Options preferences
- Builder Settings preferences
- Behavior preferences
-

-

Nokia Copyright Statement
-IBM Copyright Statement

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_prop_file.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_prop_file.htm deleted file mode 100644 index 4229841d386..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_prop_file.htm +++ /dev/null @@ -1,28 +0,0 @@ - - - - - - -C/C++ File Properties - - - - - -

C/C++ File Properties

-

This section describes properties for a Source Files in C/C++ project

- -

Intel Copyright Statement

- -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_prop_folder.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_prop_folder.htm deleted file mode 100644 index 09546de277b..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_prop_folder.htm +++ /dev/null @@ -1,36 +0,0 @@ - - - - - - -C/C++ Folder Properties - - - - - -

C/C++ Folder Properties

-

This section describes properties for a C/C++ project Folder

- -

Intel Copyright Statement

- -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_prop_proj.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_prop_proj.htm deleted file mode 100644 index 07b8cf65f88..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_prop_proj.htm +++ /dev/null @@ -1,59 +0,0 @@ - - - - - - -Project Properties - - - - - -

Project Properties

-

This section describes C/C++ Project Properties. -To select project properties, right click a project and select Properties.

- -

Related concepts
-C/C++ projects

- - -

Related reference
- -

-

-

Intel Copyright Statement

- - -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_ref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_ref.htm deleted file mode 100644 index 31ff2d2cc07..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_ref.htm +++ /dev/null @@ -1,115 +0,0 @@ - - - - - - -Reference - - - - -

Reference

-

This section describes the Views, Windows, Dialog Boxes, and Preference Panels available from the C/C++ perspective.

- -

C/C++ Views and Editors
- Selecting Views and Editors
- Console view
- C/C++ Projects view
- Editor view
- Executables view
- Project Explorer view
- Outline view
- Make Targets view
- Problems view
- Tasks view
- Properties view
- C/C++ Icons
- Debug Views
- Registers view
- Memory view
- Traditional Memory Rendering preferences
- Modules view
- Signals view
- Debug view
- Debug preferences
- Menubar
- File Menu actions
- Edit Menu actions
- Refactor Menu actions
- Navigate Menu actions
- Search Menu actions
- Project Menu actions
- Run Menu actions
- Window Menu actions
- C/C++ Toolbar
- Open Element
- Create a Make Target
- Find/Replace
- C/C++ Preferences
- Appearance
- Build preferences
- Error Parsers Options
- Build Variables
- Console
- Environment
- Make Targets
- Makefile Editor
- Settings
- Code Style preferences
- Code Templates
- - Debug preferences
- Breakpoint Actions
- Source Lookup Path
- GDB Debugging
- - Editor preferences
- Content Assist
- Advanced
- Folding
- Hovers
- Mark Occurrences
- Save Actions
- Scalability
- Syntax Coloring
- Templates
- Typing
- File Types
- Indexer
- Language Mappings
- - New CDT Project Wizard preferences
- Makefile Project
- Binary Parser
- Error Parsers
- Discovery Options
- Builder Settings
- Behavior
- - Property Pages Settings
- Multi-Configuration Edit
- - Task Tags
- -
- C/C++ Properties
- C/C++ Project Properties
- C/C++ Folder Properties
- C/C++ File Properties
- C/C++ New Project Wizard
- C/C++ Run and Debug
- Main
- Arguments
- Environment
- Debugger
- Source
- Common
- C/C++ search
-

-

IBM Copyright Statement
- Nokia Copyright Statement
-

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_run_dbg_pages.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_run_dbg_pages.htm deleted file mode 100644 index e7978333d1a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_run_dbg_pages.htm +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - -Run and Debug dialog boxes - - - - - -

Run and Debug

- -

Types of Launch configurations supported by C/C++

- C/C++ Local Application - run application on local host
- C/C++ Attach to Local Application - attach to already running application on the local host
- C/C++ Postmortem debugger - run debugger on "core" file
- Launch Group - launch multiple applications
-

Launch Configurations common tabs

- Main
- Arguments
- Environment
- Debugger
- Source
- Common
- -

IBM Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_views.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_views.htm deleted file mode 100644 index 69f311ea35e..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_o_views.htm +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - -C/C++ Views and Editors - - - - - -

C/C++ Views and Editors

-

This section describes C/C++ views and editors.

- - Selecting Views and Editors
- C/C++ Projects view
- Project Explorer view
- Navigator view
- Outline view
- - Editor view
- Executables view
- Console view
- Call Hierarchy view
- Type Hierarchy view
- Problems view
- Tasks view
- Properties view
- Search view
- Debug views
- Registers view
- Memory view
- Traditional Memory Rendering preferences
- Disassembly view
- Modules view
- Signals view
- Debug view
- Debug preferences
- C/C++ Icons
- -

IBM Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_appearance_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_appearance_pref.htm deleted file mode 100644 index d91759b2631..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_appearance_pref.htm +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - -Appearance preferences - - - - - - -

Appearance preferences

- -

Use the Appearance panel of the Preferences window to customize the appearance of C elements in the viewers. Click Window > Preferences > C/C++ > Appearance to open.

-

Appearance Preference

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Appearance Options -
OptionDescription
Show translation unit members Select this option to show translation unit members in the Project Explorer and C/C++ Projects views.
Group include directives in Project Explorer and C/C++ Projects view Select this option to group include directives in the Project Explorer and C/C++ Projects views.
Group include directives in the Outline view Select this option to group include directives in the Outline view.
Group namespaces in the Outline view Select this option to group namespace declarations in the Outline view.
Group method definitions in the Outline view Select this option to group method definitions for the same type in the Outline view.
Group macro definitions in the Project Explorer and C/C++ Project views.Select this option to group method definitions for the same type in the Project Explorer and C/C++ Project views.
Group macro definitions in the Outline view.Select this option to group macro definitions in the Outline view.
Sort header files before source files in Project Explorer and C/C++ Projects view Select this option to separate header and source files in the Project Explorer and C/C++ Projects views.
Show source roots at top of projectSelect this option to group source roots at the top of project views.
- -

Nokia Copyright Statement

-
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_code_style_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_code_style_pref.htm deleted file mode 100644 index ce3bf383019..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_code_style_pref.htm +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - Code Style preferences - - - - - -

Code Style preferences

- -

Use the Code Style preference panel to configure your global code style profiles for smart typing features, like auto-indentation and formatting. Click Window > Preferences > C/C++ > Code Style to make changes.

-

Code Style Preferences

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Code Style Preference Options
OptionDescription
- Configure Project Specific Settings... - - Opens the Project Specific Configuration dialog box to select a project to apply code style settings. -
- Edit... - - Shows a dialog which displays the settings stored in the active profile. Only user-defined profiles can be modified. -
- Remove - - Removes the selected profile. This action is only available on user-defined profiles. -
- New... - - Shows the dialog to create a new profile. The dialog requires you to enter a name for the new profile. Additionally, you may select a built-in or user-defined existing profile to base your new profile on. -
- Import... - - Imports profiles from the file system. -
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor
-

Related reference -
-C/C++ editor preferences

-IBM Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_code_templates_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_code_templates_pref.htm deleted file mode 100644 index 7172549b879..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_code_templates_pref.htm +++ /dev/null @@ -1,327 +0,0 @@ - - - - - - - Code templates - - - - - -

- Code templates -

-

The - -Code Templates preference panel lets you configure the format of newly generated code stubs, comments and files.

-

Code Templates Preferences Window

- -

The code templates page contains templates that are used by actions that generate code and/or source files. -E.g. the New Class wizard uses source and header file templates to create new files and code templates to insert generated method stubs. -Templates contain variables that are substituted when the template is applied. Some variables are available in all templates, some are specific to templates.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Options - - Description -
- New... - -

Opens the Code Template dialog to create a new file template.

-
- Edit... - -

Opens the Code Template dialog to edit the currently selected code template.

-
- Remove - -

Removes a user added file template. Predefined templates cannot be removed.

-
- Import... - -

Imports templates from the file system.

-
- Export... - -

Exports all selected templates to the file system.

-
- Export All... - -

Exports all templates to the file system.

-
- - -

Comment Templates

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Template Name - - Specifies -
- Files - -

Header comment for new source or header files.

-

Note that this template can be referenced in source and header file templates with ${filecomment}.

-
- Types - -

The comment for new types.

-

Note that this template can be referenced in source and header file templates with ${typecomment}.

-
- Fields - -

The comment for new fields.

-
- Constructors - -

The comment for new constructors.

-
- Destructors - -

The comment for new destructors.

-
- Methods - -

The comment for new methods.

-
- -

Code Templates

-
- - - - - - - - - - - - - - - - - - - - -
- Template Name - - Description -
- Method body - -

The 'Method body' templates are used when new method is created.

-
- Constructor body - -

The 'Constructor body' templates are used when a constructor is created.

-
- Destructor body - -

The 'Destructor body' templates are used when the destructor is created.

-
- -

File Templates

-File templates can not only be defined and modified for C/C++ files, but also for other content types, like Assembly files or plain text files. -The New File from Template wizard can be used to create new files based on one of the templates defined in this page. -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Template Name - - Description -
- Default C++ source template - -

Used by the New Class wizard and the New Source File wizard when a new C++ source file is created.

-

The template can specify where comments are added. Note that the template can contain the variable ${typecomment} and ${filecomment} that will be substituted by the evaluation of the Types respectively Files comment template.

-
- Default C++ header template - -

Used by the New Class wizard and the New Header File wizard when a new C++ header file is created.

-

The template can specify where comments are added. Note that the template can contain the variable ${typecomment} and ${filecomment} that will be substituted by the evaluation of the Types respectively Files comment template.

-
- Default C source template - -

Used by the New Source File wizard when a new C source file is created.

-

The template can specify where comments are added. Note that the template can contain the variable ${typecomment} and ${filecomment} that will be substituted by the evaluation of the Types respectively Files comment template.

-
- Default C header template - -

Used by the New Header File wizard when a new C source file is created.

-

The template can specify where comments are added. Note that the template can contain the variable ${typecomment} and ${filecomment} that will be substituted by the evaluation of the Types respectively Files comment template.

-
- Other file templates - -

File templates can be defined for other content types, e.g. Assembly or plain text.

-
- -

Edit Template dialog

-

Edit Template Dialog Box

- -

The following fields and buttons appear in the dialog:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Options - -

Description

-
- Name - -

The name of the template. Only available for file templates.

-
- Type - -

The file type (content type) of the template. Only available for file templates.

-
- Description - -

A description of the template

-
- Pattern - -

The template pattern.

-
- Insert Variables... - -

Displays a list of pre-defined template specific variables.

-
- -

Related concepts
-Coding aids

-

Related reference -
-C/C++ editor preferences

-IBM Copyright Statement - -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_color.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_color.htm deleted file mode 100644 index 22f42c5b90e..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_color.htm +++ /dev/null @@ -1,77 +0,0 @@ - - - - - - - Syntax Coloring preferences - - - - - - -

Syntax Coloring preferences

- -

Use the Syntax Coloring preference panel to specify how C/C++ source code is rendered. Each element category (Code, Comments, and Preprocessor) contains a list of language elements that may be rendered with its own color and style.

-

Note that general text editor settings such as the background color can be configured on the general Text Editors preference pages. Fonts may be configured on the general Colors and Fonts preference page

-

Syntax Coloring Preferences Page

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Syntax Coloring Preference Options
OptionDescription
Enable semantic highlightingCheckmark to activate semantic highlighting of specific structures in the elements listed.
EnableMakes the selected element active for syntax coloring.
ColorSpecifies the color in which to display the selected element.
BoldMakes the selected element bold.
ItalicMakes the selected element italic.
StrikethroughMakes the selected element strikethrough.
UnderlineMakes the selected element underlined.
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor

-

Related reference -
-C/C++ editor preferences

-
-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_con_assist.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_con_assist.htm deleted file mode 100644 index 05476bf8e60..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_con_assist.htm +++ /dev/null @@ -1,77 +0,0 @@ - - - - - - - Content Assist preferences - - - - - -

Content Assist preferences

- -

Use the Content Assist panel to customize the Content Assist feature in C/C++ editors.

-

Content Assist Preferences Dialog Box

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Content Assist Preference Options
OptionDescription
Insert single proposals automaticallyInserts an element into your code when the Content Assist feature finds only one proposal.
Insert common prefixes automaticallyInserts common prefixes.
Completion Proposal FilterCompletion proposal filters may have been supplied with your Eclipse application. - Completion proposal filters can sort and order the proposals provided by the Content Assist feature to best suit your needs. - Select the desired content assist filter from the list of available filters.
Enable "." as triggerEnable to use "." as a trigger for auto-completion.
Enable "->" as triggerEnable to use "->" as a trigger for auto-completion.
Enable "::" as triggerEnable to use "::" as a trigger for auto-completion.
delay (ms)Specifies the number of milliseconds before Content Assist is activated.
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor
-Working with Content Assist

-

Related reference -
-C/C++ editor preferences

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_con_assist_adv.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_con_assist_adv.htm deleted file mode 100644 index de97d0b9307..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_con_assist_adv.htm +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - - Advanced preferences - - - - - -

Advanced preferences

- -

Use the Advanced panel in the Preferences window to configure the behavior of the Content Assist (Ctrl+Space) command.

-

Content Assist Preferences Dialog Box

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Advanced Content Assist Preference Options
OptionDescription
Default Proposal KindsSpecifies the types of proposals Content Assist uses and the key bindings assigned.
Content Assist CyclingSpecifies the order and types of proposals Content Assist will cycle through.
UpMoves the selected proposal item up in the cycling list.
DownMoves the selected proposal item down in the cycling list.
Timeout for each proposal kind (ms)Specifies the number of milliseconds a code completion proposal kind is allowed to compute - proposals. If it takes more time then it is assumed that this proposal kind is faulty. - In this case a dialog is opened and an appropriate message is shown to the user
If the value is 0 each completion - proposal can compute as long as it needs to before being assumed to be faulty.
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor
-Working with Content Assist

-

Related reference -
-C/C++ editor preferences

-IBM Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_folding.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_folding.htm deleted file mode 100644 index 8ca3d5755d2..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_folding.htm +++ /dev/null @@ -1,100 +0,0 @@ - - - - - - - Folding preferences - - - - - -

Folding preferences

- -

Use the Folding preference panel to customize the C/C++ editor folding behavior.

-

Editor Folding Preferences Window

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Folding Preference Options
OptionDescriptionDefault
Enable folding when opening a new editorIf enabled, apply folding rules to the new editor. 
Select folding to useSelect the folding to use from the available choices. 
Enable folding of preprocessor branches (#if/#endif)If enabled, fold preprocessor branches. 
Enable folding of control flow statements (if/else, do/while, for, switch)If enabled, fold control flow statements. 
MacrosIf enabled, fold macro definitions.On
FunctionsIf enabled, fold functions.Off
MethodsIf enabled, fold methods.Off
StructuresIf enabled, fold structures.On
CommentsIf enabled, fold comments.Off
Header CommentsIf enabled, fold header comments.On
Inactive Preprocessor BranchesIf enabled, fold inactive processor branches.On
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor

-

Related reference -
-C/C++ editor preferences

-IBM Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_gen.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_gen.htm deleted file mode 100644 index a004422136c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_gen.htm +++ /dev/null @@ -1,104 +0,0 @@ - - - - - -Editor preferences - - - - -
-

Editor preferences

-

- Use the command linkEditor preference panel to control the - appearance of text highlighting in C/C++ editors. -

-

- Editor Preferences Panel -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OptionDescription
Smart caret - positioning in identifiersTreats CamelCase identifiers as - being made up of separate words.
Report problems as - you typeProblems found will be immediately - highlighted in the editor.
Highlight matching - bracketsWhen the cursor is beside a bracket, - the matching bracket is highlighted.
Highlight inactive - codeHighlights inactive code when the - cursor is positioned inside it.
Appearance color - optionsLists the items for which you can - specify a color.
ColorSpecifies the color in which to - display the selected item.
Documentation tool - commentsSpecifies which documentation tool - should be used to determine editor presentation and behaviors. - This enables editor features such as content-assist, documentation - comment generation and syntax highlighting. The particular tool - selected here will be used for files that are not associated with - a project, or where no project level preference has been set.
- -

- Related concepts
Coding aids -

-

- Related tasks
Customizing the C/C++ - editor -

-

- Related reference
C/C++ - editor preferences -

-
- IBM Copyright Statement -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_hov.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_hov.htm deleted file mode 100644 index 1497669e64f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_hov.htm +++ /dev/null @@ -1,64 +0,0 @@ - - - - - - - Hover preferences - - - - - -

Hovers preferences

- -

Use the Hovers preference panel to customize the C/C++ editor hover behavior.

-

Editor Hover Preferences Panel

- - - - - - - - - - - - - - - - - - - - - - - - - - -
Hovers Preference Options
OptionDescription
Enable editor problem annotationWhen selected problems found will be highlighted in the editor.
Text Hover key modifier preferencesYou can select hot-keys to enable alternate hover behavior. For example, a mouse over while pressing the <Ctrl> key will link to the element's source declaration.
Pressed key modifier while hoveringEnter a key modifier for the selected hover name.
- -
-
-
-
-
-
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor

-

Related reference -
-C/C++ editor preferences

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_mark_occurrences.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_mark_occurrences.htm deleted file mode 100644 index 3323d3dbb9f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_mark_occurrences.htm +++ /dev/null @@ -1,61 +0,0 @@ - - - - - -Mark Occurrences preferences - - - - - -

Mark Occurrences preferences

-

Use the Mark Occurrences preference panel to set annotations for the C/C++ Editor view.

-

Mark Occurrences Preference Panel

- - - - - - - - - - - - - - - - - - - - - - -
Mark Occurrences Preference Options
OptionDescriptionDefault
- Mark occurrences of the selected element in the current file - - If enabled, then you'll see within a file, where a variable, function, method, type, macro or other element is referenced. - - On -
- Keep marks when the selection changes - - If enabled, don't change the location of the mark occurrence when a new selection is made. - - On -
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor

-

Related reference -
-C/C++ editor preferences

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_save_actions.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_save_actions.htm deleted file mode 100644 index 04483eaec55..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_save_actions.htm +++ /dev/null @@ -1,57 +0,0 @@ - - - - - - - Editor preferences - - - - - -

Save actions

- -

Use the Save Actions preference panel to configure actions performed by the C/C++ editor while saving a file.

-

Save Actions Preferences

- - - - - - - - - - - - - - - - - - - - - - - -
Save Actions Preference Options
OptionDescription
Remove trailing whitespaceWhile saving a file, C/C++ editor will remove spaces and tab characters from the end of edited - or all lines.
Ensure newline at the end of fileWhile saving a file, C/C++ editor will insert a newline at the end of the last line, - if the last line does not have it already.
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor

-

Related reference -
-C/C++ editor preferences

-
-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_scalability.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_scalability.htm deleted file mode 100644 index bd2fb26d32c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_scalability.htm +++ /dev/null @@ -1,83 +0,0 @@ - - - - - - - Editor Scalability preferences - - - - - -

Scalability preferences

- -

Use the Scalability preference panel to configure options for dealing with large source files.

-

Scalability Preferences

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Scalability Preference Options
OptionDescription
Alert me when scalability mode will be turned onIf enabled, an information dialog pops up when a large file is opened - with the C/C++ Editor which exceeds the specified line limit.
Enable scalability mode options when the number of lines in the file is more thanIf the number of lines in a file exceeds the specified number the C/C++ Editor will - enable scalability mode and all scalability mode options below will take effect.
Enable all scalability mode optionsIf enabled, all options below are enabled, too.
Disable editor live parsingIf enabled, parsing while typing will be disabled. - This disables also other features like Outline view, semantic highlighting, folding, etc.
Disable semantic highlightingIf enabled, C/C++ identifiers will not be colored.
Disable syntax coloringIf enabled, no coloring of keywords, comments and literals is done.
Disable parsing-based content assist proposalsIf enabled, content assist proposals which require parsing the file will not be available.
Disable content assist auto-activationIf enabled, content assist will not be activated automatically on trigger sequences, like '.', '::' or '->'.
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor
-Working with Content Assist

-

Related reference -
-C/C++ editor preferences

-Code Style preferences

-IBM Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_typing.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_typing.htm deleted file mode 100644 index 4ffc6217287..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_editor_typing.htm +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - - Typing preferences - - - - - -

Typing preferences

- -

Use the Typing preference panel to assist in formatting input as you type.

-

Typing Preferences

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Typing Preference Options
OptionDescription
"Strings"If enabled, automatically close string quotes.
(Parenthesis) and [square] bracketsIf enabled, automatically close parenthesis and square brackets.
<Angle> bracketsIf enabled, automatically close angle brackets.
{Braces}If enabled, automatically close curly braces.
Tab key adjusts indentation of the current lineIf enabled, indent the current line when the tab key is pressed.
Adjust indentationAdjust the indentation of pasted text to match the current indentation level.
Wrap automaticallyEnable to automatically wrap string literals when they exceed the max line length.
Escape text when pasting into a literal stringIf enabled, special characters in pasted strings are escaped when pasted into an existing string literal.
New lines and bracesIf enabled, a new line or brace will be indented according to the Code Style preferences. - If disabled, the default Text Editor indentation strategy is applied (copy indent from previous line)
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor
-Working with Content Assist

-

Related reference -
-C/C++ editor preferences

-Code Style preferences

-IBM Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_file_types.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_file_types.htm deleted file mode 100644 index eedccb3ae1f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_file_types.htm +++ /dev/null @@ -1,52 +0,0 @@ - - - - - - - File Types preference (C/C++) - - - - - -

File Types preference (C/C++)

- -

Use the File Types preference panel to define which file extensions are linked to specific languages.

-

File Types Preference Panel

- - - - - - - - - - - - - - - - - - - - - -
File Types Preference Options
OptionDescription
New...Add a new File Type definition.
RemoveRemove the currently selected File Type definition.
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor

-

Related reference -
-C/C++ editor preferences

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_pref.htm deleted file mode 100644 index d0c421b78e0..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_c_pref.htm +++ /dev/null @@ -1,59 +0,0 @@ - - - - - - -C/C++ Preferences - - - - - -

C/C++ Preferences

- -

The C/C++ preference panel allows you to make changes to your C/C++ environment. Click Window > Preferences > C/C++ to view.

-

C/C++ Main Preferences Window

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C/C++ Preference Options
Follow unindexed header files when producing the outline viewActivate to do a more exhaustive search of header paths to build a more complete outline view.
Build active configuration in each projectActivate to always build only the active configuration within a project.
Build all configurations in each projectActivate to always build all the configurations within a project.
Build configurations only when there are Eclipse resource changes within the project and its resourcesActivate to build only when there are have been changes to any project and Eclipse resources.
Clear all 'do not show again' settings and show all hidden dialogs againActivate to reset all alert settings and show all hidden dialogs.
- -

Related reference -
-Views

-Intel Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_call_hierarchy_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_call_hierarchy_view.htm deleted file mode 100644 index 4246b9787cb..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_call_hierarchy_view.htm +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - -Call Hierarchy view - - - - - -

Call Hierarchy view

- -

The Call Hierarchy view shows the loaded callers and callees for a selected C/C++ function. Right-click a function name in a source file and select Open Call Hierarchy to open a Call Hierarchy view, if none is open, and show the function's callers.

- -

Call Hierarchy view

- -

Call Hierarchy view toolbar commands

- -

The Call Hierarchy view toolbar commands include:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CommandNameDescription
Show Next Reference icon
Show Next ReferenceSelects the next function.
Show Previous Reference icon
Show Previous ReferenceSelects the previous function.
Hide Variables, Constants and Enumerators icon
Hide Variables, Constants and EnumeratorsToggle to show or hide all variables, constants and enumerators in the view.
Show Callers icon
Show CallersShow all callers in the search scope of the selected function.
Show Callees icon
Show CalleesShow all members called by the currently selected function.
Show History List icon
Show History ListThis menu displays a history of previously displayed call hierarchies.
Refresh View Contents icon
Refresh View ContentsRefreshes the view to reflect the current state of the function.
Pin the Call Hierarchy View icon
Pin the Call Hierarchy ViewPins the current view and enables the user to open multiple Call Hierarchy views at the same time.
Menu icon
View MenuProvides commands for:
  • Using working sets
  • -
  • Showings Callers or Callees
  • -
  • Show or hide file names
  • -
  • Activate or deactivate filters
- -

Call Hierarchy view context menu commands

- -

The Call Hierarchy view context menu commands include:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
Show ReferenceOpens an editor view containing the referenced function call.
OpenOpens an editor view containing the function reference.
Focus onResets the view to show the selected function.
Refactor...Opens the Rename global function dialog.
DeclarationsSearch the workspace, project, or working set for all function declarations and shows the result in the Search view.
ReferencesSearch the workspace, project, or working set for all function references and shows the result in the Search view.
- -

Related concepts
- Debug information

-

Related reference
- Views

-
-Nokia Copyright Statement -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_code_temp.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_code_temp.htm deleted file mode 100644 index 24baefc6832..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_code_temp.htm +++ /dev/null @@ -1,79 +0,0 @@ - - - - - - - Templates preferences - - - - - -

Templates preferences

- -

Use the Templates preference panel to manipulate any of the common predefined templates or create your own. To modify, delete, export, -import, or create your own templates click Window > Preferences > C/C++ > Templates.

-

Templates Preferences

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Templates Preference Options
OptionDescription
New...Opens the New Template dialog to create a new template.
Edit...Opens the Edit Template dialog to edit the selected template.
RemoveRemoves the selected templates from the list.
Restore RemovedRestores templates deleted by the last Remove action.
Revert to DefaultRemoves the last edits made to the selected template restoring it to it's unmodified state.
Import...Imports a template.
Export...Exports the selected templates.
Use code formatterEnable to apply the currently selected code style to the template.
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor
-Working with Content Assist

-

Related reference -
-C/C++ editor preferences

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_console_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_console_pref.htm deleted file mode 100644 index 6ed08182645..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_console_pref.htm +++ /dev/null @@ -1,93 +0,0 @@ - - - - - - -Console preferences - - - - - - -

Console preferences

- -

Use the Console preference panel to customize the appearance of messages that appear in the Console view.

-

Console Preferences Panel

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Console Preference Options
OptionDescription
Always clear console before buildingSelect this option to clear the contents of the Console view every time you perform a build.
Open console when buildingSelect this option to open the Console view when you perform a build.
Bring console to top when building (if present)Select this option to make the Console view the active window when you perform a build.
Limit console output (#lines)Specify the maximum number of lines that can display in the Console view.
Display tab widthSpecify the number of spaces for a tab.
Output text colorCustomize the color of text in the Console view.
Information message text colorCustomize the color of information text messages in the Console view.
Error message text colorCustomize the color of error messages in the Console view.
Background colorCustomize the background color in the Console view.
Background color for build problemsCustomize the background color of build problems in the Console view.
Highlighting color for build problemsCustomize the highlighting color of build problems in the Console view.
- -

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference
-Views

-
-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_console_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_console_view.htm deleted file mode 100644 index 411f5a7db95..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_console_view.htm +++ /dev/null @@ -1,147 +0,0 @@ - - - - - - -Console view - - - - -

Console view

- -

The Console view displays the output of a process and allows you to provide keyboard input to a process. There are numerous consoles available, see the Open Console dropdown list for those available to you.

-

Console View

- -The output console shows several different kinds of text, each in a different color: -

- - -

Console view toolbar

-

The table below lists the toolbar options displayed in the Console view. Note that toolbar options may differ between the various consoles.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconNameDescription
next error iconNext ErrorShow the next error in the Console view.
previous error iconPrevious ErrorShow the previous error in the Console view.
show error iconShow Error in EditorToggle to synchronize the selected error with the Editor view (default).
save output file iconCopy Build LogCopy build output to file.
Scroll Lock iconScroll LockToggles the Scroll Lock.
Clear Console iconClear ConsoleClears the current console.
Pin Console iconPin ConsoleForces the Console view to remain on top of other views in the window area.
Display Selected Console iconDisplay Selected ConsoleIf multiple consoles are open, you can select the one to display from a list.
open Console iconOpen ConsoleOpens a new console to display the log for:
-
    -
  • New Console View
  • -
  • Program Output Console
  • -
  • Windows Program Output Console
  • -
  • CVS, and others based on installed features
  • -
- -

Console view context menu

-

When you right-click in the Console view -(or when you press Shift+F10 when the focus is on the Console view), -you see one or more of the following options in a context menu depending on the console view visible: -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
ClearClears the current console.
Editor options: Cut, Copy, Paste, Select AllThese options perform the standard edit operations. Which options are available depends on where the focus is in the Console view. For example, you cannot paste text into the program output, but you can paste text to the bottom of the file.
Go to LineOpens a dialog that moves the focus to the line you specify. The dialog also indicates the total number of lines in the console buffer.
Find/Replace...Opens a Find/Replace dialog that operates only on the text in the Console view.
Open LinkSelect to follow a detected hyperlink in any console view that supports. For example, the CVS console.
Scroll LockToggles the Scroll Lock.
- -

Related references -
C/C++ Views and Editors -

-
-

-Red Hat Copyright Statement
-IBM Copyright Statement -

-
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_cproj_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_cproj_view.htm deleted file mode 100644 index 3cf4f431a47..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_cproj_view.htm +++ /dev/null @@ -1,292 +0,0 @@ - - - - - - -C/C++ Project View - - - - - -

C/C++ Projects view

-

Note: -This view is not supported anymore. It is recommended to use the Project Explorer view.

-

The C/C++ Project view displays, in a tree structure, only elements relevant to C and C++ project files, similar to the Project Explorer view. In this view you can do the following: -

- -

Files that you select in the C/C++ Projects view affect the information that is displayed in other views.

-

Right-click on any resource in the Project Explorer view to open a pop-up menu that allows you to perform operations such as copying, moving, creating new resources, comparing resources with each other, or performing team operations.

-

C/C++ Projects View

- - -

C/C++ Projects toolbar options

-

The table below lists the toolbar options displayed in the C/C++ Projects view.

- -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconNameDescription
Minimize IconMinimizeMinimizes the view.
Maximize IconMaximizeMaximizes the view.
Back IconBackThis command displays the hierarchy that was displayed immediately prior to the current display.  - For example, if you Go Into a resource, then the Back command in the resulting display returns the view to the same hierarchy from which you activated the - Go Into command. The hover help for this button tells you where it will take you. This command is similar to the Back button in a web browser.
Forward IconForwardThis command displays the hierarchy that was displayed immediately after the current display.  - For example, if you've just selected the Back command, then selecting the Forward command in the resulting display returns the view to the same hierarchy from which you activated the Back command. The - hover help for this button tells you where it will take you. - This command is similar to the Forward button in a web browser.
Up IconUpThis command displays the hierarchy of the parent of the current highest level resource. The hover help for this button tells you where it will take you.
Collapse All IconCollapse AllThis command collapses the tree expansion state of all resources in the view.
Link with Editor IconLink with EditorThis command toggles whether the view selection is linked to the active editor. - When this option is selected, changing the active editor will automatically update the selection to the resource being edited.
View Menu IconMenuClick the white upside-down triangle icon to open a menu of items specific to the view.

-
-
Select Working Set
-
Opens the Select Working Set dialog to allow selecting a working set for the view.

-
Deselect Working Set
-
Deselects the current working set.

-
Edit Active Working Set
-
Opens the Edit Working Set dialog to allow changing the current working set.

-
Filters
-
This command allows you to select filters to apply to the view so that you can show or hide various resources as needed. - File types selected in the list will not be shown in the C/C++ Projects view.

-
Link with Editor
-
See the toolbar item description above.

-

- - -

C/C++ Projects view icons

- -

The table below lists the icons displayed in the C/C++ Projects view.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconDescription
- C or C++ file IconC or C++ file
- Executable file iconDebuggable executable file
- C or C++ object file iconObject file
- Class IconClass
- Macro Definition IconMacro Definition
- Enum IconEnum
- Enumerator IconEnumerator
- Variable IconVariable
- Field private iconField private
- Field protected iconField protected
- Field public iconField public
- Include iconInclude
- Makefile iconMakefile
- Method private iconMethod private
- Method protected iconMethod protected
- Method public iconMethod public
- Namespace iconNamespace
- Namespace declared iconNamespace declared
- Struct iconStruct
- Type definition iconType definition
- Union iconUnion
- Function iconFunction
- -

The table below lists some overlay decorations displayed in the C/C++ Projects view.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- C overlayC/C++ project
- Edited overlayEdited
- Inherit overlayInherits
- Indexed overlayIndexed
- Error overlayError
- Warning overlayWarning
- Wrench overlayWrench signifies customized build settings or include paths/macros
- Inactive overlayExcluded from build / Deprecated / Inactive
- -

Related concepts -
Project file views -

- -

Related tasks -
Displaying C/C++ file components in the C/C++ Projects view -
Hiding files by type in the C/C++ Projects view

- -

Related references -
Project Explorer view

-
C/C++ Views

-
-

-Red Hat Copyright Statement
-IBM Copyright Statement -

- -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_create_make_target.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_create_make_target.htm deleted file mode 100644 index db8623f83be..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_create_make_target.htm +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - - Create a Make Target - - - - -

Create a Make Target

- -

Use the Create a Make Target dialog box to define build settings when creating a Make Target.

- -

Create a Make Target Window

- -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Create a Make Target options
OptionDescription
Target NameName of the Make Target.
Make TargetThe reference to the make section in your makefile.
Use defaultSelect this checkbox to use the default make command. Clear the check box to specify a new make command.
Build commandIf you clear the Use default checkbox type a new make command in this field.
Stop on first build errorStops the build when an error occurs.
Run all project buildersRuns additional project builders such as discovery.
- -

Related concepts -
-Build overview
-Makefile

-

Related tasks
-Creating a makefile
-Creating a Make Target
- -Defining Project Build settings

- -
-IBM Copyright Statement - - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_breadcrumb.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_breadcrumb.htm deleted file mode 100644 index f5e7addcbd6..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_breadcrumb.htm +++ /dev/null @@ -1,29 +0,0 @@ - - - - - -Debug Breadcrumb - - - - -

Debug Breadcrumb

-

Use the Debug Breadcrumb layout to show a compact presentation of the currently active debug context and its parents.

-

Debug Breadcrumb

-

To show the Debug Breadcrumb layout, in the Debug view toolbar select View Menu > Layout > Breadcrumb. Alternatively, resize the Debug view such that the height of the view is small enough to fit only one line of text. This causes the view to change over to the Breadcrumb layout automatically.

-

The Debug Breadcrumb allows you to invoke actions on any element shown in the breadcrumb. Actions can be invoked through the context menu or through key bindings. To select an element in the breadcrumb click on it or activate the Debug view and use the left and right arrow keys. -

You can also change the active debug context using the breadcrumb. Click on one of the arrows or any element top open a drop-down window. The drop-down shows all the siblings of the element for which the drop-down was opened. Click on an element to make it the new active debug context. To open the drop-down with the keyboard, select and element and press the down key. - -

Related concepts -
-Debug overview
-Debug information

-

Related tasks -
-Debugging

-

Related reference -
-Debug View

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_brkpt_actions.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_brkpt_actions.htm deleted file mode 100644 index 944c102afe2..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_brkpt_actions.htm +++ /dev/null @@ -1,55 +0,0 @@ - - - - - - - Breakpoint Actions preferences - - - - - -

Breakpoint Actions preferences

- -

Use the Breakpoint Actions page in the Preferences window to create, edit, and remove breakpoint actions. The breakpoint actions defined here are available to all projects in the current workspace.

-

Breakpoint Actions preference page

- - - - - - - - - - - - - - - - - - - - - - - - - -
Breakpoint Actions Preference Options
OptionDescription
New...To create a new breakpoint action, click New.
Edit...To edit the currently selected action, click Edit. In the Action dialog box that appears, edit the action settings, then click OK.
DeleteTo delete the currently selected action, click Delete.
- -

Related concepts
- C/C++ Development perspective

-

Related tasks
- Using breakpoints, watchpoints, and breakpoint actions

-

Related reference
- Debug preferences

-
-Nokia Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_pref.htm deleted file mode 100644 index 308a788d9db..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_pref.htm +++ /dev/null @@ -1,67 +0,0 @@ - - - - - - -Debug preferences - - - - -

Debug preferences

- -

The C/C++ Debug panel controls general settings for C/C++ debugging.

-

C/C++ Debug preferences panel

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C/C++ Debug Preference Options
Default variable formatSelect the default variable format from either Default, Hexadecimal, Decimal, Octal or Binary.
Default expression formatSelect the default expression format from either Default, Hexadecimal, Decimal, Octal or Binary.
Default register formatSelect the default register format from either Default, Hexadecimal, Decimal, Octal or Binary.
Character encodingSelect the character encoding of the debugged program. This applies to char type strings. Note that this requires GDB version 7.0 or later.
Wide character encodingSelect the wide character encoding of the debugged program. This applies to wchar_t type strings. Note that this requires GDB version 7.0 or later.
Show source files in binaries Show source files associated with project binaries.
- -

Related concepts -
-Debug information

-

Related tasks -
-Debugging

-

Related reference -
-Views

-

Nokia Copyright Statement
-IBM Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_src.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_src.htm deleted file mode 100644 index a6e5346907a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_src.htm +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - - Source Lookup Path preferences - - - - - -

Source Lookup Path preference

- -

Use the Source Lookup Path preference page to add or remove source containers.

- -

Debug Source Code Locations Preferences

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Default Source Lookup Path Options -
OptionsDescription
Add...Opens the Add Source dialog to insert a new source container of one of the following types:

-
    -
  • Absolute File Path
  • -
  • Compilation Directory
  • -
  • File System Directory
  • -
  • Path Mapping
  • -
  • Project
  • -
  • Project - Path Relative to Source Folders
  • -
  • Program Relative File Path
  • -
  • Workspace
  • -
  • Workspace Folder
  • -
-
Edit...Opens the Edit File System Directory dialog to modify the currently selected source container.
RemoveRemove the currently selected source container.
UpMove the currently selected source container higher in the list.
DownMove the currently selected source container lower in the list.
- -

Nokia Copyright Statement
-IBM Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_src_path_mapping.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_src_path_mapping.htm deleted file mode 100644 index 6467e480465..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_src_path_mapping.htm +++ /dev/null @@ -1,79 +0,0 @@ - - - - - - - Source Lookup Path preferences - - - - - -

Edit Source Lookup Path Mappings

- -

Use the Source Lookup Path Mappings to edit the Path Mapping source container type.

- -

Debug Source Lookup Path Mapping

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Source Lookup Path Mappings Options -
OptionsDescription
NameThe name of the Path Mapping. Only the name "Found Mappings" is used by CDT when automatically creating path mappings, such as from the C Source Not Found Editor.
Compilation path:The path of the folder as it is in the debug information. This is the folder path when the source was compiled. -

- This path must exactly match the path as it is in the debug information. For example, if a file was compiled with forward (/) slashes, then forward slashes should be entered as path separator. - Similarly, if there is a relative path (such as "..") in the compilation path, that should be included as well. -

- The C Source Not Found Editor automatically creates the correct form when "Locate File..." is used. -

Local file system path:The path of the folder as it is locally, where Eclipse can find the file. -
Resolve path mappings using debugger backend.Allow the mapping to be performed with the debugger backend where supported. This allows any direct interaction with the backend (for example via the console) to have a consistent view of file names. -

- This option is the default and provides a more complete path mapping solution. -

AddAdd a new row to the table. Both the Compilation path and Local file system path need to be specified. -
RemoveRemove the currently selected row.
UpMove the currently selected row higher in the list.
DownMove the currently selected row lower in the list.
- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_view.htm deleted file mode 100644 index 9b0eabb53c0..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dbg_view.htm +++ /dev/null @@ -1,338 +0,0 @@ - - - - - - -Debug view - - - - - - -

Debug view

- -

The Debug view shows the target debugging information in a tree hierarchy.

-

Debug view

-

The number beside the thread label is a reference counter, not a -thread identification number (TID).

-

The CDT displays stack frames as child elements. It displays the reason for - the suspension beside the thread, (such as end of stepping range, breakpoint - hit, and signal received). When a program exits, the exit - code is displayed.

-

The icons that appear in the Debug view include:

- - - - - - - - - - - - - - - - - - - - - - - - - - -
- Icons - Session item Description
- Launch instance icon - Launch instance Launch configuration name and launch type
- Icon: Debugger -  Debugger instance icon - Debugger instance Debugger name and state
- Icon: Thread; suspended Icon: Thread; running  Icon: Thread; stopped - Thread instance Thread number and state
- Stack frame instance icon - Stack frame instance Stack frame number, function, file name, and file line number
-

In addition to controlling the individual stepping of your programs, you can -also control the debug session. You can perform actions such as terminating the -session and stopping the program by using the debug launch controls available -from Debug view.

- -

Debug view toolbar options

-

The table below lists the toolbar options displayed in the Debug view.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Icons - ActionDescription
- Remove all Terminated launches icon - Remove All Terminated Launches Clears all terminated processes in Debug view
  Connect to a ProcessEnables the selection of a running process to debug.
- Restart icon - RestartStarts a new debug session for the selected process
- Resume icon - ResumeSelect the Resume command to resume execution of the currently suspended debug target.
- Suspend icon - SuspendSelect the Suspend command to halt execution of the currently selected thread in a debug target.
- Terminate icon - Terminate Ends the selected debug session and/or process. The impact of this action depends on the type of the item selected in the Debug view.
- Disconnect icon - DisconnectDetaches the debugger from the selected process (useful for -debugging attached processes).
- Step Into icon - Step Into Select to execute the current line, including any routines, and proceed to the next statement.
- Step Over icon - Step Over Select to execute the current line, following execution inside a routine.
- Step Return icon - Step Return Select to continue execution to the end of the current routine, then follow execution to the routine's caller.
- Drop to Frame icon - Drop to Frame Select the Drop to Frame command to re-enter the selected stack frame in the Debug view.
- Instruction Stepping Mode icon - Instruction Stepping Mode Activate to enable instruction stepping mode to examine a program as it steps into disassembled code.
- Use Step Filters icon - Use Step Filters Select the Use Step Filters command to change whether step filters should be used in the Debug view.
- Menu

Use the Debug view menu to:

-
    -
  • change the layout of debug view (tree vs. breadcrumb)
  • -
  • alternate showing of full or no paths on source files
  • -
  • control how views are managed
  • -
  • activate or deactivate the child elements shown in the Debug view
  • -
- -

Debug view context menu commands

-

The Debug view context menu commands include:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconsNameDescription
- Copy Stack icon - Copy Stack Copies the selected stack of suspended threads as well as the state of the running threads to the clipboard.
- Find...Opens the debug view element searching dialog.
- Drop to Frame icon - Drop To Frame Select the Drop to Frame command to re-enter the selected stack frame in the Debug view.
- Step Into icon - Step Into Select to execute the current line, including any routines, and proceed to the next statement.
- Step Over icon - Step Over Select to execute the current line, following execution inside a routine.
- Step Return icon - Step Return Select to continue execution to the end of the current routine, then follow execution to the routine's caller.
- Instruction Stepping Mode icon - Instruction Stepping Mode Activate to enable instruction stepping mode to examine a program as it steps into disassembled code.
- Use Step Filters icon - Use Step Filters Toggles step filters on/off. When on, all step functions apply step filters.
- Resume without signal icon - Resume Without Signal Resume program execution after receiving the signal.
- Resume icon - ResumeSelect the Resume command to resume execution of the currently suspended debug target.
- Suspend icon - SuspendSelect the Suspend command to halt execution of the currently selected thread in a debug target.
- Terminate icon - Terminate Ends the selected debug session and/or process. The impact of this action depends on the type of the item selected in the Debug view.
- Terminate and Relaunch icon - Terminate and Relaunch Select the Terminate and Relaunch command to terminate the selected debug target and then relaunch it.
- Disconnect icon - DisconnectDetaches the debugger from the selected process (useful for - debugging attached processes)
- Remote all Terminated icon - Remove All Terminated Clears all terminated processes in Debug view
- Terminate and Remove icon - Terminate and Remove Terminates the selected debug target and removes it from the view.
- Terminate all icon - Terminate/Disconnect All Terminates or disconnects all active launches in the view.
- PropertiesOpens the Properties for window showing the process properties.
- -

Related concepts -
-Debug overview
-Debug information

-

Related tasks -
-Debugging

-

Related reference -
-Run and Debug dialog box
-Debug Breadcrumb
-C/C++ Views

- -
-Nokia Copyright Statement
-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_debug.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_debug.htm deleted file mode 100644 index 735108d26a8..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_debug.htm +++ /dev/null @@ -1,47 +0,0 @@ - - - - - - - Debug Preferences - - - - - -

Debug preferences

- -

Use the Debug preference panel in the Preferences window to manage common globally defined debug settings.

-Debug Preferences - -

- - - - - - - - - - - - - - - - - - - - - - - - -
Debug Preference Options
OptionsDescription
Character encodingUse this option to specify the charset used by the char type of the inferior (target) program
Wide character encodingUse this option to specify the charset used by the wchar_t type of the inferior (target) program
Show source files in binariesSelect this checkbox to show the source files in binaries.
- -

IBM Copyright Statement

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_discovery_preferences.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_discovery_preferences.htm deleted file mode 100644 index 8e44c338ed3..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_discovery_preferences.htm +++ /dev/null @@ -1,35 +0,0 @@ - - - - - - -C/C++ Project Properties, Standard, Discovery Options - - - - -

Discovery Options page, C/C++ Preferences window

- -

You can define the discovery options on the Discovery Options page of a C/C++ Preferences window.

- -

Discovery Options, Preferences Dialog Box

- -

-

-
Automate discovery of paths and symbols
-
Select this checkbox to scan the build output for paths and symbols.
-
Build output parser options
-
This section allows you to select the make build output parser.
-
Generate scanner info command options
-
Select to invoke secondary paths and symbols provider (such as GNU specs).
-
Restore Defaults
Returns any changes back to their default setting.
-
Apply
Applies any changes.
-

- - -

IBM Copyright Statement

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dissassembly_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dissassembly_view.htm deleted file mode 100644 index 9939e553839..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dissassembly_view.htm +++ /dev/null @@ -1,54 +0,0 @@ - - - - - - -Disassembly view - - - - - -

Disassembly view

- -

The Disassembly view shows the loaded program as assembler instructions mixed with source code for comparison. The currently executing line is indicated by an arrow marker and highlighted in the view. You can do the following tasks in the Disassembly view:

-
    -
  • Set breakpoints at the start of any assembler instruction
  • -
  • Enable and disable breakpoints and their set their properties
  • -
  • Step through the disassembly instructions of your program
  • -
  • Jump to specific instructions in the program
  • -
-

Disassembly View icon

- - -

Disassembly view context menu commands

- -

The Disassembly view context menu commands include:

- - - - - - - - - - - - - - - - -
CommandNameDescription
Run to line icon
Run To Line

Resumes program execution until the specific line is reached. This is a convenient way to suspend execution at a line without setting a breakpoint.

Resume at line icon
Resume At Line Resume program execution from the line selected in the Disassembly view.
- -

Related concepts
- Debug information

-

Related reference
- C/C++ Views

-
-Nokia Copyright Statement -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dsfgdb.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dsfgdb.htm deleted file mode 100644 index ae9698af0a8..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_dsfgdb.htm +++ /dev/null @@ -1,161 +0,0 @@ - - - - - - - GDB Debugging Preferences - - - - - -

GDB Debugging Preferences

- -

Use this preferences panel to control how the C/C++ debugger behaves when debugging with GDB, -specifically when using a GDB (DSF) launcher. -

GDB preferences panel

- - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
GDB Preference Panel Options
CategoryOptionDescription
Debug Configurations Defaults
GDB debuggerSpecifies the GDB debugger binary that will be used by default for each - newly created debug launch. Using an absolute path will directly point to the binary (e.g, /home/user/myGdb), - while using a binary name will have C/C++ look through the PATH variable for that binary (e.g., myGdb). This can - be useful of your GDB binary is not named 'gdb'. Each launch configuration allows to override this setting in - the Debugger tab.
GDB command fileSpecifies the GDB debugger command file that will be used by default for each - newly created debug launch. This can be useful if you often/always want to use a GDB command file for your launches. - Each launch configuration allows to override this setting in the Debugger tab.
Stop on startupWhen checked, the C/C++ debugger will stop execution at the specified symbol when - launching or re-starting a process. By default, this setting makes the C/C++ debugger stop when entering 'main'.
Command timeoutWhen checked, the C/C++ debugger will abort the debug session if any command sent - to GDB does not get an answer before the specified timeout. Using this can prevent debug sessions from hanging forever - when debugging un-reliable targets. -

- Using the Advanced... button allows to set a different timeout for individual commands. A value of zero can be - used to specify "no timeout" for a particular command. MI commands must start with a hyphen ('-'). - For example, '-target-select'.

Non-stop modeWhen checked, the C/C++ debugger will run in non-stop mode for each newly created - debug launch. Non-stop mode allows each thread of a debug session to be controlled independently. This allows to stop - one or more threads while leaving others running. In contrast, all-stop mode interrupts and resumes all threads at the - same time. Note that non-stop mode is only available starting with GDB 7.0.
General Behavior
Terminate GDB when last process exitsWhen checked, the C/C++ debugger will terminate the GDB - process (on the host) after all the target processes it is debugging have terminated. Otherwise it - will leave it running. It can be useful to keep GDB running if you expect to want to attach or create - new processes to debug after the previously debugged processes have terminated.
Use enhanced debug hoverWhen checked, hovering over an expression in the editor during a - debug session will bring up an enhanced expression evaluation control. Otherwise, a more basic - control is used. This, of course, assumes that you have the debugger's hovering capability turned on in - C/C++ > Editor > Hovers. If not, this checkbox has no effect.
- debug hover modes
Show only suspended threads in the Debug viewWhen checked, the Debug view will only show threads that are suspended. - When dealing with a large number of threads, this helps focus on the threads being inspected. Obviously, - this option is only valuable in non-stop mode, where some threads can run while others are stopped.
Use aggressive breakpoint filteringWhen checked, the button "Show Breakpoints Supported by Selected Target" - of the Breakpoints view will only show the breakpoints that affect the currently selected C/C++ debug context - (e.g., thread, process). Otherwise, "Show Breakpoints Supported by Selected Target" will show all breakpoints - that are for any C/C++ target.

- Show Breakpoints Supported by Selected Target button

Enable GDB tracesWhen checked, the debug session will produce an additional console which - will contain all the gdb/mi activity. Basically, this details the interaction between the C/C++ debugger and GDB. - This information is often critical when the debugger is not behaving as you expect. Include this console output - when submitting a bugzilla report against the C/C++ debugger. It is recommended to keep this setting enabled at - all times, as it does not cause any negative effect. -

- Once the number of characters specified by the limit field is reached, older trace lines will be discarded - gradually. This is to avoid these traces consuming too much memory, for very long debug sessions.

Display run-time type of variablesWhen checked, the C/C++ debugger will show the actual variable type (not the - declared one) in Variables and Expressions views. Not only does this allow to see what is the current run-time - type of a variable, but it allows to access fields that may not be in the base class. - Note that this feature will only work starting with GDB 7.5.
Pretty Printing
Enable pretty printers in variable/expression treeWhen checked, the C/C++ Debugger will display STL types in a user-friendly - fashion. This can be seen in the Variables and Expressions views, as well as in the advanced editor hover. - For example, Maps, Lists and Vectors will be shown in an array-style format instead of showing the - details of the actual implementation of the data struture. Note that pretty printing requires a GDB that - has python support enabled and the user of STL pretty-printers.
For collections, initially limit child count toWhen using pretty printing, collections (e.g., Maps, Lists, etc) can contain - a large number of elements. Trying to display all this children at once can cause very poor responsiveness. This - value will limit the number of children displayed initially, while allowing the user to manually request more - children directly from the view.
-

Related reference
-


-

IBM Copyright Statement

- -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_editor_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_editor_view.htm deleted file mode 100644 index 9ba6e6a9027..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_editor_view.htm +++ /dev/null @@ -1,39 +0,0 @@ - - - - - - - Editor view - - - - -

Editor view

-

The C/C++ editor provides specialized features for editing C/C++ related files.

-

C/C++ Editor

-

Associated with the editor is a C/C++-specific Outline view, - which shows the structure of the active C, C++ or makefile. It is updated as you edit these files.

- -

The editor includes the following features:

-
    -
  • Syntax highlighting
  • -
  • Content/code assist
  • -
  • Integrated debugging features
  • -
- -

The most common way to invoke the C/C++ editor is to open a file from - the Project Explorer or the C/C++ Project views using pop-up menus or by clicking the file - (single or double-click depending on the user preferences).

- -

The C/C++ editor does not contain a toolbar itself, but relies on the use of the main -toolbar, Edit menu, Search menu -and key binding actions.

- -
-

-IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_environment_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_environment_pref.htm deleted file mode 100644 index e136a355b13..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_environment_pref.htm +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - -Environment preferences - - - - - - -

Environment preferences

- -

Use the Environment preference panel to define environment variables and their use.

-

Environment Preference

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Environment Options -
OptionsDescription
Environment variables to set Shows a list of the environment variables and their value.
New...Click to open the New Variable dialog where you define the variable name and value.
Select...Click to open the Select variables dialog.
Edit...Click to edit the currently selected variable and its value.
RemoveClick to remove the currently selected variable.
UndefineClick to undefine the currently selected variable.

- NOTE: Some variables, like PATH, have special meaning and cannot be undefined.
Append variables to native environment Activate this checkbox to append the variables to the native environment during execution.
Replace native environment with specified one Activate this checkbox to replace the native environment with these variables, restoring the native environment upon completion.
- -

Nokia Copyright Statement

-
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_inc.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_inc.htm deleted file mode 100644 index 1427d0718d4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_inc.htm +++ /dev/null @@ -1,109 +0,0 @@ - - - - - - - C/C++ File Properties, Paths and Symbols, Includes - - - - -

C/C++ File Properties, Paths and Symbols, Includes

-

Use the Paths and Symbols properties panel Includes tab to modify the list of included paths and change the order in which they are referenced.

-

C/C++ File Properties, Paths and Symbols, Includes

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Paths and Symbols, Symbols tab
OptionDescription
Languages (left pane)Displays language related to this file.
Include paths (right pane)List of include paths related to given language.
Add...Add new include path.
Edit...Modify selected include path.
DeleteRemove the selected include path.
IncludeToggle selected path exported or not.
Move UpMove the selected element up in the list.
Move DownMove the selected element down in the list.
Import Settings...Import symbol settings.
Export Settings...Export symbol settings.
- -
-

Available for :
-
CDT projects, folders and files
-
- -

Related reference
- -

-
-

Intel Copyright Statement

- - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_lang_mapp.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_lang_mapp.htm deleted file mode 100644 index 950e1ce217c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_lang_mapp.htm +++ /dev/null @@ -1,57 +0,0 @@ - - - - - - -Language Mappings preferences - - - - - -

Language Mappings preferences

- -

Use the Language Mappings properties panel to customize the use of C/C++ language associations for the file.

-

Language Mappings preference page

- - - - - - - - - - - - - - - - - - - - - - - - - -
Language Mappings Options
OptionDescription
Content Type The content type associated with the language.
ConfigurationShows the list of configurations for the selected content type.
LanguageShows the list of corresponding languages associated with the configurations in the list for the specific content type.
- -

Related reference
- -

-

- -
-

Nokia Copyright Statement

-
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_lng.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_lng.htm deleted file mode 100644 index 3b2b06bd6b1..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_lng.htm +++ /dev/null @@ -1,38 +0,0 @@ - - - - - - C/C++ File Properties, Language mapping - - - -

C/C++ File Properties, Language mappings

-

Customize the use of C/C++ language associations in the Language Mappings preference panel for individual files.

-

C/C++ Project Properties, Language mapping

-

-
-
Language
-
The language to use for this file and build configuration.
-

Available for :
-
CDT source files
-
-

Related reference
- -

-

-

IBM Copyright Statement

- -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_steps.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_steps.htm deleted file mode 100644 index 46b0d78cc12..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_steps.htm +++ /dev/null @@ -1,83 +0,0 @@ - - - - - - C/C++ File Properties, Build, Settings, Build Steps tab - - - -

C/C++ File Properties, Build, Settings, Build Steps tab

-Use the Build Steps properties panel to customize the selected build configuration allowing the specification -of user defined build command steps, as well as a descriptive message to be displayed in the -build output, immediately prior to and immediately after normal build processing executes. -

C/C++ File Properties, Build, Settings, Build Steps tab

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Settings, Build Steps tab
OptionDescription
Custom build step applicabilitySelect either 'Apply' or 'Disable' custom build step. In case of apply, custom build step would override standard one.
Additional input file namesDefine additional file names to be used in custom build step.
Output file name(s)Define name(s) for output files generated by custom build step.
CommandSpecifies a command, or a list of semicolon separated commands, to be executed during custom build step.
DescriptionSpecify optional descriptive text that is associated with the post-build step to be displayed in the build output immediately prior to execution of the post-build step command or commands.
- -

Related reference
- -

-
-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_sym.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_sym.htm deleted file mode 100644 index 3aa6ea6d0b8..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_sym.htm +++ /dev/null @@ -1,103 +0,0 @@ - - - - - - - C/C++ File Properties, Paths and Symbols, Symbols - - - - -

C/C++ File Properties, Paths and Symbols, Symbols

-

Use the Paths and Symbols properties panel # Symbols tab to modify the list of preprocessor symbols.

-

C/C++ File Properties, Paths and Symbols, Symbols

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Paths and Symbols, Symbols tab
OptionDescription
Languages (left pane)Displays language related to this file.
Symbol / ValueList of symbols related to given language.
Add...Add new symbol.
Edit...Modify selected symbol value.
DeleteRemove selected symbol.
Export / UnexportToggle selected symbol exported or not.
Show built-in valuesCheck to display system (built-in) includes.
Import Settings...Import symbol settings.
Export Settings...Export symbol settings.
-
-

Available for :
-
CDT projects, folders and files
-
- -

Related reference
- -

-
-

Intel Copyright Statement

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_toolsettings.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_toolsettings.htm deleted file mode 100644 index 7beb016d754..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fileprop_toolsettings.htm +++ /dev/null @@ -1,110 +0,0 @@ - - - - - - C/C++ File Properties, Build, Settings, Tool settings tab - - - -

C/C++ File Properties, Build, Settings, Tool settings tab

-Customizes the tools and tool options used in your build configuration. -

C/C++ File Properties, Build, Settings, Tool Settings tab

-

- -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - -
Tool Settings options
ConfigurationClick here for a description.
Manage configurationsClick here for a description.
(Left pane)Displays a list of tools and their option categories. Select a desired tool from the list to modify its options.
(Right pane)Displays the options that you can modify for the selected tool. This list of options changes depending on which options category you select for a specific tool in the left pane.
-
-

Available for: CDT source files

- -

Related reference
- - -

-

- -

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_find_replace.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_find_replace.htm deleted file mode 100644 index 382b6d017e5..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_find_replace.htm +++ /dev/null @@ -1,58 +0,0 @@ - - - - - - - C/C++ Find/Replace - - -

C/C++ Find/Replace

-

Ctrl+F (or Edit > Find/Replace) displays the Find/Replace dialog. -Here you can specify text to search for and optionally text with which to replace it. -

-

Find and Replace Dialog Box

-

You can specify:

-
    -
  • The direction (forward or back from the current cursor location)
  • -
  • The scope (All for the whole file or Selected Lines to search only -within the highlighted area)
  • -
  • Whether the search is Case Sensitive or Whole Word. -You can also specify whether the search wraps at the end of the file.
  • -
- -

If you close the Find/Replace dialog with text in the Find field, -you can use Ctrl+K (or Edit > Find Next) or -Ctrl+Shift+K (or Edit > Find Previous) to go to the next -occurrence of that text. -The directions for "Next" and "Previous" -are not affected by the Direction setting in the Find/Replace dialog. -

- -

Note: -Wildcards are not currently supported for searches.

- -

Incremental Find

- -

You can also choose Incremental Find from the Find/Replace dialog. -With this option selected, each letter you type in the Find field -causes the editor focus to move to the first complete occurrence of the text -you are typing. -You can also use incremental find by pressing Ctrl+J (Edit > Incremental Find). -In this case, the text you type appears in the Status Line at the bottom of -the Eclipse window. -

- -

Note: -The settings in the Find/Replace dialog do not affect the operation -of incremental find in the Status Line.

- - -

-IBM Copyright Statement
-IBM Copyright Statement -

- - -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fprop_resource.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fprop_resource.htm deleted file mode 100644 index 467e41722ec..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fprop_resource.htm +++ /dev/null @@ -1,61 +0,0 @@ - - - - - - C/C++ Folder Properties, Resource - - - -

C/C++ Folder Properties, Resource

-

C/C++ Folder Properties, Resource

-
-
Resource
-
Shows resource information.
-
Read only
-
Set Read-only attribute for folder
-
Archive
-
Set Archive attribute for folder
-
Derived
-
Set Derived attribute for folder
-
Text file encoding
-
Sets an alternate text encoding.
-

Available for :
-
Any projects, folders and files regardless of project kind
-
-

Related reference
- -

- -

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fprop_toolsettings.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fprop_toolsettings.htm deleted file mode 100644 index 7843918ff5e..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_fprop_toolsettings.htm +++ /dev/null @@ -1,114 +0,0 @@ - - - - - - C/C++ Folder Properties, Build, Settings, Tool Settings tab - - - -

C/C++ Folder Properties, Build, Settings, Tool settings tab

-Customizes the tools and tool options used in your build configuration. -

C/C++ Folder Properties, Build, Settings, Tool settings tab

-

- -

Related reference
- - -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - -
Tool settings options
ConfigurationClick here for a description.
Manage configurationsClick here for a description.
(Left pane)Displays a list of tools and their option categories. Select a desired tool from the list to modify its options.
(Right pane)Displays the options that you can modify for the selected tool. This list of options changes depending on which options category you select for a specific tool in the left pane.
-
-

Available for: CDT projects, folders and source files

- -

Related reference
- - -

-

- -

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_icons.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_icons.htm deleted file mode 100644 index 010b14d4c3d..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_icons.htm +++ /dev/null @@ -1,139 +0,0 @@ - - - - - - -C/C++ Icons - - - - - -

C/C++ Icons

- -

The table below lists the C/C++ icons displayed in the Stand-alone Debugger.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconDescription
- C or C++ file iconC or C++ file
- Class iconClass
- Code template iconCode template
- Macro Definition iconMacro Definition
- Enum iconEnum
- Enumerator iconEnumerator
- Variable iconVariable
- Field private iconField private
- Field protected iconField protected
- Field public iconField public
- Include iconInclude
- Makefile iconMakefile
- Method private iconMethod private
- Method protected iconMethod protected
- Method public iconMethod public
- Namespace iconNamespace
- Struct iconStruct
- Typedef iconTypedef
- Union iconUnion
- Function iconFunction
-

Related concepts -
-Project file views
-Outline view

-

Related tasks -
-Displaying C/C++ file components in the -C/C++ Projects view

-

Related reference -
-Views

-IBM Copyright Statement. -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_include_browser_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_include_browser_view.htm deleted file mode 100644 index 33ecf67ad38..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_include_browser_view.htm +++ /dev/null @@ -1,173 +0,0 @@ - - - - - - Include Browser View - - - - -

- Include Browser view -

-

- The Include Browser view shows the <include> and #include relationships between source and header files. -

-

Include Browser view

-

- Include Browser toolbar buttons -

-

- The Include Browser tree shows files included by the focused file or files including the focused file depending on the selection made in the - toolbar. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Include Browser Toolbar Options
IconNameDescription
Show Next Include icon -

- Show Next Include -

-
-

- This command selects the next include directive of the current file and opens it in the editor. -

-
Show Previous Include icon -

- Show Previous Include -

-
-

- This command selects the previous include directive of the current file and opens it in the editor. -

-
Hide System Includes icon -

- Hide System Includes -

-
-

- This command toggles the display of include directives with angle brackets (<>). -

-
Hide Inactive Code Includes icon -

- Hide Includes from Inactive Code -

-
-

- This command toggles the display of include directives which are contained in an inactive conditional preprocessor branch. -

-
Show Includes icon -

- Show Includers -

-
-

- Show files including the currently focused file. -

-
Show Included Files icon -

- Show Included Files -

-
-

- Show files included by the currently focused file. -

-
Show History List icon -

- Show History List -

-
-

- This menu displays a history of previously displayed include relationships. -

-
Refresh icon -

- Refresh View Content -

-
-

- This command updates the view content by running a new query on the index database. -

-
Menu icon -

- View Menu -

-
-

- Shows additional options to manage the Include Browser view including:
-

    -
  • Select Working Set...
  • -
  • Deselect Working Set
  • -
  • Edit Active Working Set...
  • -
  • Show Includers
  • -
  • Show Files Included
  • -
  • Hide System Includes
  • -
  • Hide Inactive Includes
  • -
-

-
-

- Related reference
- Views -

-
-Nokia Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_indexer_preference.html b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_indexer_preference.html deleted file mode 100644 index 95fc083c56f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_indexer_preference.html +++ /dev/null @@ -1,121 +0,0 @@ - - - - - - Indexer preferences (C/C++) - - - - -

Indexer preferences (C/C++)

-

Use the Indexer preference panel to select the indexer used by default for new projects and configure its behavior.

-

Indexer Preferences Window
-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Indexer Options
OptionDescription
Select Indexer Select the indexer to use by default for all new projects.
Index source files not included in the buildActivate this checkbox to index all source files used by the project.
Index unused headersActivate this checkbox to index unused header files.
Allow heuristic resolution of includes Activate this checkbox to allow the indexer to skip indexing duplicate include files.
Skip files larger thanEnter the maximum file size to skip when indexing.
Skip all references (Call Hierarchy and Search will not work) Activate this checkbox to not index references to save space and gain performance. This prevents some portions of CDT from working, like Call Hierarchy and search for references.
Skip implicit references (e.g. overloaded operators) Activate this checkbox to not index implicit references.
Skip type and macro references (Search for these references will not work) Activate this checkbox to not index macro or type references. This prevents some portions of CDT from working, like Search.
Files to index up-front Type a comma separated list of files that should always be indexed immediately.
Automatically update the index Activate this checkbox to have the index automatically update as it requires.
Update index immediately after every file change Activate this checkbox to force an index update whenever a file is saved.
Use active build configuration Activate to always use the active build configuration indexer settings to build the index.
Use the build configuration specified in the project's indexer settings Activate to always use the project's indexer settings to build the index.
Index database cache: Limit relative to the maximum heap size Specify the relative size limit the index can reach based on the maximum heap size.
Index database cache: Absolute limit Specify the maximum size the index database cache is limited to.
Header file cache: Absolute limit Specify the maximum size the header file cache is limited to.
-

Related concepts
-Coding aids
-C/C++ search

-

Related tasks
-Searching for C/C++ elements
-Customizing the C/C++ -editor

-

Related reference -
-C/C++ search page, Search window
-Search action
-Search view
-

-
-

- Copyright IBM statement
- Nokia Copyright Statement -

-

-

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_language_mapping_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_language_mapping_pref.htm deleted file mode 100644 index d9d93139c2e..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_language_mapping_pref.htm +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - -Language Mappings preferences - - - - - - -

Language Mappings preferences

- -

Use the Language Mappings preference panel to customize the use of C/C++ language associations for the workspace.

-

Language Mappings preferences

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Language Mappings Preference Options -
OptionDescription
Content Type The content type associated with the language.
LanguageThe language associated with the content type.
Add...Click to show the Add Mapping dialog where you define the content type and language associated with it.
-

Add Mapping dialog

RemoveClick to remove the selected language mapping.
- -

Related reference
- -

-

- -

Nokia Copyright Statement

-
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_edit.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_edit.htm deleted file mode 100644 index 0079dff78e6..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_edit.htm +++ /dev/null @@ -1,221 +0,0 @@ - - - - - -Edit Menu actions - - - - -
-

Edit Menu actions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_file.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_file.htm deleted file mode 100644 index 1b0e77fbbbe..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_file.htm +++ /dev/null @@ -1,145 +0,0 @@ - - - - - -File Menu actions - - - -
-

File Menu actions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_navigate.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_navigate.htm deleted file mode 100644 index e37aa2a4add..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_navigate.htm +++ /dev/null @@ -1,239 +0,0 @@ - - - - - -Navigate Menu actions - - - -
-

Navigate Menu actions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- Note: Other Navigate options are - used with the JDT. Refer to the Java development user guide - for details. -

-

- IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_project.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_project.htm deleted file mode 100644 index 7244e8887ff..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_project.htm +++ /dev/null @@ -1,139 +0,0 @@ - - - - - -Project Menu actions - - - -
-

Project Menu actions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_refactor.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_refactor.htm deleted file mode 100644 index 579050591fc..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_refactor.htm +++ /dev/null @@ -1,83 +0,0 @@ - - - - - -Refactor Menu actions - - - - -
-

Refactor Menu actions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- Intel Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_run.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_run.htm deleted file mode 100644 index c3afbae0b4f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_run.htm +++ /dev/null @@ -1,130 +0,0 @@ - - - - - -Run Menu actions - - - -
-

Run Menu actions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_search.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_search.htm deleted file mode 100644 index 157b583080c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_search.htm +++ /dev/null @@ -1,82 +0,0 @@ - - - - - -Search Menu actions - - - -
-

Search Menu actions

-

- Search menu commands open the search dialog. There - are specialized tabs on the general Search dialog to - help you search for: -

-
    -
  • Files, or for text in files
  • -
  • Elements in C/C++ files
  • -
  • Text in the online help
  • -
  • Plug-ins.
  • -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- Related concepts
Coding aids
C/C++ search -

-

- Related tasks
Searching - for C/C++ elements
Customizing the C/C++ - editor -

-

- Related reference
C/C++ - editor preferences
Search - dialog
Search view -

-

- IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_source.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_source.htm deleted file mode 100644 index b147821ee14..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_source.htm +++ /dev/null @@ -1,124 +0,0 @@ - - - - - -Source Menu actions - - - - -
-

Source Menu actions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameFunctionKeyboard Shortcut
Adds or removes single-line, C++-style, - comment markers on each line in the selection, or the line - containing the cursor, if there is no selectionCtrl+/
Adds a block comment around the - selectionCtrl+Shift+/
Removes the comment markers around any - block comments in the selectionCtrl+Shift+\
Increases indentation on each line in - the selection, or the line containing the cursor, if there is no - selection 
Decreases indentation on each line in - the selection, or the line containing the cursor, if there is no - selectionShift+Tab
Applies simple indentation rules to the - current selection, or the line containing the cursor, if there is - no selectionCtrl+I
Applies the full - command linkC/C++ > Code Style > Formatter - preferences to the entire contents of the active editor, or to the - selection if there is one - Ctrl+Shift+F
Adds an include statement and, - optionally, a "using" declaration for the currently selected nameCtrl+Shift+N
Adds all the required includes for the - selected file 
Sorts the selected linesCtrl+Alt+S
Opens the Implement Method dialog 
Opens the Generate Getters and Setters - dialog that allows you to create Getters and Setters for fields in - the current type. Available on fields and types or on a text - selection inside a type 
Surrounds the selected statements with - a code template (as defined in - command linkC/C++ > Editor > Templates - ) - Alt+Shift+Z
-

- Intel Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_window.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_window.htm deleted file mode 100644 index b9d05507502..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_m_window.htm +++ /dev/null @@ -1,231 +0,0 @@ - - - - - -Window Menu actions - - - -
-

Window Menu actions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- IBM Copyright Statement -

-
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_make_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_make_pref.htm deleted file mode 100644 index 6ca13f56343..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_make_pref.htm +++ /dev/null @@ -1,73 +0,0 @@ - - - - - - -Make Targets Preferences - - - - - - -

Make Targets preferences

- -

Use the Make Targets preference panel in the Preferences window to set make target options.

- -

Make Targets Preferences Window

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Make Targets Preference Options
OptionsDescription
Build Make target in the backgroundSelect this checkbox to perform builds in the background.
Rebuild Last TargetThis option defines the scope of command "Rebuild Last Target" in Make Targets View.
From selected projectRebuild the same make target as was run last time in the currently selected project.
From selected folderRebuild the same make target as was run last time in the currently selected folder.
From selected rootRebuild the same make target as was run last time in the project from root folder.
- -
-
-
-
- -

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference
-Views
-Make Targets View -

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_make_settings_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_make_settings_pref.htm deleted file mode 100644 index aa6b95aae94..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_make_settings_pref.htm +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - -Settings preferences - - - - - - -

Settings preferences

- -

Use the Settings preference panel in the Preferences window to specify the Makefile style and include directories.

- -

Settings Preferences Window

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Settings Preference Options
OptionDescription
Posix MakeEnable to generate makefiles that are POSIX Make compatible.
GNU MakeEnable to generate makefiles that are GNU Make compatible.
New...Opens the Browse for Folder dialog to select a directory.
RemoveClick to remove the currently selected directory from the Makefile include directories list.
UpClick to move the currently selected directory up in the list.
DownClick to move the currently selected directory down in the list.
- -

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference
-Views

-
-IBM Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_make_targets_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_make_targets_view.htm deleted file mode 100644 index b817fca4628..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_make_targets_view.htm +++ /dev/null @@ -1,83 +0,0 @@ - - - - - - -Make Targets view - - - - - -

Make Targets view

- -

Use the Make Targets view to select the make targets you want to build in your workspace.

- -

Make Targets View

- -

Make Target toolbar

-

The table below lists the toolbar options displayed in the Make Targets view.

- -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconCommandDescription
Home iconNew Make TargetOpens the Create Make Target dialog box to define a new make target.
Home iconEdit Make TargetEdits currently selected target in the Modify Make Target dialog box.
Home iconBuild Make TargetBuilds currently selected target.
Home iconHomeMove to the top level.
Back iconBackNavigates back to a previous level.
Forward iconForwardNavigates forward to the next level.
Forward iconHide Empty FoldersToggles the display of empty folders in the Make Targets view.

- - -

Related tasks -
Creating a Make Target

- -

Related references -
Views

-
-

-Red Hat Copyright Statement
-IBM Copyright Statement -

- -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_makefile_settings_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_makefile_settings_pref.htm deleted file mode 100644 index 247a92778fb..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_makefile_settings_pref.htm +++ /dev/null @@ -1,78 +0,0 @@ - - - - - - -Makefile Editor preferences - - - - - - -

Makefile Editor preferences

- -

Use the Makefile Editor preference panel in the Preferences window to set syntax and folding options for the Makefile editor.

- -

Makefile Editor Syntax tab

- - - - - - - - - - - - - - - - - - - - - - - - -
Makefile Editor Syntax Options
OptionsDescription
ColorClick to set the selected syntax item to a specific color.
BoldIf enabled, set the selected syntax item to bold.
ItalicIf enabled, set the selected syntax item to italic.
-

Makefile Editor Folding tab

-

Makefile Editor Folding tab

- - - - - - - - - - - - - - - - -
Makefile Editor Folding Tab Options
OptionsDescription
Enable folding when opening a new editorIf enabled, activate folding when a new Makefile editor is opened.
- -

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference
-Views

-
-IBM Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mem_view_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mem_view_pref.htm deleted file mode 100644 index 5144f141186..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mem_view_pref.htm +++ /dev/null @@ -1,101 +0,0 @@ - - - - - - - - -Traditional Memory Rendering Preferences - - - - - - -

Traditional Memory Rendering preferences

- -

Use the Traditional Memory Rendering preference panel to change the appearance of the Memory view when displaying memory in traditional mode.

-

C/C++ Projects View

- -

Traditional Memory Rendering preference options

-

The table below lists the options displayed in the Traditional Memory Rendering Preferences.

- -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Traditional Memory Rendering Preferences Options
OptionDescription
Use Global Text ColorToggles the use of the global Text Color option.
Text ColorChanges the color of the text.
Brighten Alternate CellsSet the brightness used to highlight alternate cells.
Use Global Background ColorToggles the use of the global Background Text Color option.
Background ColorChanges the background color.
Changed ColorSet the color used to display changed memory locations.
Edit ColorSet the color used to show edited memory locations.
Use Global Selection ColorToggles the use of the global selection color option
Selection ColorSet the color used to select memory locations.
Edit BufferSet how the edit buffer should behave: -
    -
  • Save on Enter, Cancel on Focus Lost
  • -
  • Save on Enter or Focus Lost
  • -
-
History Trails LevelsSet the number of history levels to retain.

- - -

Related concepts -
-Debug information

-

Related tasks -
-Working with memory

-

Related reference -
-C/C++ Views

-
-IBM Copyright Statement
-Nokia Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_memoryview.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_memoryview.htm deleted file mode 100644 index 814ffca12ad..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_memoryview.htm +++ /dev/null @@ -1,223 +0,0 @@ - - - - - - - - -Memory view - - - - - -

Memory view

- -

The Memory view of the Debug -perspective lets you monitor and modify your process memory. The process memory -is presented as a list of so called memory monitors. Each monitor represents -a section of memory specified by it's location called base address. Each -memory monitor can be displayed in different predefined data formats -- memory -renderings. The debugger supports five rendering types -- hexadecimal -(default), ascii, signed integer and unsigned integer. The -default rendering is displayed automatically on the monitor creation.

-

Memory View

-

The Memory view contains two -panes -- the Memory Monitors pane and the Memory Renderings pane. The -Memory Monitors pane displays the list of memory monitors added to the debug -session currently selected in the Debug view. The content of the Memory -Renderings pane is controlled by the selection in the Memory Monitors pane and -consists of the tabs that display renderings. The Memory Renderings pane can be -configured to display two renderings simultaneously.

- -

Memory view toolbar options

-

The table below lists the icon3s displayed in the Memory view toolbar.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - view - - - - - - - - - - - - - - - - - - - - - - - - -
Icon
Name
Description
New Memory View Icon
New Memory View
Click to create a new memory view.
Pin Memory Monitor icon3
Pin Memory Monitor
Select to pin the memory monitor on top of all other memory monitors.
 
Import
Import a previously exported memory monitor.
 
Export
Export the selected memory monitor.
Toggle Memory Monitors icon
Toggle Memory Monitors Pane
Shows/hides the Memory Monitor pane.
Toggle Split Pane icon
Toggle Split Pane
Toggles the Memory Renderings pane split.
Link Memory Renderinicones icon
Link Memory Rendering Panes
Synchronizes the selection of two memory renderings.
Switch Memory Monitor icon
Switch Memory Monitor
When more than one memory monitor is active, select a different memory monitor to view.
View Menu iconView Menu > Layout Switch the Monitors and Rendering panes display between horizontal or vertical orientation.
View Menu > Preferences

Opens the Preferences window allowing you to set:

-
    -
  • Reset Memory Monitor - set to reset only visible or all renderings when resetting a memory monitor
  • -
  • Padded String - enter strings to show un-retrievable memory
  • -
  • Select Codepages - specify the standard to convert memory to ASCII and EBCDIC strings
  • -
Table Rendering Preferences Specify the memory loading mode to use when rendering scrolls to the end of the buffer.
- Table Rendering Preferences pane
Traditional Rendering Preferences Opens the Traditionally Memory Rendering pane in the Preferences dialog box.
Find/Replace...Opens the Find/Replace dialog box to search the Memory Rendering view.
Find NextFinds the next occurrence of the search string.
- -

Monitors pane context menu

-

The Monitors pane context menu inside the Memory view includes:

- - - - - - - - - - - - - - - - - - - - - -
Icon
Name
Description
Add Memory Monitor icon
Add Memory Monitor
Adds a new memory address or variable to the Memory Monitors pane.
Remote Memory Monitor icon
Remove Memory Monitor
Removes the selected memory address or variable from the Memory Monitors pane.
Reset icon
Reset
Resets the current memory monitor view.
- -

Rendering pane context menu

-

The Rendering pane context menu inside the Memory view includes:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Icon
Name
Description
Add Rendering icon
Add Rendering
Add a memory rendering pane to display a memory monitor item at a different address or in a different format.
Remote Rendering icon
Remove Rendering
Removes the selected rendering from the Memory view.
 PanesEnable or disable the showing of the Address, Binary, and Text portions of the rendering view.
 EndianToggle between the Little (default) and Big Endian display of memory.
 TextChoose the character encoding used to convert memory values into text for display. Choices include: ISO-8859-1 (default), US-ASCII, or UTF-8.
 Cell Size Specify the cell size used to display values in the Binary column. Choices include: 1, 2, 4 (default), and 8 bytes.
 RadixSpecify the radix used to display the values in the Binary column. Choices include: Hex, Decimal Signed, Decimal Unsigned (default), Octal, and Binary.
Copy to Clipboard icon
Copy To Clipboard Copies the selected portion of the Rendering pane to the clipboard.
 Go To Address Opens an edit box to type in a memory address. Press Enter to go to that address and show it in the Rendering pane.
 Reset To Base Address Resets the Rendering pane to the original base address.
Refresh
Refreshes the Rendering pane.
- -

Related concepts -
-Debug information

-

Related tasks -
-Working with memory

-

Related reference -
-C/C++ Views

-
-IBM Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_build.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_build.htm deleted file mode 100644 index 39d28a3c246..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_build.htm +++ /dev/null @@ -1,41 +0,0 @@ - - - - - - C/C++ Project Properties, Managed Make File, Build - - - -

C/C++ Project Properties, Managed Make File, C/C++ Build

-Customizes the options used for a specific file in your build -configuration. Select a tab in the Resource Configuration settings area -to set a specific category of options. -

C/C++ Project Properties, Managed Make File,  Build

-

-
-
Exclude from build
-
Excludes the selected file from being built with the selected -build configuration.
-
Configuration:
-
Specifies the selected build configuration from the list provided.
-
Resource Configuration settings
-
Sets file options which apply only to the selected file.
-
Restore Defaults
-
Returns any changes back to the settings of the selected -configuration.
-
Apply
-
Applies any changes.
-
-

Related reference
-C++ Project Properties, Managed -Make File, C/C++ Build, Tool Settings
-C++ Project Properties, Managed Make -File, Info -

-

-IBM Copyright Statement

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_info.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_info.htm deleted file mode 100644 index 59b3e11ec3a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_info.htm +++ /dev/null @@ -1,34 +0,0 @@ - - - - - - C/C++ Project Properties, Managed Make File, Info - - - -

C/C++ Project Properties, Managed Make File, Info

-

C/C++ Project Properties, Managed Make File, Info

-
-
Info
-
Shows file information.
-
Read only
-
Sets the file to be read only.
-
Derived
-
Specifies that the file is derived from other resources.
-
Text file encoding
-
Specifies an alternate text encoding.
-
Restore Defaults
-
Returns any changes back to their default setting.
-
Apply
-
Applies any changes.
-
-

Related reference
-C++ Project Properties, Managed Make -File, C/C++ Build

-

-IBM Copyright Statement

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_rcbs.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_rcbs.htm deleted file mode 100644 index ab7b21c3c7f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_rcbs.htm +++ /dev/null @@ -1,64 +0,0 @@ - - - - - - C/C++ Project Properties, Managed Make File, Build - - - -

C/C++ Project Properties, Managed Make File, C/C++ Build, Custom -Build Steps

-Customizes the selected build configuration allowing the specification -of a user defined build command step -for the selected file. In addition to the build command, the user may -specify any additional input file(s) -dependencies, the output file(s) generated by the build step, a -descriptive message to be displayed in the -build output when the command is executed, and a rule for how the -custom build step should be applied with -respect to other tools defined in the configuration, if any. Custom -build steps may be specified for any -file type, regardless of the project nature. -

Resource Properties, Managed Make, C/C++ Build, Custom Build Steps

-

-
-
Exclude from build
-
Excludes the selected file from being built with the selected -build configuration.
-
Configuration:
-
Specifies the selected build configuration from the list provided.
-
Resource Configuration settings, Custom Build Steps
-
Defines a custom build step for the selected file.
-
Custom Build Step Applicability
-
Disables the custom build step for the selected file, or applies -the custom build step, overriding any other tools defined for the -configuration.
-
Additional Input File Name(s)
-
Specifies a semicolon separated list of additional input files -required by this build command. The selected file is included by -default. Paths are interpreted as relative to the project directory.
-
Output File Name(s)
-
Specifies a semicolon separated list of output files produced by -this build command. Paths are interpreted as relative to the build -directory.
-
Command
-
Specifies a semicolon separated list of commands that will be -executed to perform this build step.
-
Description
-
Specifies an announcement string which will be echoed in the -build output when this build step is executed.
-
Restore Defaults
-
Returns any changes back to the settings of the selected -configuration.
-
Apply
-
Applies any changes.
-
-

Related reference
-C++ Project Properties, Managed Make -File, Info

-

Intel Copyright Statement

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_tool_settings.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_tool_settings.htm deleted file mode 100644 index 0fde36fd589..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_mfile_tool_settings.htm +++ /dev/null @@ -1,38 +0,0 @@ - - - - - - C/C++ Project Properties, Managed Make File, Build - - - -

C/C++ Project Properties, Managed Make File, C/C++ Build, Tool -Settings

-Customizes the tools and tool options used by the selected file in your -build configuration. -

C/C++ Project Properties, Managed Make File,  Build

-

-
-
Exclude from build
-
Excludes the selected file from being built with the selected -build configuration.
-
Configuration:
-
Specifies the selected build configuration from the list provided.
-
Resource Configuration settings, Tool Settings
-
Sets individual tool options for the selected file.
-
Restore Defaults
-
Returns any changes back to the settings of the selected -configuration.
-
Apply
-
Applies any changes.
-
-

Related reference
-C++ Project Properties, Managed Make -File, Info

-

-IBM Copyright Statement

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_modules_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_modules_view.htm deleted file mode 100644 index 4bafd780f89..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_modules_view.htm +++ /dev/null @@ -1,82 +0,0 @@ - - - - - - - -Modules view - - - - - - - -

Modules view

- -

The Modules view of the Debug -perspective lets you view information about the modules loaded in the current -debug session, including executables and shared libraries. The view consists -of two areas: the modules tree and the detail pane. The detail pane displays -the detail information for the module selected in the modules tree. Expanding a -module enables users to view the module's internals - functions, global variables, associated -source files, etc.

- -Modules view - -

Modules view toolbar options

- -

The table below lists the icons displayed in the Modules view toolbar.

- - - - - - - - - - - - -
IconNameDescription
Load Symbols for all modules iconLoad Symbols for All ModulesLoads the symbols of the all modules involved in the current session. This option does not affect the modules whose symbols are already loaded.
- -

Modules view context menu commands

- -

The table below lists the Modules context menu commands.

- - - - - - - - - - - - - - - - - -
IconNameDescription
load symbols for all iconLoad Symbols for AllLoads the symbols of the all modules involved in the current session. This option does not affect the modules whose symbols are already loaded.
 Find...Opens the Find dialog box to search the Modules view.
- -

Related concepts -
-Debug information

-

Related tasks -
-Debugging

-

Related reference -
-C/C++ Views

-
-IBM Copyright Statement
-Nokia Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_navigator_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_navigator_view.htm deleted file mode 100644 index 0c40db17a6f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_navigator_view.htm +++ /dev/null @@ -1,106 +0,0 @@ - - - - - - - Navigator view - - - - - -

Navigator view

-

The Navigator view provides a hierarchical view of the resources in the Workbench including hidden files.

-

Navigator View

- -

Toolbar

- -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconNameDescription
Minimize iconMinimizeMinimizes the Navigator view.
Maximize iconMaximizeMaximizes the Navigator view.
Back IconBackThis command displays the hierarchy that was displayed immediately prior to the current display.  - For example, if you Go Into a resource, then the Back command in the resulting display returns the view to the same hierarchy from which you activated the - Go Into command. The hover help for this button tells you where it will take you. This command is similar to the Back button in a web browser.
Forward IconForwardThis command displays the hierarchy that was displayed immediately after the current display.  - For example, if you've just selected the Back command, then selecting the Forward command in the resulting display returns the view to the same hierarchy from which you activated the Back command. The - hover help for this button tells you where it will take you. - This command is similar to the Forward button in a web browser.
Up IconUpThis command displays the hierarchy of the parent of the current highest level resource. The hover help for this button tells you where it will take you.
Collapse All IconCollapse AllThis command collapses the tree expansion state of all resources in the view.
Link with Editor IconLink with EditorThis command toggles whether the Navigator view selection is linked to the active editor. - When this option is selected, changing the active editor will automatically update the Navigator selection to the resource being edited.
Menu IconMenuClick the black upside-down triangle icon to open a menu of items specific to the Navigator view.

-
-
Select Working Set
-
Opens the Select Working Set dialog to allow selecting a working set for the Navigator view.

-
Deselect Working Set
-
Deselects the current working set.

-
Edit Active Working Set
-
Opens the Edit Working Set dialog to allow changing the current working set.

-
Sort
-
This command sorts the resources in the Navigator view according to the selected schema:
-
    -
  • By Name:  Resources are sorted alphabetically, according to the full name of the resource (e.g., A.TXT, then B.DOC, then C.HTML, etc.)
  • -
  • By Type:  Resources are sorted alphabetically by file type/extension (e.g., all DOC files, then all HTML files, then all TXT files, etc.).
  • -


-
Filters
-
This command allows you to select filters to apply to the view so that you can show or hide various resources as needed. - File types selected in the list will not be shown in the Navigator.

-
Link with Editor
-
See the toolbar item description above.

-

- -

In addition to these menu items, the Navigator view menu shows a list of recently used working sets that have been selected in the view.

- -

Related references -
C/C++ Views and Editors

-
- -

 IBM Copyright Statement

- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz.htm deleted file mode 100644 index 18d725ce476..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz.htm +++ /dev/null @@ -1,55 +0,0 @@ - - - - - - - New Project Wizard - - -

New Project Wizard

-

The New Project wizard helps you create a new C or C++ project in the workbench. -To access the wizard, from the menu bar select -File > New > Project. -The New Project wizard appears: -

- -

New Project Wizard

- -

With the New Project wizard you can choose to:

-
    -
  • Create C Project
  • -
  • Create C++ Project
  • -
-

-You can either provide your makefile to build new project, -or let CDT generate makefile automatically. -In CDT 3.x, there were 2 different project types: -"Managed make" and "Standard make", respectivelly -

-

-Currently, these features are combined in the single project. -In most cases, you can switch makefile generation ON or OFF -at any time after project creation. -

- -


-CDT projects
-

- -

Related tasks
-Tutorial: Creating a simple application
-

- -

Related reference
-Set Project Name and Location
-Select Project type
-Select toolchain
-Select configurations
-

-Intel Copyright Statement -

- -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_config.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_config.htm deleted file mode 100644 index 992b2887cf3..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_config.htm +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - New Project Wizard, Select configurations - - - -

New Project Wizard, Select configurations

-

You can select configuration(s) from this page of the wizard.

-

New Project Wizard, Select configurations

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameFunction
Project typeSelected project type.
Tool-chainsOne or more selected tool chains
ConfigurationsList of all build configurations to be created. - Check items you want to create. - At least one configuration must be checked. -
Select allChecks all configurations
Deselect allUnchecks all configurations
Advanced settings ...Displays properties dialog for new project.
-

- -


-CDT projects
-

- -

Related tasks
-Tutorial: Creating a simple application
-

- -

Related reference
-Set Project Name and Location
-Select Project type
-Select toolchain
-Select configurations
-

-Intel Copyright Statement -

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_name.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_name.htm deleted file mode 100644 index d7dbb81e2ab..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_name.htm +++ /dev/null @@ -1,61 +0,0 @@ - - - - - - New Project Wizard - Select Name and Location - - - -

New Project Wizard - Select Name and Location

-

Select a name for the project. You can also enter a new path for -your project by deselecting the Use Default Location checkbox -and entering the new path in the Location text box.

-

New Project Wizard - Select Name and Location

-

- - - - - - - - - - - - - - - - - - - -
NameFunction
NameSpecifies the name of the project.
Use Default LocationWhen selected, creates the new project in the default -workspace location.
LocationIf Use Default Location is not selected, specifies -the location where the project is to be created.
-

- -


-CDT projects
-

- -

Related tasks
-Tutorial: Creating a simple application
-

- -

Related reference
-Set Project Name and Location
-Select Project type
-Select toolchain
-Select configurations
-

-Intel Copyright Statement -

- - -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_toolchain.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_toolchain.htm deleted file mode 100644 index febc2023cba..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_toolchain.htm +++ /dev/null @@ -1,57 +0,0 @@ - - - - - - New Project Wizard, Select a toolchain - - - -

New Project Wizard, Select a toolchain

-

You can select toolchain(s) from this page of the wizard. A toolchain is a set of tools (such as a compiler, linker, and assembler) intended to build your project. - Additional tools, such as a debugger, can be associated with a toolchain. - There can be several toolchains available, depending on the project type you specify, and the compilers installed on your system.

-
-

New Project Wizard, Select a toolchain

-

- - - - - - - - - - - - - - - -
NameFunction
ToolchainSpecifies toolchains available for selected project type.
Show Project Types and toolchains only if they are supported on the platformWhen selected (default), the list is filtered so that only toolchains - that are buildable on the host system are shown.
- If it is not selected, the list displays all known toolchains.
-

- -


-CDT projects
-

- -

Related tasks
-Tutorial: Creating a simple application
-

- -

Related reference
-Set Project Name and Location
-Select Project type
-Select toolchain
-Select configurations
-

-Intel Copyright Statement -

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_type.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_type.htm deleted file mode 100644 index 4990b4c3846..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_new_proj_wiz_type.htm +++ /dev/null @@ -1,56 +0,0 @@ - - - - - - New Project Wizard, Select a Project Type - - - -

New Project Wizard, Select a Project Type

-

You can select a type of project from this page of the wizard. This project type will determine the toolchain and data, and tabs that the CDT uses. Once created, C/C++ projects display in the C/C++ Projects view.

-

New Project Wizard, Select a Project Type

-

- - - - - - - - - - - - - - - -
NameFunction
Project TypeSpecifies a project type from the list provided.
Show Project Types and toolchains only if they are supported on the platformIf checked (default), list is filtered so that only project -types that are buildable on the host system are shown.
- If unchecked, lists all known project types in the Project - Type list.
-

- -


-CDT projects (detailed information about project types)
-

- -

Related tasks
-Project types selection
-Tutorial: Creating a simple application
-

- -

Related reference
-Set Project Name and Location
-Select Project type
-Select toolchain
-Select configurations
-

-Intel Copyright Statement -

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_behavior.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_behavior.htm deleted file mode 100644 index abd1cdd37f3..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_behavior.htm +++ /dev/null @@ -1,78 +0,0 @@ - - - - - - -Makefile Project - Behavior page - - - - -

Makefile Project - Behavior page

-

Use the Behavior page in the Makefile Projects preference panel to define build behavior.

-

Makefile project - behavior page

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Makefile Project - Behavior options -
OptionDescription
Stop on first build error Stops the build when an error occurs.
Use parallel build Activate to generate parallel builds.
Use optimal jobs number Activate to let the system determine the optimal number of parallel jobs to perform.
Use parallel jobs Set the maximum number of parallel jobs to perform.
Build on resource save (Auto build) Defines what the standard builder will call when a file is saved, it is not recommended to enable Auto Build for C/C++ projects.
Make build target Define what the standard builder will call by default when told to build, rebuild, clean, etc. You can change these so that new projects will use different targets if the defaults are not appropriate. Click Variables to open the Select build variable dialog.
Build (Incremental build) Defines what the standard builder will call when an incremental build is performed.
CleanDefines what the standard builder will call when a clean is performed.
-

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings

-

Related reference
- New CDT Project Wizard

-
-IBM Copyright Statement
-Nokia Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_buildset.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_buildset.htm deleted file mode 100644 index bf296fc0785..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_buildset.htm +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - -Makefile Project - Builder Settings page - - - - - -

Makefile Project - Builder Settings page

-

Use the Builder Settings page in the Makefile Projects preference panel to define build settings.

-

Make Builder Preferences window

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Makefile Project - Builder Settings options -
OptionDescription
Builder type Select the type of builder used by the project.
Use default build command Select this checkbox to use the default make command. Clear the check box to specify a new make command.
Build command If you clear the Use default build command checkbox type a new make command in this field.
Generate Makefiles automatically Activate to generate makefiles automatically during a build operation.
Expand Env. Variable Refs in Makefiles Activate to expand environment variable references in the generated makefile.
Build directory Type the build directory path, or click Workspace, File system, or Variables to specify the build directory.
-

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings

-

Related reference
- New CDT Project Wizard

-
-IBM Copyright Statement
-Nokia Copyright Statement -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_def_symb.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_def_symb.htm deleted file mode 100644 index 8cb2779458f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_def_symb.htm +++ /dev/null @@ -1,58 +0,0 @@ - - - - - - -Paths and symbols page, C/C++ Properties window - - - - - - - -

Manage defined symbols dialog box

- -

You can manage preprocessor symbols from the Manage defined symbols dialog box.

-

Manage Defined Symbols Dialog Box

-
-
New
-
Enter a new defined symbol.
-
Edit
-
Modify selected defined symbol.
-
Remove
-
Remove selected defined symbol.
-
Restore
-
Restore a previously removed defined symbol.
-
Delete
-
Delete a defined symbol.
-
Delete All
-
Delete all defined symbols.
- -
- -

Related concepts -
-Build overview

-

Related tasks -
-Including paths and symbols

-

Related reference -
-Project properties

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_discovery_options.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_discovery_options.htm deleted file mode 100644 index 8cfdf7bdaa5..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_discovery_options.htm +++ /dev/null @@ -1,81 +0,0 @@ - - - - - - -Makefile Project - Discovery Options page - - - - - -

Makefile Project - Discovery Options page

- -

Use the Discovery Options page in the Makefile Projects preference panel to configure various options for the scanner configuration.

-

Makefile project - discovery options page

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Makefile Project - Discovery Options page -
OptionDescription
Discovery profiles scope Define the scope as configuration-wide or per language for this profile.
Automate discovery of paths and symbolsActivate this checkbox to scan the build output to populate the paths and symbol tables.
Report path detection problems Activate this checkbox to report all path detection problems.
Discovery profile Select the discovery profile to use for paths and symbol detection.
Enable build output scanner info discovery Activate this checkbox to configure the scanner to parse the output from a build.
Local build output from file Click Browse to select a file from disk or click Variables to open the Select Variables window to define the build output file.
Enable generate scanner info command Activate this checkbox to specify use of the default scanner information command
Compiler invocation command Type the command that invokes the compiler, for example: gcc, or click Browse to locate it.
-

Related concepts -
-Build overview

-

Related tasks -
-Including paths and symbols

-

Related reference -
-New CDT Project Wizard

-
-IBM Copyright Statement
-Nokia Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_parser_binary.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_parser_binary.htm deleted file mode 100644 index 1f7d673711a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_parser_binary.htm +++ /dev/null @@ -1,64 +0,0 @@ - - - - - - -Makefile Project - Binary Parsers page - - - - - - -

Makefile Project - Binary Parsers page

- -

Use the Binary Parser page in the Makefile Project preference panel to manage the binary parsers available to projects.

-

Binary Parser Preferences Panel

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Makefile Project - Binary Parsers options -
OptionDescription
Binary ParserSelect binary parsers from the list, and changed the order in which they are used.
Move Up Moves the selected binary parser higher in the list.
Move Down Moves the selected binary parser lower in the list.
Binary Parser OptionsIf a binary parser has parser options you can define them in this section.
-

Related concepts -
-Build overview

-

Related tasks -
-Selecting a binary parser

-

Related reference
- New CDT Project Wizard

-
-IBM Copyright Statement
-Nokia Copyright Statement -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_parser_error.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_parser_error.htm deleted file mode 100644 index 7380d82f057..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_parser_error.htm +++ /dev/null @@ -1,81 +0,0 @@ - - - - - - -Makefile Project - Error Parsers page - - - - - - -

Makefile Project - Error Parsers page

- -

Use the Error Parsers page in the - - Makefile Projects preference panel to define a list of error parsers that will be assigned to a new Makefile Project - created by a New CDT Project Wizard.

- -

Make Error Parser Preferences Dialog Box

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Makefile Project - Error Parser options -
OptionDescription
Error ParsersLists the various error parsers which can be enabled or disabled.
Move Up Moves the selected error parser higher in the list.
Move Down Moves the selected error parser lower in the list.
Check All Selects all error parsers.
Uncheck All Clears all error parsers.
- -

Related concepts -
Build overview -

- -

Related tasks -
Tracking down compilation errors -
Tuning Error Parsers -

- -

Related reference -
New CDT Project Wizard -
Console View -
Problems View -

- -
-IBM Copyright Statement
-Nokia Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_platf.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_platf.htm deleted file mode 100644 index 10589223153..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_newproj_platf.htm +++ /dev/null @@ -1,40 +0,0 @@ - - - - - - - - -Target platform, C/C++ Properties window - - - - -

Target platform, C/C++ Properties window

- -

The Target platform page of the C/C++ Properties window lets you select the -select the platform on which you plan to deploy your program for managed make -projects.

- -
-
Platform
-
Specifies the deployment platform for your project.
-
Configurations
-
Specifies the configuration(s) for your project.
-
- -

Related concepts -
-Build overview

-

Related tasks -
-Selecting a deployment platform

-

Related reference -
-Project properties

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_open_element.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_open_element.htm deleted file mode 100644 index d236ba46f22..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_open_element.htm +++ /dev/null @@ -1,25 +0,0 @@ - - - - - - - Open Element - - - - -

Open Element

- -

Use Open Element to open up the declaration of C/C++ classes, structures, unions, typedefs, enumerations, namespaces, functions, methods and variables.

- -

Open Element Dialog Box

- - - -

-IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_outline_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_outline_view.htm deleted file mode 100644 index 097ece4ca95..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_outline_view.htm +++ /dev/null @@ -1,170 +0,0 @@ - - - - - - -Outline view - - - - - -

Outline view

- -

The Outline view displays an outline of a structured C/C++ file that is currently -open in the editor area, by listing the structural elements.

- -

Outline View

- - -

Outline view toolbar icons

- -

The table below lists the icons displayed in the Outline view toolbar.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconDescription
Collapse All IconCollapse All
Sort items alphabetically IconSort items alphabetically
Hide Fields IconHide Fields
Hide Static Members IconHide Static Members
Hide Non-Public Members IconHide Non-Public Members
Hide Inactive Elements IconHide Inactive Elements
- -

Outline view icons

- -

The table below lists the icons displayed in the Outline view.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Icon - Description
- Class iconClass
- Namespace iconNamespace
- Macro Definition iconMacro Definition
- Enum iconEnum
- Enumerator iconEnumerator
- Variable iconVariable
- Field private iconField private
- Field protected iconField protected
- Field public iconField public
- Include iconInclude
- Method private iconMethod private
- Method protected iconMethod protected
- Method public iconMethod public
- Struct iconStruct
- Type definition iconType definition
- Union iconUnion
- Function iconFunction
- -

Related concepts -
-Outline view

-

Related tasks -
-Displaying C/C++ file components in the -C/C++ Projects view

-

Related reference -
-Views

-
-IBM Copyright Statement -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build.htm deleted file mode 100644 index 54384e90943..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build.htm +++ /dev/null @@ -1,33 +0,0 @@ - - - - - - -Build preferences - - - - - - -

Build preferences

- -

Use the Build preference panel to define build options.

- -

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference
-Views

-
-IBM Copyright Statement
-Nokia Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build_error_parsers.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build_error_parsers.htm deleted file mode 100644 index 7d41f8ecd8b..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build_error_parsers.htm +++ /dev/null @@ -1,146 +0,0 @@ - - - - - - -Error Parser Preferences - - - - - - -

Error Parser Preferences

- -

Use the Error Parsers Tab on - Build preference panel to define global error parsing options. -

-

Error Parsers scan build output looking for potential error or warning messages. - They create Problem Markers which help to visualize problems for users. - Most of Error Parsers scan build output line by line and check if the line match a certain pattern. - This preference page lets define those patterns. -

-

Build Preferences Panel

- - - - - - - - - - - - - - - - - - - - - -
Error Parsers
GroupDescription
Error ParsersLists the available error parsers and the order in which they are called. -
    -
  • Click Add... to add additional parsers.
  • -
  • Click Edit... to show the Error Parser Options list if applicable.
  • -
  • Click Delete to remove a parser.
  • -
  • Click Move Up to move a parser earlier in the call order.
  • -
  • Click Move Down to remove a parser later in the call order.
  • -
Error Parser OptionsLists the patterns used by the selected error parser and the order in which they are called. -
    -
  • Click Add... to add a new pattern to the list.
  • -
  • Click Delete to remove a pattern.
  • -
  • Click Move Up to move a pattern earlier in the call order.
  • -
  • Click Move Down to remove a pattern later in the call order.
  • -
  • Click a pattern to select it for editing.
  • -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Error Parser Patterns
FieldDescription
SeverityDefines severity of problem marker to be generated. The choice is one of following: -
- Error Error -
Warning Warning -
InfoInfo -
Ignore Ignore - use this option - to suppress generating a marker. -
-
PatternJava regular expression pattern. This pattern should define groups in parentheses for using - in File, Line, and Description fields. -
The pattern is assumed to start from the beginning of line and end at the end, - so it is unnecessary to specify starting "^" or ending "$" in the pattern. -
FileDefine a file which will be associated with the problem marker. -
This is a replacement pattern. Use $ notation - to refer to one of the the groups defined in Pattern, - i.e. $1, $2,$3 etc. -
LineDefine a line in the file which will be associated with the problem marker. -
This is a replacement pattern like for File field. -
DescriptionDefine a description which will be assigned to the problem marker. -
This is a replacement pattern like for File field. -
ConsumeThis field defines if the pattern stops processing of output line (consumes it). - By default it does (field is empty). - Use No if the same line needs to be processed by several patterns. -
- -

Related concepts -
Build overview

-

- -

Related tasks -
Tracking down compilation errors -
Defining Project Build settings -
Building projects -

- -

Related reference -
Project properties, Error Parsers tab -
Console View -
Problems View -

- -
-IBM Copyright Statement
-Nokia Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build_scanner_discovery.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build_scanner_discovery.htm deleted file mode 100644 index 076214d57f7..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build_scanner_discovery.htm +++ /dev/null @@ -1,239 +0,0 @@ - - - - - - - -Scanner Discovery Preferences - - - - - - -
-

Scanner Discovery Preferences

- -

General

- -

-Use the Discovery Tab on - Build preference panel to define global scanner discovery options. -

-

-In the Discovery tab you can see a list of Language Settings Providers. Language Settings Providers supply Language Settings such as include paths and preprocessor macros -for the indexer and other components of CDT. -

-

Scanner Discovery Preferences Panel

- -

-A user can define some properties for global (or "shared") providers on this preference. Note that providers can be either shared or defined per configuration. -Properties for non-shared providers can be defined in Project properties: Preprocessor Include Paths, Macros, etc. -

- - - - - - - - - - - - - - - - - - - - - - - - - -
Discovery tab
GroupDescription
Language Settings ProvidersLists the available language settings providers.
Clear EntriesClick to clear all entries of the selected provider. - This operation takes effect after pressing "Apply" or "OK". - Normally this will trigger a rerun if the provider supplies built-in compiler settings. - Build output parsers will regain language settings after build while parsing new build output. -
This operation might be unavailable if the provider does not have any language settings. - Some providers may not have the capability to clear. -
ResetClick to reset options of the selected provider to default values. This operation also clears the provider entries. - The button can be enabled if some options in "Language Settings Provider Options" panel were changed. -
- -
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Kinds of Language Settings Providers
ProviderDescription
Build Output Parser ProviderBuild Output Parser Provider parses output of build - looking for include paths and macros passed to the compiler via compiler options. - Include files, macro files passed the the compiler and some other compiler options are normally also recognized. -
- For gcc, include paths commonly passed with "-I" option and macros with "-D" option. - The language settings found by BOP are available after the build is finished. -
Builtin Compiler Settings ProviderBuiltin Compiler Settings Provider launches the compiler with special options that instruct the compiler - to print built-in settings such as include paths to internal system headers and the list of internally predefined macros. - This provider is usually shared between projects in workspace and runs in background once. - When it is finished the language settings are available to all the projects between which it is shared. -
Managed Build Language Settings ProviderMBS Provider supplies language settings provided by Managed Build System. -
User Language Settings ProviderA user has an opportunity to enter language settings manually using this provider. - User Language Settings Provider should be normally the first in the list so these settings override settings supplied by other providers. -
Contributed PathEntry ContainersThis provider is here for backward compatibility support of PathEntry Containers from older versions of CDT. - Using this method is not recommended. -
Contributed ScannerInfo EntriesThis provider is here for backward compatibility support of ScannerInfo Entries from older versions of CDT. - Using this method is not recommended. -
- -
- -

Language Settings Providers Options

-

-Language settings providers can have options that affect the behavior of a provider. These options are presented in "Language Settings Provider Options" panel. -

- -

Build Output Parser Options

-

BOP Options Panel

- - - - - - - - - - - - - - - - - - - - - - - - -
Build Output Parser Options
ProviderOptions
Compiler command patternThe pattern which is used to recognize compiler command in build output. -
Note that the pattern is Java regular expression pattern, it is NOT globbing pattern used to expand file name in command line. -
Container to keep discovered entriesThe discovered entries can be associated with the project, enclosing folder or the file itself.
Use heuristics to resolve pathsThe provider will try to find the best match for the discovered path in the project - or workspace trying several heuristics. If disabled, the discovered paths will stay as they appear in build output. -
-
- -

Builtin Compiler Settings Provider Options

-

Specs Detector Options Panel

- - - - - - - - - - - - - - - - - - - - - - - - -
Builtin Compiler Settings Provider Options
ProviderOptions
Command to get compiler specsThe command to make the compiler print built-in settings. - Following variables are recognized: -
    -
  • ${COMMAND} - compiler command from the tool-chain, such as "gcc".
  • -
  • ${FLAGS} - applicable compiler flags from the tool-chain, such as language dialect flag "-std=c++0x".
  • -
  • ${ALL_FLAGS} - all compiler flags from the tool-chain, except those explicity excluded, - either by tool provider or by being entered in the "Other flags (excluded from discovery)" in the "Miscellaneous" tool page.
  • -
  • ${INPUTS} - indicates normally an empty specs file required by the compiler. - If no such file exists the file gets created temporarily in Eclipse workspace plugin area. -
  • -
  • ${EXT} - an extension for the language to discover built-in settings. - A provider can be associated with multiple languages and it will run the command for each language. -
  • -
-
BrowseUse this button to locate the compiler on the file system. - The result is put into "Command to get compiler specs" input field. -
Allocate console in the Console ViewEnable to troubleshoot problems running the command. - When enabled, output of each run of the provider will be directed to a special console in the Console View. - See also Scanner Discovery - Console View. -
- -

-To see the entries a provider discovered, go to project properties (or the properties of the resource of interest), see -Project properties: Preprocessor Include Paths, Macros, etc. - -

- -

-A hint: After compiler upgrade re-discover changed settings with "Clear Entries" of the appropriate provider. -

- - -

Related concepts
-Scanner Discovery
-C/C++ Indexer
-

- -

Related tasks
-Setting up include paths and macros for C/C++ indexer
-

- -

Related reference
-C/C++ Project properties: Preprocessor Include Paths, Macros, etc.
-

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build_vars.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build_vars.htm deleted file mode 100644 index b9ab714f60e..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_build_vars.htm +++ /dev/null @@ -1,60 +0,0 @@ - - - - - - - Build Variables preferences - - - - - - -

Build Variables preferences

- -

Use the Build Variables preference panel to add, edit, or remove local build variables. Local build variables are displayed in bold text.

-

Build Variables Preferences Page

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Build Variables Preference Options
OptionDescription
Add...Click to add a new build variable in the Define a New Build Variable dialog box.
Edit...Click to edit the selected build variable.
RemoveClick to remove the select build variable.

- NOTE: System variables cannot be removed.
Show system variablesEnable to display system variables in the variables list.
- - -

Related reference
-Build preferences

-
-Nokia Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_multi_cfg.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_multi_cfg.htm deleted file mode 100644 index c3bca8e9479..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_multi_cfg.htm +++ /dev/null @@ -1,68 +0,0 @@ - - - - - - - Multi-Configuration Edit preferences - - - - - -

Multi-Configuration Edit preferences

-

Use the Multi-Configuration Edit preference panel to simultaneously edit properties for multiple project configurations. Its possible to select one or more configurations for editing.

-

But, then we deal with string list property values, it is not obvious how to concatenate them, if they differ.

-

Multi-Configuration Edit preferences tab

- - - - - - - - - - - - - - - - - - - - - - - -
Property Pages Settings Preference Options
OptionDescription
String list Display ModeSpecifies how values are shown. The two options are: -
    -
  • Conjunction shows common elements only, so if 1st configuration has - value <A, B, C> and 2nd configuration has <B, C, D>, <B, C> will be shown. -
  • Disjunction shows all existing elements except doubles, so if 1st configuration has - value <A, B, C> and 2nd configuration has <B, C, D>, <A, B, C, D> will be shown. -
- Note that Display mode can be changed directly on each tab which deals with string lists. - Result is immediate: data on the tab is refreshed according to selected mode.
String list Write ModeSpecifies how values are saved. The two options are: -
    -
  • Modify mode adds, changes or removes elements affected by user's actions. - Elements which were not touched by user are left unchanged.
    - Example: cfg1 has <A, B, C>; cfg2 has <B, C, D>.
    - User removed B and added F.
    - Result: cfg1 has <A, C, F>; cfg2 has <C, D, F>. -
  • Replace mode puts currently visible elements to all configurations. - Old contents will be lost.
    - Example: cfg1 has <A, B, C>; cfg2 has <B, C, D>.
    - Visible list depends of Display mode: <B, C> or <A, B, C, D>.
    - User removed B and added F.
    - Result: both cfgs will contain either <C, F> or <A, C, D, F> depending of Display mode. -
- Note that Write mode can be changed directly on each tab which deals with string lists.
- -

Related reference
-Property Pages Settings preferences

-
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_prop_pages.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_prop_pages.htm deleted file mode 100644 index ab469cff846..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_prop_pages.htm +++ /dev/null @@ -1,84 +0,0 @@ - - - - - - - Property Pages Settings preferences - - - - - -

Property Pages Settings preferences

- -

Use the Property Pages Settings preference panel to set the behaviors of CDT property pages.

-

Property Pages Settings Preference Panel

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Property Pages Settings Preference Options
OptionDescription
Show 'Manage Configurations...' buttonShows or hides corresponding button, normally placed on every property page.
- If this button is hidden, Manage operation can be accessed from Main Menu or Context Menu.
Display 'Include Files' tabDisplays a tab under 'Paths & Symbols' showing files which are included by default. - These included files will be parsed before source, even if they're not explicitly - #include'd by the source file. Corresponds to the '-include' switch on GNU compilers.
Display 'Data hierarchy' tabDisplays auxiliary tab which allows browsing data of project configurations. - This feature is useful for debug purposes mostly, so it's disabled by default.
Display tool option tips of 'Tool Settings' tab at fixed location
Display 'Tool Chain Editor' tabShows or hides corresponding tab. Normally, users need not to edit tool chains manually.
Save Property Dialog BoundsDefines how property dialog parameters are preserved: -
    -
  • Save size only - position is set by system
  • -
  • Save size and position - next time, dialog is shown at the same place with the same size
  • -
  • Do not save at all - size and position is set by system each time dialog is shown
  • -
Discovery Profiles Naming RuleDiscovery profiles have unique IDs, but their names may be duplicate, - especially if they are contributed by different developers. So there - are 4 way to distinguish them in the list on Discovery tab: -
    -
  • Show disc. page names if they are unique. Else names + profile IDs.
  • -
  • Show disc. page names if they are unique. Else show profile IDs.
  • -
  • Always show names + profile IDs
  • -
  • Always show profile IDs only
  • -
- -

Related reference
-Multi-Configuration Edit preferences

- -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_task_tags.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_task_tags.htm deleted file mode 100644 index eff22be6717..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_task_tags.htm +++ /dev/null @@ -1,79 +0,0 @@ - - - - - - - Task Tags preferences - - - - - -

Task Tags preferences

- -

Use the Task Tags preference panel to configure global todo tags for C/C++ editor views.

-

Task Tags Preferences

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Task Tags Preference Options
OptionDescription
- New... - Opens the New Task Tag dialog box to create a new todo task tag.
-

New Task Tag Dialog Box

-
- Edit... - Opens the Edit Task Tag dialog box to modify the selected tag. -
- Remove - - Removes the selected task tag. -
- Default - - Sets the selected task tag as the default tag. The default tags appears in bold text. -
- Case sensitive task tag names - - Enable to enter task tags using the same case as the tag. Disable to always use the defined case for the tags. -
- -

Related reference
-Reference -


-Nokia Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_wizard_defaults.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_wizard_defaults.htm deleted file mode 100644 index e5b9b46ffc0..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_wizard_defaults.htm +++ /dev/null @@ -1,34 +0,0 @@ - - - - - - - CDT Project Wizard Defaults preferences - - - - -

CDT Project Wizard Defaults preferences

- -

These settings affect CDT New Project Wizard behaviour.

-

CDT Project Wizard Defaults preferences tab

-
-
Show only supported toolchains, by default
-
Allows to filter out toolchains which are not supported by system.
- If disabled, all toolchains known to CDT are shown.
- Note that this mode can be switched directly in Project Wizard dialog. -
-
Group old-style toolchains to <Others> folder
-
Old-style toolchains do not distinguish project types (executable, shared library or static library).
- So they can be either placed to list's root, or grouped in <Others> folder on the left pane of Wizard. -
-
Restore Defaults
-
Sets all parameters to default values
-
Apply
-
Saves current settings.
-
- -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_wizard_toolchains.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_wizard_toolchains.htm deleted file mode 100644 index dc774ebdab1..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_pref_wizard_toolchains.htm +++ /dev/null @@ -1,63 +0,0 @@ - - - - - - - New CDT Project Wizard preferences - - - - - -

New CDT Project Wizard preferences

- -

Use the New CDT Project Wizard to define which toolchains are selected in New CDT Project Wizard by default.

-

CDT Project Wizard Toolchains preferences tab

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
New CDT Project Wizard Preference Options
OptionDescription
Project typesThe same project types list as shown in Project Wizard.
ToolchainThe same list of toolchains as shown in Project Wizard.
Make toolchain(s) preferredMakes the selected toolchain(s) preferred.
-
    -
  • Preferred toolchains are marked by arrow icon (">").
  • -
  • In the Project Wizard dialog, preferred toolchain is selected by default.
  • -
  • If there are more than one toolchain preferred, the first of them is selected.
  • -
  • If there are no toolchains preferred, the first in the whole list is selected.
  • -
Make toolchain(s) not preferredRemoves preference mark from selected toolchain(s).
Show project types and toolchains only if they are supported on the platformThe same control as on Project Wizard page. Defines whether unsupported project types and toolchains are hidden or shown.
- -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_problems_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_problems_view.htm deleted file mode 100644 index 96afc19ae83..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_problems_view.htm +++ /dev/null @@ -1,55 +0,0 @@ - - - - - - - Problems view - - - - - -

Problems view (C/C++)

- -

Use the Problems view to display any errors encountered during a build.

-

Problems View

- -

Errors are passed up from your C++ compiler. The Problems view lists the error, filename and folder. -If you select an error the associated file will open in a C/C++ Editor view, and the cursor and text highlighting will display the line where the error was encountered.

- -

C/C++ Perspective in Eclipse showing code errors

- -

Problems view toolbar options

-

The table below lists the toolbar options displayed in the Problems view.

- - - - - - - - -
IconCommandDescription
Menu iconView MenuClick to open a menu of items specific to the view, including:
-
    -
  • Show - specify which errors or warnings are shown
  • -
  • Group By - specify error grouping
  • -
  • Sort By - specify how errors are sorted
  • -
  • New Problems View - create a new Problems view
  • -
  • Configure Contents... - opens the Configure Contents dialog box
  • -
  • Columns... - opens the Configure Columns dialog box
  • -
  • Preferences - opens the Preferences dialog box
  • -
-
- -

Related references -
C/C++ Views -
Problems View (Workbench)

-
-

-IBM Copyright Statement
-Nokia Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_project_explorer_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_project_explorer_view.htm deleted file mode 100644 index 0847ce1cc3b..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_project_explorer_view.htm +++ /dev/null @@ -1,232 +0,0 @@ - - - - - - -Project Explorer View - - - - - -

Project Explorer view

-

The Project Explorer view displays, in a tree structure similar to the C/C++ Projects view, but it is not limited to C and C++ projects. In this view you can do the following: -

    -
  • Browse the elements of C/C++ source files
  • -
  • Open files in the editor view
  • -
  • Open projects in a new window
  • -
  • Create new projects, classes, files, or folders
  • -
  • Manage existing files (cut, paste, delete, move or rename)
  • -
  • Restore deleted files from local history
  • -
  • Import or Export files and projects
  • -
- -

Files that you select in the Project Explorer view affect the information that is displayed in other views.

-

Right-click on any resource in the Project Explorer view to open a pop-up menu that allows you to perform operations such as copying, moving, creating new resources, comparing resources with each other, or performing team operations.

-

Project Explorer view

- - -

Project Explorer toolbar

-

The table below lists the toolbar options displayed in the Project Explorer view.

- -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconNameDescription
Minimize iconMinimizeMinimizes the view.
Maximize iconMaximizeMaximizes the view.
Collapse All IconCollapse AllThis command collapses the tree expansion state of all resources in the view.
Link with Editor IconLink with EditorThis command toggles whether the view selection is linked to the active editor. - When this option is selected, changing the active editor will automatically update the selection to the resource being edited.
Menu IconMenuClick the black upside-down triangle icon to open a menu of items specific to the view.

-
-
Top Level Elements
-
Choose whether to show working sets or projects as top level elements. - Choosing working sets allows easy grouping of projects in large workspaces.

-
Select Working Set
-
Opens the Select Working Set dialog to allow selecting a working set for the view.

-
Deselect Working Set
-
Deselects the current working set.

-
Edit Active Working Set
-
Opens the Edit Working Set dialog to allow changing the current working set.

-
Package Presentation
-
Choose to display packages in flat or hierarchical form.

-
Customize View
-
This command allows customization of view filters and content modules. - The previous will allow you to suppress the display of certain types of files - while the later will allow entirely new types of content to be shown in the view.

-
Link Editor
-
See the toolbar item description above.

-

- -

The Project Explorer view is provided by the Eclipse Platform. See the Workbench User Guide for more information.

- -

Project Explorer view icons

- -

The table below lists the icons displayed in the Project Explorer view for C/C++ content.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconDescription
- C or C++ file iconC or C++ file
- Executable file iconDebuggable executable file
- C or C++ object file iconObject file
- Class iconClass
- Macro Definition iconMacro Definition
- Enum iconEnum
- Enumerator iconEnumerator
- Variable iconVariable
- Field private iconField private
- Field protected iconField protected
- Field public iconField public
- Include iconInclude
- Makefile iconMakefile
- Method private iconMethod private
- Method protected iconMethod protected
- Method public iconMethod public
- Namespace iconNamespace
- Namespace declared iconNamespace declared
- Struct iconStruct
- Type Definition iconType definition
- Union iconUnion
- Function iconFunction
- -

Related concepts -
Project file views -

- -

Related tasks -
Displaying C/C++ file components in the Project Explorer view -
Hiding files by type in the Project Explorer view

- -

Related references -
C/C++ Projects view

- -
-

-IBM Copyright Statement -

- -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_all.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_all.htm deleted file mode 100644 index 467d30798e5..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_all.htm +++ /dev/null @@ -1,68 +0,0 @@ - - - - - - C/C++ Project Properties, Configuration management - - - -

C/C++ Project Properties, Configuration management

-All C/C++-specific property pages have unified controls -to handle configurations. - -

C/C++ Project Properties, Configurations management.

-

- -
- -
- - - - - - - - - - - - - - - - - - -
Configuration management properties
ConfigurationSpecifies the type of configuration(s) for the selected project. A Debug configuration lets you see what's going on "inside" a program as it executes. To debug your application, you must use executables compiled for debugging. These executables contain additional debug information that lets the debugger make direct associations between the source code and the binaries generated from the original source. A Release configuration provides the tools with options set to create an application with the best performance.
Manage configurationsOpens the Manage Configurations dialog where you can set which configurations are active based on the toolchain(s) that were specified for the selected project. In addition, you can also create new configurations, rename an existing configuration, or remove ones that are no longer required. -

Note:The Configuration selection that you specify in this dialog (unlike the behavior of CDT 3.x) affects only these property pages. This means that the selected configuration is not made the active configuration (the one used to build project).

-
- -

-Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build.htm deleted file mode 100644 index e446b5934fa..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build.htm +++ /dev/null @@ -1,216 +0,0 @@ - - - - - - - C/C++ Project Properties, C/C++ Build - - - - -

C/C++ Project Properties, C/C++ Build

-

This page serves as the main window that contains all builder-specific property pages. -In addition, directly from this window you can define preferences for the Builder settings and Behaviour properties. -

-

Note: Modifying some settings, such as the Generate makefiles automatically option, might affect other parameters (setting them from enabled to disabled in some situations) -and, moreover, change the visibility of other property pages. -

- -

C/C++ Project Properties, C/C++ Build

- - -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Builder settings preferences
ConfigurationClick here for its description.
Manage configurationsClick here for its description.
Builder typeSpecifies the type of builder to use: Internal builder (builds C/C++ programs using a compiler that implements the C/C++ Language Specification) and External builder (external tools let you configure and run programs and Ant buildfiles using the Workbench, which can saved and run at a later time to perform a build).
Use default build commandWhen enabled, this option indicates that you want to use the default make command. When disabled, it indicates the use of a new make command. This option is only available when the Build type option is set to External.
Build commandSpecifies the default command used to start the build utility for your specific toolchain. Use this field if you want to use a build utility other than the default make command (when the Use default build command is not selected the field is active, and when you use an external builder or a custom makefile, you can provide your specific commands).
VariablesOpens the Select build variable dialog where you can add environment variables and custom variables to the build command. -

C/C++ Project Properties, C/C++ Build, Select build variable

-
-
Generate Makefiles automaticallyWhen selected, Eclipse changes between two different CDT modes: it either uses the customer's makefile for the build (referred to as a 'Standard Make project' in CDT 3.x) if one exists, or it generate makefiles for the user (called 'Managed build project' in CDT 3.x). By default, this option is automatically set.
Expand Env. Variable Refs in MakefilesDefines whether environment variables ( ${xxx} ) should be expanded in makefile. By default, this option is automatically set.
Build directoryDefines the location where the build operation takes place. This location will contain the generated artifacts from the build process. This option is disabled when the Generate Makefiles automatically option is enabled.
WorkspaceOpens the Folder Selection dialog where you can select a workspace location for the project. This is the directory that will contain the plug-ins and features to build, including any generated artifacts. This button is only visible when Generate makefiles automatically is set not selected.
File systemOpens the file system navigator where you can specify another file system to use. This button is only visible when Generate makefiles automatically is set not selected.
VariablesOpens the Select build variable dialog where you can select a variable to specify as an argument for the build directory, or create and configure simple build variables which you can reference in build configurations that support variables. This button is only visible when Generate makefiles automatically is set not selected.
- -

C/C++ Project Properties, C/C++ Build

- - - -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Behaviour preferences
Stop on first build errorStops building when Eclipse encounters an error. -

Note: If this option is not selected, it is helpful for building large projects because it tells make to continue making other independent rules even when one rule fails.

Use parallel buildWhen enabled, this option indicates the activation of the generation of parallel builds. - -

If you enable this option, you need to determine the number of parallel jobs to perform:

-
    -
  • Use optimal jobs number - Lets the system determine the optimal number of parallel jobs to perform.
  • -
  • Use parallel jobs - Lets you specify the maximum number of parallel jobs to perform.
  • -
-
Workbench build behaviorBy default, the following settings are what the builder uses when instructed to build, rebuild, clean, and so on. You can change these settings so that new projects can use different targets if these defaults are not appropriate.
Build on resource save (Auto build)When selected, builds your project whenever resources are saved. By default, this option is selected and builds occur automatically each time resources are modified. When this option is not selected, a build occurs only manually using a menu item. If you require more control over when builds occur (for example, when a build should wait until you finish a large assortment of changes), disable this option and manually invoke builds yourself.
make build target ( for Build on resource save (Auto build))To build your project when resources are saved and change the default make build target, enable the Build on resource save (Auto Build) option, and specify a new build target in the Make build target field.
VariablesOpens the Select build variable dialog where you can add variables to the build command. -

C/C++ Project Properties, C/C++ Build, Select build variable

-
Build (Incremental build)Defines what the builder calls when an incremental build is performed. When this option is enabled, an incremental build occurs meaning that only resources that have changed since the last build are considered. If this option is disabled, a full build occurs, meaning that all resources within the scope of the build are considered. -
make build target (for Build (Incremental build))To change the build default make build target, enable the Build (Incremental build) option, and specify a new build target in the Make build target field.
VariablesOpens the Select build variable dialog where you can add variables to the make build target command.
CleanDefines what the builder calls when a clean is performed. The make clean is defined in the makefile.
make build target (for Clean)To change the rebuild default make build target, enable the Clean option, and specify a new build target in the Make build target field.
VariablesOpens the Select build variable dialog where you can add variables to the make build target command.
- - -

Related reference
- -

-

- - -

Intel Copyright Statement

- - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_discovery.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_discovery.htm deleted file mode 100644 index e6e19d67e6d..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_discovery.htm +++ /dev/null @@ -1,152 +0,0 @@ - - - - - - C/C++ Project Properties, Discovery Options - - - - -

Discovery Options properties

-

WarningNote that this functionality has been deprecated and not fully supported anymore

-

Use the Discovery Options properties panel to control how information required to build your project is discovered, enhance search and Content Assist functionality, and automatically enhance your makefile, such as include paths and symbol definitions.

-

Discovery options preference page

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Discovery Options preferences
GroupDescription
ConfigurationClick here for a description.
Manage Configurations...Click here for a description.
Discovery Profiles ScopeSpecifies the type of profile to set for discovery: -
    -
  • Per Language - Enables the association of different profiles with different resource types (different tools and input types), to have different settings discovered, e.g. for C and C++ source files and for different tools used by the project. -In addition, selecting this option lets you have different profile settings for different folders; however, only project profile types are allowed. - -
  • Configuration-wide - The Eclipse CDT uses only one profile for discovering scanner information for -the entire project (configuration). This means that both the project and per-file discovery profiles are allowed. - -
- -
Tools (language specific list)Shows a list of language specific compilers. Select a language from the list.
Automated discovery of paths and symbols
Automate discovery of paths and symbolsScans the build output to populate the path and symbol tables, such as symbol definitions, system include directories, local include directories, macros, and include files.
Report path detection problemsSets the notification of diagnostic errors for include paths that the Eclipse CDT is unable to resolve as it parses the build output.
Discovery profileIndicates the discovery profile to use for paths and symbol detection. The type of Configuration and Discovery Profile Scope you specify determine what which Discovery Profile options display on this tab.
Discovery profile options
Enable build output scanner info discoveryConfigures the scanner to parse the output from a build for compiler commands with options that specify the definition of preprocessor symbols, and include search paths (for GCC compiler, -D and -I respectively). This button is only visible when Configuration is set to Release and the Discovery Profiles Scope is set to Configuration-wide.
Load build output from fileSpecifies the name of the file you selected to load the build output from.
LoadLets you load a file to discover paths and symbols based on a previous builds' output. To activate the discovery select a build log file and then the Load button. This button is only visible when Configuration is set to Release and the Discovery Profiles Scope is set to Configuration-wide. -

Note: Click Variables to open the Select Variables window to define a build output file.

-
Browse...Click to locate a previously built output file to load the build output from. This button is only visible when Configuration is set to Release and the Discovery Profiles Scope is set to Configuration-wide.
Variables...Click to specify an argument for, or create and configure simple launch variables which you can reference in launch configurations that support variables. This button is only visible when Configuration is set to Release and the Discovery Profiles Scope is set to Configuration-wide.
Enable generate scanner info commandEnables the retrieval of information from the scanner. If it is not selected, the includes will be populated with default gcc system includes; Eclipse gathers the compiler settings based on the specified toolchain. This means that the Eclipse CDT can obtain the default gcc system includes to associate with the project. -

When selected, you can specify any required compiler specific commands in the Compiler invocation command field.

-
Compiler invocation commandIndicates the compiler specific command used to invoke the compiler (such as gcc, or more complicated commands used to perform all necessary steps for compiling C/C++ source files into .o files, and linking the object files and libraries into an executable program. For example, the command gcc -E -P -v hello.c | hello.cpp reads a compiler's configuration file and prints out information that includes the compiler's internally defined preprocessor symbols and include search paths. The information is complementary to the scanner configuration discovered when the output is parsed (if you've enabled the Enable build output scanner info discovery option), and is added to the project's scanner configuration. You can click Browse to locate this command, if required. - -

Note: The parsing of build output for scanner information is compiler specific. For example, the GNU toolchain compilers (gcc and g++) use -I for include paths, and -D for symbol definitions. Consult your compiler specific documentation for more information about scanner information commands, such as the following gcc commands:

-
    -
  • -D name
  • -
  • -I
  • -
  • -U name
  • -
  • -I-
  • -
  • -nostdinc
  • -
  • -nostdinc++
  • -
  • -include file
  • -
  • -imacros file
  • -
  • -idirafter dir
  • -
  • -isystem dir
  • -
  • -iprefix prefix
  • -
  • -iwithprefix dir
  • -
  • -iwithprefixbefore dir
  • -
-
Browse...Click to browse for a file to include in the compiler invocation command. This button is only visible when Configuration is set to Release and the Discovery Profiles Scope is set to Configuration-wide.
Compiler invocation argumentsEnter additional arguments to send to the chosen compiler.
- -

Related reference
- -

- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_environment.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_environment.htm deleted file mode 100644 index f373ae70a7a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_environment.htm +++ /dev/null @@ -1,119 +0,0 @@ - - - - - - C/C++ Project Properties, Environment - - - - -

C/C++ Project Properties, Environment

-Use the Environment property page to customize the build environment for all projects in the workspace; it lets you control the environment variables used by the build. -

C/C++ Project Properties, Environment

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Environment preference options
GroupDescription
ConfigurationClick here for a description.
Manage Configurations...Click here for a description.
Environment variables to setShows the current list of environment variables and their corresponding value. These are the environment variable values used when building.
VariableSpecifies the name of the environment variable.
ValueSpecifies the value of the environment variable.
Append variables to native environmentAppends the variables to the native environment during its execution.
Replace native environment with specified one Replaces the native environment with the specified variables, and then restores the native environment upon its completion.
Add...Opens the New variable dialog to create a new environment variable and value. Custom environment variables that you create appear in bold within the list. -

C/C++ Project Properties, Environment, New environment variable

-

Click Variables to Select variables by name to include in the value. Select Add to all configurations to make this new environment variable available to all configurations for the selected project; otherwise, the variable is only available for the currently selected configuration.

-
Select...Opens the Select variables dialog where you can choose from a list of system variables. -

C/C++ Project Properties, Environment, New environment variable

Edit...Modifies the name and value of the selected environment variable.
RemoveRemoves the selected environment variables from the list.
UndefineUndefines the currently selected variable; however, some variables, such as the PATH variable, cannot be undefined. -
- -

Related reference
- - -

- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_artifact.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_artifact.htm deleted file mode 100644 index d64a42690a6..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_artifact.htm +++ /dev/null @@ -1,91 +0,0 @@ - - - - - - C/C++ Properties, Build, Settings, Build Artifact tab - - - - -

C/C++ Properties, Build, Settings, Build Artifact tab

-

Use the Build Artifacts properties tab to specify build artifact information, such as the type and name, that gets built by the selected build configuration.

-

C/C++ Properties, Build, Settings, Build Artifact tab

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Build artifact options
GroupDescription
ConfigurationClick here for a description.
Manage Configurations...Click here for a description.
Artifact TypeShow the type for the selected artifact. Select an artifact type that is built by the currently selected build configuration (such as an Executable, Static library, and Shared library).
Artifact nameIndicates the name of artifact. By default, the name is the same as project name.
Artifact extensionSpecifies the file extension for the specified artifact type.
Output prefixIndicates a prefix that you want to prepend to the output results.
-
-

Available for: CDT projects.

- -

Related reference
- - -

- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_binparser.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_binparser.htm deleted file mode 100644 index cc8cfb3bf2b..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_binparser.htm +++ /dev/null @@ -1,101 +0,0 @@ - - - - - - C/C++ Project Properties, Build, Settings, Binary Parser - - - -

C/C++ Project Properties, Build, Settings, Binary Parser

-

Use the Binary Parsers properties tab to -ensure the accuracy of the Project Explorer and C/C++ Projects views, and to successfully run -and debug your programs. After you select the correct parser for your -development environment and build your project, you can view the -symbols of the object file using the C/C++ Projects view.

- -

C/C++ Project Properties, Build, Settings, Binary Parser

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Binary parser options
GroupDescription
ConfigurationClick here for a description.
Manage Configurations...Click here for a description.
Binary Parser (top pane)Lists all of the binary parsers currently known to CDT. Select the parsers that you want to use, and select the corresponding line to edit parser's options, if required.
Binary Parser OptionShows the parameters for the currently selected parser in the list above. Depending on the parser you select, the options in the list will be different (in particular, some may have no options at all).
Move UpMoves the selected parser higher in list. Note: The order matters for selected parsers only: they are applied to binaries in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.
Move DownMove the selected parser lower in list. Note: The order matters for selected parsers only: they are applied to binaries in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.
-
-

Available for: CDT projects.

- -

Related tasks -
-Selecting a binary parser

- - -

Related reference
- - -

- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_errparser.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_errparser.htm deleted file mode 100644 index 566c8c54473..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_errparser.htm +++ /dev/null @@ -1,132 +0,0 @@ - - - - - - C/C++ Project Properties, Build, Settings, Error Parsers - - - -

C/C++ Project Properties, Build, Settings, Error Parsers

-

Use the Error Parsers properties tab to customize the list of parsers that detect error messages in the -build output log.

-

C/C++ Project Properties,  Build, Settings, Error Parsers

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Error Parser options
GroupDescription
ConfigurationClick here for a description.
Manage Configurations...Click here for a description.
Error ParsersLists all of the error parsers currently known to CDT. Select the parsers that you want to use, and select the corresponding line to edit parser's options, if required.
Add...Add an error parsers to the list.
Edit...Edit the current error parser in the list.
DeleteDelete the selected error parser in the list.
Move UpMoves the selected parser higher in list. Note: The order matters for selected parsers only: they are applied to error logs in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.
Move DownMove the selected parser lower in list. Note: The order matters for selected parsers only: they are applied to error logs in the same sequence as defined by the user. The order is not preserved for unchecked parsers, so you do not have to move them.
-
-

Available for: CDT projects.

- -

Related tasks -
Tuning Error Parsers -
Tracking down compilation errors -

- -

Related reference
- - -

-

-
-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_steps.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_steps.htm deleted file mode 100644 index 39c3a44e902..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_steps.htm +++ /dev/null @@ -1,143 +0,0 @@ - - - - - - C/C++ Properties, Build, Settings, Build Steps tab - - - -

C/C++ Properties, Build, Settings, Build Steps tab

-

Use the Build Steps properties tab to customize the selected build configuration allowing for the specification -of user defined build command steps, as well displaying a descriptive message -in the build output, immediately before and after, normal build -processing executes.

-

C/C++ Properties, Build, Settings, Build Steps tab

-

- -

Note: To ensure reasonable custom build step behavior, sensible input must -be provided when specifying custom build step information. Custom build steps -are not verified for correctness in any regard and are passed exactly -as entered into the build stream.
-
-In the descriptive text, below, the term "main build" is defined as the -sequence of commands to execute when a build is invoked, not -including pre-build or post-build steps.
-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Build step options
GroupDescription
ConfigurationClick here for a description.
Manage Configurations...Click here for a description.
Pre-build StepsIdentifies any steps that are to occur before the build takes place. -

Note: The pre-build step is not executed if the state of the main build is determined to be up to date; otherwise it is executed. An attempt to execute the main build will occur regardless of the success or failure of executing the pre-build step.

-
CommandSpecifies one or more commands to execute immediately before the execution of the build. Use semicolons to separate multiple commands.
DescriptionSpecifies optional descriptive text associated with the pre-build step that is displayed in the build output immediately before the execution of the pre-build step command (or commands).
Post-build stepsIdentifies any steps that are to occur after the build takes place. -

Note: The post-build step is not executed if the state of the main build is determined to be up to date. It will be executed only if the main-build has executed successfully.

-
CommandSpecifies one or more commands to execute immediately after the execution of the build. Use semicolons to separate multiple commands.
DescriptionSpecifies optional descriptive text associated with the post-build step that is displayed in the build output immediately after the execution of the post-build step command (or commands).
-
-

Available for: CDT projects.

- -

Related reference
- - -

-

-
-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_tool.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_tool.htm deleted file mode 100644 index 7d0a6d548a2..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_settings_tool.htm +++ /dev/null @@ -1,109 +0,0 @@ - - - - - - C/C++ Project Properties, Build, Settings, Tool settings tab - - - -

C/C++ Project Properties, Build, Settings, Tool settings tab

-Use the Tool Settings properties tab to customize the tools and tool options used in your build configuration. -

C/C++ Project Properties, Build, Settings, Tool Settings tab

-

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Tool settings options
GroupDescription
ConfigurationClick here for a description.
Manage Configurations...Click here for a description.
(Left pane)Displays a list of tools and their option categories. Select a desired tool from the list to modify its options.
(Right pane)Displays the options that you can modify for the selected tool. This list of options changes depending on which options category you select for a specific tool in the left pane.
-
-

Available for: CDT projects and source files

- -

Related reference
- - -

-

-
-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_toolchain.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_toolchain.htm deleted file mode 100644 index 73483b5c4aa..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_toolchain.htm +++ /dev/null @@ -1,105 +0,0 @@ - - - - - - C/C++ Project Properties, Tool Chain edit - - - -

Tool chain editor preferences (C/C++ Project Properties)

-
-

Customizes the toolchain used in your build configuration; it lets -you specify which tools the builder needs to include when it builds the project for a specified toolchain and configuration.

-

-Tool chain editor preferences

- - -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Tool chain editor properties
ConfigurationClick here for a description.
Manage configurationsClick here for a description.
Display compatible toolchains onlyWhen selected, it shows a list of toochains that are only compatible with the current configuration. When this option is not selected, it shows a list of all toolchains known to the Eclipse CDT. A Toolchain is compatible if it can run on given platform. .
Current toolchainIndicates the toolchain to use with the current configuration. A toolchain is a set of tools (such as a compiler, linker, and assembler) intended to build your project. Additional tools, such as a debugger, can be associated with a toolchain. There can be several toolchains available, depending on the compilers installed on your system.
Current builderIndicates the builder used to build the selected configuration. A builder refers to an external make utility, such as GNU make, that the Eclipse CDT uses (and relies on) to build a project. The CDT can generate makefiles automatically when you create a Make C or C++ project, or you have the option of creating a C or C++ Make project where you provide the makefile yourself.
Used toolsShows a list of tools currently included for the selected toolchain. You can click Select Tools to modify this list.
Select ToolsOpens the Select Tools dialog that lets you add or remove tools from the list of tools for the selected toolchain.
-
-

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_variables.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_variables.htm deleted file mode 100644 index 5fcd7f794bc..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_build_variables.htm +++ /dev/null @@ -1,122 +0,0 @@ - - - - - - Variables properties (C/C++ Project Properties) - - - -

Variables properties (C/C++ Project Properties)

-Customizes the Eclipse CDT build environment variables for all projects in the workspace; it lets -you control the environment variables used by the build to for the purposes of building the selected configuration.

-

C/C++ Project Properties, Variables

-

- -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Variables preferences
Environment variables to setShows the current list of environment variables and their corresponding value. These are the environment variable values used when running an application.
ConfigurationClick here for a description.
Manage configurationsClick here for a description.
(The variables table)Lists the CDT build variables and system variables, by Name, Type, and the Value. Custom Build variables are identified by the name being highlighted using a bold font.
NameIndicates the name of the variable, either a user defined variable or a system variable.
TypeShows the type for the variable.
ValueSpecifies the value of the variable.
Show system variablesWhen selected, system variables are included in the Variables table; otherwise, they are excluded so that only user defined variables appear in the Variables list.
AddCreates a new variable and corresponding value.
EditModifies the name and value of the selected variable.
DeleteRemoves the selected variables from the list. Note: Some variables are read-only and cannot be removed. -
- -

Related reference
- -

-

- -

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_builders.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_builders.htm deleted file mode 100644 index 55c061fb216..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_builders.htm +++ /dev/null @@ -1,119 +0,0 @@ - - - - - - C/C++ Project Properties, Builders - - - -

C/C++ Project Properties, Builders

-

You can select which Builders to enable for this project and in -which order they are used.

-

C/C++ Project Properties, Builders

-

- - -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Builder properties
Configure the builders for the projectSelects which builders to enable from the list. You can disable the CDT Builder and you can control when the CDT Builder runs with respect to the project builders that you define. -
New...Opens the Choose configuration type dialog so that you can add a new builder to the list.

-

C/C++ Project Properties, Builders, Choose configuration type

-

The Ant Builder option lets you configure and deploy projects; however, if you want to use some other tool or prefer to do it yourself, you can set up a Program external tool project builder. This type allows you to customize the deployment of your project as you require, while maintaining the convenience of automatically running your script every time your project is built.

-

The Program option lets you to define an external tool for any executable file that is accessible on your local or network file system. For example, if instead of Ant you prefer to use your own shell scripts or Windows .bat files to package and deploy your Eclipse projects, you can then create a Program external tool that would specify where and how to execute that script.

Import...Opens the Import launch configuration dialog so that you can import a builder to include it in the list.

-

Import launch configuration -

Edit...Opens the Configure Builder dialog that lets you specify when to run the selected builder.

-

Configure Builder -

-

When you configure a builder, you have the following options: -

    -
  • After a "Clean" - When enabled, the selected builder is scheduled to run after a clean operation occurs. -
  • During manual builds - When enabled, the selected build is initiated when you explicitly select a menu item or press its corresponding shortcut key combination. -
  • During auto builds - When enabled, automatic builds are performed as resources are saved (they are incremental and operate over an entire workspace). Note: running your project builder during auto builds is possible, although it is not recommended because of performance concerns. -
  • During a "Clean" - When enabled, the selected builder is scheduled to run during a clean operation. -
-

RemoveRemoves the selected builder from the list.
UpMoves the currently selected builder higher in the list to change the builder order.
DownMoves the currently selected builder lower in the list to change the builder order.
- -
-

Available for: Any projects, folders and files regardless of project kind.

- -

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_cfg_dialog.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_cfg_dialog.htm deleted file mode 100644 index 499dce7cba9..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_cfg_dialog.htm +++ /dev/null @@ -1,58 +0,0 @@ - - - - - - C/C++ Project Properties, Configurations management. - - - -

C/C++ Project Properties, Configurations management.

-All CDT-specific property pages have unified controls -to handle configurations. - -

C/C++ Project Properties, Configurations management.

-

-
-
Configuration:
-
Specifies the selected build configuration from the list provided. -Note that configuration selection, unlike CDT 3.x, affects only property pages contents. -Selected configuration would not be made Active configuration (used to build project). -
-
Manage configurations
-
Adds, removes, renames configurations. Sets active configuration.
-
-

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general.htm deleted file mode 100644 index f7e829f092f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general.htm +++ /dev/null @@ -1,61 +0,0 @@ - - - - - - C/C++ Project Properties, C/C++ General - - - -

C/C++ Project Properties, C/C++ General

-

General project properties

-

C/C++ Project Properties, C/C++ General

-

-
-
Documentation tool comments
-
Specifies which documentation tool should be used to determine editor presentation and behaviors. This - enables editor features such as content-assist, documentation comment generation and syntax highlighting. The particular - tool selected here will be used for the files under this project and overrides the workspace level preference. - Note this preference is only available for the project level.
-

Available for :
-
Any projects, folders and files regardless of project kind
-
-

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_doc.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_doc.htm deleted file mode 100644 index 977c50b8fc4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_doc.htm +++ /dev/null @@ -1,57 +0,0 @@ - - - - - - C/C++ Project Properties, C/C++ Documentation - - - -

C/C++ Project Properties, C/C++ Documentation

-

You can select which installed documentation to use for your project.

-

C/C++ Project Properties, C/C++ Documentation

-

-
-
Help Books
-
Sets the help books to use for this project.
-
Check all
-
Makes all books selected.
-
Uncheck all
-
Makes all books unselected.
-

Available for :
-
CDT projects
-
-

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_exp.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_exp.htm deleted file mode 100644 index 3502686d883..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_exp.htm +++ /dev/null @@ -1,78 +0,0 @@ - - - - - - - C/C++ Project Properties, General, Export page - - - - -

C/C++ Project Properties, General, Export page

-

You can modify the list of exported elements -(include paths, symbols, libraries, library paths) -

- -

-

-

-There are 4 tabs on this page: Include paths, Symbols, Libraries, Library paths. -
-They have the similar design and display corresponding -elements exported by current project to outside. -
-There are 2 ways to make value exported: -

    -
  • Use 'Add' button on Export page -
  • Use 'Export' button on Path and Symbols page. -
- -
-
Add
-
Add new element
-
Edit
-
Modify selected element
-
Delete
-
Remove selected element
-

Available for :
-
CDT projects. May be enabled/diabled in Preferences.
-

- -

Related reference
- - -

-

-

Intel Copyright Statement

- - - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_idx.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_idx.htm deleted file mode 100644 index 4f2f85b88d5..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_idx.htm +++ /dev/null @@ -1,64 +0,0 @@ - - - - - - C/C++ Project Properties, Indexer - - - -

C/C++ Project Properties, C/C++ Indexer

-

You can select which C/C++ Indexer to use for your project. The -indexer is necessary for search and related features, like content -assist.

-

C/C++ Project Properties, C/C++ Indexer

-

-
-
Enable project specific settings
-
Check this box if you need specific index settings for this project. Else common settings (defined in Preferences) will be applied. In this case, all controls below are disabled.
-
Select indexer
-
Specifies the Indexer to use for this project; No Indexer -disables indexing. Every indexer may have its own set of options. -
-
Build configuration for the indexer
-
Index source either from specified configuration, or from active one. - Since indexing takes a lot of time, using active configuration is not recommended, - because re-index will be fired after each active configuration change. -
-

Available for :
-
C/C++ projects
-
-

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_lng.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_lng.htm deleted file mode 100644 index bd7d79be4be..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_lng.htm +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - C/C++ Project Properties, Language mapping - - - -

C/C++ Project Properties, Language mappings

-

Customize the use of C/C++ language associations in the Language Mappings preference panel for a project.

-

C/C++ Project Properties, Language mapping

-

-
-
Project-specific settings (upper pane)
-
Language mappings specific for current project.
-
Add
-
Add project-specific language mapping
-
Remove
-
Delete project-specific language mapping
-
Workspace-specific settings (lower pane)
-
Language mappings specific for whole workspace.
-

Available for :
-
C/C++ projects
-
-

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_hier.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_hier.htm deleted file mode 100644 index 739795acd1b..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_hier.htm +++ /dev/null @@ -1,90 +0,0 @@ - - - - - - - C/C++ Properties, Include Paths and Symbols, Data hierarchy - - - - -

C/C++ Properties, Include Paths and Symbols, Data hierarchy tab

-

Use the Data Hierarchy tab in the Paths and Symbols properties panel to inspect all data related to Project/Configuration description.

-

This tab is optional, it can be enabled/disabled in Preferences.

- -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Paths and Symbols, Data hierarchy tab
OptionDescription
Object to viewSelect either Project description, Configuration description (or Resource description, for Folder or File) to inspect.
Expand allExpands the whole data structure.
Expand level...Expands data structure up to required level. Collapses inner levels.
Collapse allCollapses whole data structure
- -
-

Available for :
-
CDT projects, folders and files
-
- -

Related reference
- -

-

-
-

Intel Copyright Statement

- - - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_inc.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_inc.htm deleted file mode 100644 index 4e037ac29d5..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_inc.htm +++ /dev/null @@ -1,106 +0,0 @@ - - - - - - - C/C++ Project Properties, Paths and Symbols, Includes - - - - -

C/C++ Project Properties, Paths and Symbols, Includes

-

You can modify the list of included paths and change the order in which they are referenced.

- -

-

- -
-
Languages (left pane)
-
Displays languages related to this project. - Select one to see corresponding include paths. -
-
Include paths (right pane)
-
List of include paths related to given language.
-
Add
-
Add new include path
-
Edit
-
Modify selected include path
-
Delete
-
Remove selected include path
-
Export / Unexport
-
Toggle selected path exported or not
-
Move Up
-
Move the currently selected element up in the list.
-
Move Down
-
Move the currently selected element down in the list.
-
Show built-in values
-
Check to display system (built-in) includes.
-

Available for :
-
CDT projects, folders and files
-

- -

Related reference
- - - -

-

-

Intel Copyright Statement

- - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_lib.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_lib.htm deleted file mode 100644 index dbfc5d5705b..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_lib.htm +++ /dev/null @@ -1,103 +0,0 @@ - - - - - - - C/C++ Project Properties, Paths and Symbols, Libraries - - - - -

C/C++ Project Properties, Paths and Symbols, Libraries

-

You can modify the list of libraries and change the order in which they are referenced.

- -

-

- -
-
Libraries (main pane)
-
List of libraries for given build configuration.
-
Add
-
Add new library
-
Edit
-
Modify selected library
-
Delete
-
Remove selected library
-
Export / Unexport
-
Toggle selected library exported or not
-
Move Up
-
Move the currently selected element up in the list.
-
Move Down
-
Move the currently selected element down in the list.
-
Show built-in values
-
Check to display system (built-in) libraries.
-

Available for :
-
CDT projects, folders and files. - Note that current toolchain may not support this feature.
-

- -

Related reference
- - -

-

-

Intel Copyright Statement

- - - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_libpath.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_libpath.htm deleted file mode 100644 index cb8e601caad..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_libpath.htm +++ /dev/null @@ -1,103 +0,0 @@ - - - - - - - C/C++ Project Properties, Paths and Symbols, Library paths - - - - -

C/C++ Project Properties, Paths and Symbols, Library paths

-

You can modify the list of library paths and change the order in which they are referenced.

- -

-

- -
-
Library paths (main pane)
-
List of library paths for given build configuration.
-
Add
-
Add new library path
-
Edit
-
Modify selected library path
-
Delete
-
Remove selected library path
-
Export / Unexport
-
Toggle selected library path exported or not
-
Move Up
-
Move the currently selected element up in the list.
-
Move Down
-
Move the currently selected element down in the list.
-
Show built-in values
-
Check to display system (built-in) library paths.
-

Available for :
-
CDT projects, folders and files. - Note that current toolchain may not support this feature.
-

- -

Related reference
- - - -

-

-

Intel Copyright Statement

- - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_out.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_out.htm deleted file mode 100644 index c4a24c3fba9..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_out.htm +++ /dev/null @@ -1,93 +0,0 @@ - - - - - - - C/C++ Project Properties, Paths and Symbols, Output location - - - - -

C/C++ Project Properties, Paths and Symbols, Output location

- -

You can modify a list of project output entries effective in given configuration.

- -

-

- -
-
Add Folder
-
Make existing folder a source folder.
-
Create/Link Folder
-
Create output folder or link directory outside the project as an output folder
-
Edit filter data
-
Edit filter for selected output folder.
-
Delete folder
-
Remove an output folder.
-

Available for :
-
CDT projects
-

- -

Related reference
- - -

-

-

Intel Copyright Statement

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_ref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_ref.htm deleted file mode 100644 index f41bff2605a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_ref.htm +++ /dev/null @@ -1,125 +0,0 @@ - - - - - - C/C++ Project, Paths and Symbols, Project References - - - -

C/C++ Project Properties, Paths and Symbols, Project References

-

-Project references are a powerful way of expressing dependencies between -Build configurations in different projects. Specifically they perform 2 roles: -

    -
  • Automatic propagation of Exported Settings from one project -to another which depends on it
  • -
  • Build, if necessary, referenced projects before dependent project
  • -
-

-Unlike the Eclipse Common References page, -this page allows setting references to specific configurations. - -

Since CDT 7 this functionality has been improved: -

    -
  • - Referenced projects are ordered

    and this order can be changed using the buttons provided. -Referenced projects are built in the order listed in the dialog, and the order is used in the build for setting -up the Include paths and Library link lines. -

  • -
  • - Can reference another configuration in the same project

    It's allowed to reference another configuration - in the same project. -

  • -
  • - Referenced projects which don't exist in the workspace are shown in gray. -
  • -
- -

C/C++ Project, Paths and Symbols, Project References

-

-
-
Projects list (main pane)
-
Displays all other CDT projects which current project can refer to. - All configurations are displayed for each project. A check mark indicates the configuration is referenced. - Note that only one configuration can be checked in any given project. -
[Active] configuration presents - in each configs list and represents current active configuration. -
Configurations can reference another configuration in the same project. -
Referenced projects, which don't exist in the workspace, are shown in gray.
-
Expand all
-
Expands all configuration lists
-
Collapse all
-
Collapses all configuration lists
-
Move up
-
Move the project up in the references list
-
Move down
-
Move the project down in the references list
-

Available for :
-
CDT projects
-
- -

Related concepts
- Configuring Project References
- -

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_src.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_src.htm deleted file mode 100644 index e4f160c757c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_src.htm +++ /dev/null @@ -1,93 +0,0 @@ - - - - - - - C/C++ Project Properties, Paths and Symbols, Source location - - - - -

C/C++ Project Properties, Paths and Symbols, Source location

- -

You can modify a list of project source entries effective in given configuration.

- -

-

- -
-
Add Folder
-
Make existing folder a source folder.
-
Create/Link Folder
-
Create source folder or link directory outside the project as a source folder
-
Edit filter data
-
Edit filter for selected source folder.
-
Delete folder
-
Remove a source folder.
-

Available for :
-
Any projects, folders and files regardless of project kind
-

- -

Related reference
- -

-

-

Intel Copyright Statement

- - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_sym.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_sym.htm deleted file mode 100644 index 0d602479909..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_pns_sym.htm +++ /dev/null @@ -1,100 +0,0 @@ - - - - - - - C/C++ Project Properties, Paths and Symbols, Symbols - - - - -

C/C++ Project Properties, Paths and Symbols, Symbols

-

You can modify the list of preprocessor symbols.

- -

- - -
-
Languages (left pane)
-
Displays languages related to this project. - Select one to see corresponding symbols. -
-
Symbol / Value
-
List of symbols related to given language.
-
Add
-
Add new symbol
-
Edit
-
Modify selected symbol value/dd> -
Delete
-
Remove selected symbol
-
Export / Unexport
-
Toggle selected symbol exported or not
-
Show built-in values
-
Check to display system (built-in) includes.
-

Available for :
-
CDT projects, folders and files
-

- -

Related reference
- - -

-

-

Intel Copyright Statement

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_scanner_discovery.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_scanner_discovery.htm deleted file mode 100644 index 9522ff45851..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_scanner_discovery.htm +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - - -C/C++ Project properties: Preprocessor Include Paths, Macros, etc. - - - - - - -

C/C++ Project properties: Preprocessor Include Paths, Macros, etc.

- -

-Include paths and preprocessor macros for C/C++ indexer and other Language Settings are supplied by Language Settings Providers using Scanner Discovery mechanism. -

-

-The entries can be inspected and set up on project properties page "Preprocessor Include Paths, Macros, etc." - Entries tab. -

- -

-Language Settings Providers can be set up and configured for the selected configuration on project properties page "Preprocessor Include Paths, Macros, etc." - Providers tab. -

- - -

Related concepts
-C/C++ Indexer
-Scanner Discovery
-

- -

Related tasks
-Setting up include paths and macros for C/C++ indexer
-

- -

Related reference
-C/C++ Project properties: Preprocessor Include Paths, Macros, etc. - Entries tab
-C/C++ Project properties: Preprocessor Include Paths, Macros, etc. - Providers tab
-

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_sd_entries.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_sd_entries.htm deleted file mode 100644 index 8aee323131b..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_sd_entries.htm +++ /dev/null @@ -1,199 +0,0 @@ - - - - - - - -C/C++ Project properties: Preprocessor Include Paths, Macros, etc. - Entries tab - - - - - - -

C/C++ Project properties: Preprocessor Include Paths, Macros, etc. - Entries tab

- -

-Include paths and preprocessor macros for C/C++ indexer can be inspected and set up on the project property page "Preprocessor Include Paths, Macros, etc.", "Entries" tab. -This tab presents Language Settings Providers employed by Scanner Discovery to provide include paths, -macros and other Language Settings. -

-

-Note that the entries could be set also on an individual resource, such as file or folder. Open file or folder properties to inspect resource-specific entries. -The entries on a folder or a project will apply to all subfolders and C/C++ files under it - unless overriden on a lower level. -

- -

-"Entries" tab shows a list of Language Settings Providers for each language. A provider node can be expanded to show include paths and macros defined by the provider. -A user can add custom entries here under "User Setting Entries" provider. -

-

Scanner Discovery Properties Entry Panel

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Entries tab controls
GroupDescription
ConfigurationA set of properties for the project. Not required for debugging.
Manage Configurations...A dialog to create or manage configurations. Not required for debugging.
LanguagesLists all of the languages defined by the toolchain. Select a language to see the list of applicable providers.
Setting EntriesLists all of the providers for the selected language and entries supplied by them. Expand a provider node to see the entries.
Show built-in valuesDisable checkbox "Show built-in values" to filter out built-in setting entries in the view. - Built-in compiler entries need to be provided to C/C++ indexer but not to the compiler during the build. -
Add...Add an entry to the provider. Enabled only when the provider supports the operation.
Edit...Edit the selected settings entry. Enabled only when the provider supports the operation.
DeleteDelete the selected settings entry. Enabled only when the provider supports the operation.
Move UpMoves the selected entry higher in the list. Enabled only when the provider supports the operation
Move DownMoves the selected entry lower in the list. Enabled only when the provider supports the operation
-
- -

Adding and Editing entries

-

Use Add... and Edit... buttons to add or modify the entries. Both buttons open similar dialog described here.

-

Scanner Discovery Add Include Dialog

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Add/Edit entries dialog
GroupDescription
Kind of Setting EntryA dropbox to select desired kind of setting entry. - Scanner Discovery Kinds Dropdown
-						Following kinds are available:
-						- Include Directory
-						- Preprocessor Macro
-						- Include File
-						- Preprocessor Macros File
-						- Library Path
-						- Library -
This dropbox is not available in "Edit" mode. -
Kind of pathA dropbox to select desired kind of path. - Scanner Discovery Path Dropdown
-						Following kinds of paths are available:
-						- Project Path
-						- Workspace Path
-						- File System Path -
This dropbox is shown for path entries only. -
PathEnter path value of the entry. -
This field is shown for path entries only. -
Open folder buttonUse folder button to navigate folder structure to select existing path. - The provided dialog varies depending on the kind of path selected in the corresponding dropbox. -
This button is shown for path entries only. -
VariablesSelect one of the build or environment variables provided by CDT to embed into "Path" field. -
This button is enabled only for File System Paths. -
Treat as built-inEnable this checkbox to mark the entry as built-in. - Built-in compiler entries need to be provided to C/C++ indexer but not to the compiler during the build. -
Contains system headersEnable if the include path is a system directory which contains system headers. -
This checkbox is shown for Include Directories only. -
Framework folderMac OS has a unique way of specifying include directories for Frameworks. - Enable if the included directory is Mac Framework directory. -
This checkbox is shown for Include Directories only. -
NameShown for Preprocessor Macro only. Specify the macro name here.
ValueShown for Preprocessor Macro only. Specify the macro value here.
-
- - -

Related concepts
-Scanner Discovery
-C/C++ Indexer
-

- -

Related tasks
-Setting up include paths and macros for C/C++ indexer
-

- -

Related reference
-C/C++ Project properties: Preprocessor Include Paths, Macros, etc. - Providers tab
-

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_sd_providers.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_sd_providers.htm deleted file mode 100644 index 81669a9f9b5..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_sd_providers.htm +++ /dev/null @@ -1,136 +0,0 @@ - - - - - - - -C/C++ Project properties: Preprocessor Include Paths, Macros, etc. - Providers tab - - - - - - -

C/C++ Project properties: Preprocessor Include Paths, Macros, etc. - Providers tab

- -

-Include paths and preprocessor macros for C/C++ indexer and other Language Settings are supplied by Language Settings Providers as part of Scanner Discovery. -Language Settings Providers can be set up and configured for the selected configuration in the "Providers" tab. -

-

-"Providers" tab is only shown in properties of a project, not in properties of a file or a folder. -

-

Scanner Discovery Properties Providers Panel

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Providers tab controls
GroupDescription
ConfigurationA set of properties for the project. Not required for debugging.
Manage Configurations...A dialog to create or manage configurations. Not required for debugging.
Language Setting Providers listLists all of the providers available for the current configuration. Select the providers to assign to the configuration.
Clear EntriesClears all entries of the selected provider. - This operation takes effect after pressing "Apply" or "OK". - Normally this will trigger a rerun if the provider supplies built-in compiler settings. - Build output parsers will regain language settings after build while parsing new build output. -
This operation might be unavailable if the provider does not have any language settings. - Some providers may not have the capability to clear. -
On this property page, this operation is applicable only to non-shared providers. -
ResetResets options of the selected provider to default values. - This operation also clears the provider entries. - The button can be enabled if some options in "Language Settings Provider Options" panel were changed. -
In this dialog, this operation is applicable only to non-shared providers. -
Move UpMoves the selected provider higher in the list.
Move DownMoves the selected provider lower in the list.
-
- - - -

-A user can define some options for configuration providers (or "non-shared") on this property page. Note that providers can be either shared or defined per configuration. -Options of global (or "shared") providers can be configured on C/C++ Preferences: Scanner Discovery. -

- -

-There are 2 specific options that are added for non-shared providers defined per configuration. They are described in the table below. -

- - - - - - - - - - - - - - - - - - - - - -
Discovery tab
GroupDescription
Use global provider shared between projectsProviders can be global or belong to a configuration. Global providers share their entries between all configurations which refer to them. -
Store entries in project settings folderProviders can persist their entries in workspace or under project folder. - Storing entries under project when approprate can make sharing with the other team members easier. -
- -

-The rest of the options is described in C/C++ Preferences: Scanner Discovery, under Language Settings Providers Options. -

- - -

Related concepts
-Scanner Discovery
-C/C++ Indexer
-

- -

Related tasks
-Setting up include paths and macros for C/C++ indexer
-

- -

Related reference
-C/C++ Project properties: Preprocessor Include Paths, Macros, etc. - Entries tab
-

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_typ.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_typ.htm deleted file mode 100644 index 6c1c30e209d..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_general_typ.htm +++ /dev/null @@ -1,61 +0,0 @@ - - - - - - C/C++ Project Properties, File Types - - - -

C/C++ Project Properties, File Types

-

You can view a list of file types on the File Types page of a C/C++ -project's properties window.

-

C/C++ Project Properties, File Types

-

-
-
Use workspace settings
-
Enables the use of the Managed workspace settings.
-
Use Project Settings
-
Enables the use of project settings, or the addition or removal -of specific file types.
-
New...
-
Adds a new file type.
-
Remove
-
Removes a listed file type.
-

Available for :
-
C/C++ projects
-
-

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_manage_dialog.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_manage_dialog.htm deleted file mode 100644 index f3c7deee9ca..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_manage_dialog.htm +++ /dev/null @@ -1,59 +0,0 @@ - - - - - - - C/C++ Project Properties, Manage Configuration Dialog - - - - -

C/C++ Project Properties, Manage Configuration Dialog

-

-Manages the configurations defined for the project. Select a button to add, -rename, remove configuration or set it active. -

-

- -

-
Main pane
-
Displays the list of defined configurations for the given project.
-
Set active
-
Sets selected configuration active.
-
New
-
Displays the new configuration dialog that can be used to create a new configuration.
-
Remove
-
Removes the selected configuration from the list, prompts the user to confirm the action.
-
Rename
-
Displays the rename configuration dialog that can be used to rename the configuration name & description.
-
OK
-
Closes the manage configuration dialog
-

- -

Related reference
- - -

- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_manage_newdialog.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_manage_newdialog.htm deleted file mode 100644 index 47da7449567..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_manage_newdialog.htm +++ /dev/null @@ -1,55 +0,0 @@ - - - - - - - C/C++ Project Properties, New Configuration Dialog - - - - -

C/C++ Project Properties, New Configuration Dialog

-

-Creates a new configuration based on either -an existing configuration or a default configuration. -

-

- -

-
Name:
-
Name of the new configuration.
-
Description:
-
Description of the new configuration.
-
Existing configuration:
-
A list of existing configurations of the current project, to be derived from.
-
Default configuration:
-
A list of default configurations available for the current project, to be derived from.
-

- -

Related reference
- -

- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_manage_rendialog.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_manage_rendialog.htm deleted file mode 100644 index 024fdf1b50d..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_manage_rendialog.htm +++ /dev/null @@ -1,49 +0,0 @@ - - - - - - - C/C++ Project Properties, Rename Configuration Dialog - - - - -

C/C++ Project Properties, Rename Configuration Dialog

-

-Renames the name and the description of -the existing configuration. -

-

-

- -

-
Name:
Name of the configuration.
-
Description:
Description of the configuration.
-

- -

Related reference
- -

- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_ref.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_ref.htm deleted file mode 100644 index 1d5eb510377..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_ref.htm +++ /dev/null @@ -1,51 +0,0 @@ - - - - - - C/C++ Project, Managed, Project References - - - -

C/C++ Project Properties, Project References

-

C/C++ Project, Project References

-

-
-
Project references for <project>:
-
Specifies the projects required to build this project.
-

Available for :
-
Any projects (not CDT-specific)
-
-

Related reference
- -

- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_refactoring_history.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_refactoring_history.htm deleted file mode 100644 index 7d6f30c7383..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_refactoring_history.htm +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - C/C++ Project, Managed, Refactoring History - - - -

C/C++ Project Properties, Refactoring History

-

Lets you explore the entire refactoring history for the currently selected project.

-

C/C++ Project, Managed, Refactoring History

-

-
-
Refactoring history for <project>:
-
The refactoring history dialog displays the entire refactoring history of your workspace. Drill down to an individual refactoring and select it to see more details about the performed refactoring in the details view below. -This dialog may also be used to remove certain refactorings from the refactoring history. Select an entire year, month, week or day and press Remove to remove the selected refactorings from the refactoring history. -In order to be able to better select refactorings from the refactoring history, there are two ways to group your refactorings: - -Group by Project: Refactorings are grouped by project. Every refactoring is associated with the project that contains the element which served as input to the recorded refactoring. -Note: There are certain instances of refactorings which cannot be uniquely associated with a project. These refactorings are associated with the entire workspace. -Group by Date: Refactorings are grouped by date. The refactoring history dialog presents the refactorings as a history, last recently executed refactorings first. -
-

Available for :
-
Any projects, folders and files regardless of project kind
-
-

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_resource.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_resource.htm deleted file mode 100644 index 4ed20aaf4b2..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_resource.htm +++ /dev/null @@ -1,97 +0,0 @@ - - - - - - C/C++ Project Properties, Resource - - - -

C/C++ Project Properties, Resource

-

Shows resource information for the selected type.

-
-

C/C++ Project Properties, Resource

-

- -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Resource properties
PathSpecifies the location of the selected resource type within the workspace. For example, similar to folders, projects map to directories in the file system.
TypeIndicates the type for the selected resource: Folder, Project, or File.
LocationSpecifics the location of the selected resource within the file system.
Last modifiedShows the date that the selected resource was last modified.
Text file encodingSets an alternate text encoding. Because text files are encoded differently (depending on the locale and platform), use the default text file encoding for the locale of your host operating system. However, if you want to work with text files that originate from another source (for example, to work with text files that use a different encoding scheme than your native one, so that you can easily exchange files with another team), choose Other and select an appropriate one from the list.
Inherited from containerWhen enabled, the selected resource inherits the text encoding specified for it's container resource.
OtherWhen enabled, the selected resource uses an alternate text encoding other than that specified for its container resource. You can enable this option if you want to work with text files that originate from another source (ones that use a different encoding scheme than your native one), so that you can easily exchange files with others.
New text file line delimiterSpecifies the end of line character(s) to use for new text files being created.
Inherited from containerWhen enabled, the selected resource inherits the character line ending for new text files specified for it's container resource.
OtherWhen enabled, the selected resource uses an alternate end of line character(s) for new text files other than that specified for its container resource. For example, you can set the Text file encoding option to UTF-8, and then set the line endings character for new files to Unix, so that text files are saved in a format that is not specific to the Windows operating system, and the files can easily be shared amongst various developer systems.
- -
-

Available for: Any projects, folders and files regardless of project kind.

- -

Related reference
- -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_rundebug.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_rundebug.htm deleted file mode 100644 index 4ab20b848f7..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_prop_rundebug.htm +++ /dev/null @@ -1,81 +0,0 @@ - - - - - - C/C++ Properties, Run and Debug settings - - - -

C/C++ Properties Run and Debug settings

- -Run/Debug settings are mostly applicable to Java projects, not to C/C++ projects. - -

C/C++ Properties, Run and Debug settings

-

-
-

Available for :
-
Any projects, folders and files regardless of project kind
-
-

Related reference
- - -

-

-

Intel Copyright Statement

- -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_properties.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_properties.htm deleted file mode 100644 index c21f476b4a3..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_properties.htm +++ /dev/null @@ -1,62 +0,0 @@ - - - - - - -C/C++ Properties - - - - - -

C/C++ Properties

-

This section describes C/C++ Properties.

-

Properties can be obtained for projects, folders and separate files. -To select object properties, right click on object in view and select Properties.

-

Selecting C/C++ Project Properties

- - -

Related concepts
-CDT projects

- - -

Related reference
- -

-

-

Intel Copyright Statement

- - -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_properties_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_properties_view.htm deleted file mode 100644 index 94cec5ee083..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_properties_view.htm +++ /dev/null @@ -1,62 +0,0 @@ - - - - - - - Properties view - - - - - -

Properties view

-

The Properties view displays property names and values for a selected item such as a resource.

-

Properties View

-

Toolbar buttons allow you to toggle to display properties by category or to filter advanced properties. Another toolbar button allows you to restore the selected property to its default value.

-

To see more detailed information about a resource than the Properties view gives you, right-click the resource name in the Project Explorer view and select Properties from the pop-up menu.

- - -

Properties view toolbar options

-

The table below lists the toolbar options displayed in the Properties view.

- -

- - - - - - - - - - - - - - - - - - - - - -
IconNameDescription
Pin IconPin Properties ViewForces the Properties view to remain on top of other views in the workbench area.
Menu IconView MenuClick the white upside-down triangle icon to open a menu of items specific to the Properties view.

-
-
New Properties View
-
Create a new pane within the Properties view. Panes can be selected using the names that appear on the left edge.

-
Pin to Selection
-
Pin the current selection to remain within the viewable area of the Properties view.

-

- -

Related references -
C/C++ Views

-
-

- IBM Copyright Statement
- Nokia Copyright Statement -

- - - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_registersview.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_registersview.htm deleted file mode 100644 index 569a880fc90..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_registersview.htm +++ /dev/null @@ -1,191 +0,0 @@ - - - - - - - - -Registers view - - - - - -

Registers view

- -

The Registers view of the Debug perspective lists information about the registers in a selected stack frame. -Values that have changed are highlighted in the Registers view when your program -stops.

-

Registers View

- -

Registers view toolbar options

-

The table below lists the icons displayed in the Registers view toolbar.

- - - - - - - - - - - - - - - - - - - - - - - - - - -
IconNameDescription
Show Type Names icon
Show Type Names
Displays the type, (such as int) beside each register value.
Show Logical Structure icon
Show Logical Structure
Changes if logical structures should be shown in the view or not.
Collapse All icon
Collapse All
Collapses all the the currently expanded registers.
Menu Layout icon
View Menu > LayoutProvides multiple layout options for the Registers view.
- -

Registers view context menu commands

-

The Registers view context menu commands include:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Icon
Name
Description
Add Register Group Open the Register Group dialog which allows you to define a register group that is shown in the Registers view.
Assign Value Assigns a value to the selected register.
Cast to Type icon
Cast To Type... Open the Cast To Type dialog.
Change Value icon
Change Value... Open the Set Value dialog to change the selected registers value.
Content Assist Opens a content assist dialog at the current cursor position.
CopyCopies the currently selected text or elements to the clipboard
Copy Registers icon
Copy Registers
Copies the register names and contents to the clipboard
Create Watch Expression icon
Create Watch Expression Converts the selected register into a watch expression.
CutCopies the currently selected text or element to the clipboard and removes the element.
Disable icon
DisableDisables the selected register.
Display as Array icon
Display As Array...Open the Display As Array dialog which allows you to specify the start and length of the array.
 Edit Register Group Open the Register Group dialog to edit the selected register group.
Enable icon
Enable
Enables the selected register.
Find...Open the Find dialog which allows you to find specific elements within the view.
Find/ReplaceOpen the Find / Replace dialog.
FormatSelect a format type. Choices include: Default, Decimal, Hexadecimal, Octal or Binary.
Max Length... Open the Configure Details Pane dialog to set the maximum number of characters to display. Default is 10000.
PastePaste the current clipboard content as text.
 Remove Register Group Removes the currently selected register group.
Restore Default Register GroupsRestores the original register groups.
Restore Original Type Returns the selected register to the original type.
Select All Select all the editor content.
Wrap Text Activate to wrap the text contents within the visible area of the Details pane of the Registers view.
- -

Related concepts -
-Debug information

-

Related tasks -
-Working with registers

-

Related reference -
-C/C++ Views

-
-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_arg.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_arg.htm deleted file mode 100644 index e22bab5c5fd..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_arg.htm +++ /dev/null @@ -1,48 +0,0 @@ - - - - - - - - -Arguments page, Run or Debug dialog box - - - - -

Arguments page, Run or Debug dialog boxes

- -

The Arguments page of the Run or Debug dialog box lets you specify the program arguments -that an application uses and the working directory for a run or debug configuration.

- -Arguments page, Run or Debug dialog -

- - - - - - - - - - -
ComponentDescription
Program argumentsSpecifies the arguments that are passed on the command line.
Variables...Select variables by name to include in the program arguments list.
Working directorySpecifies the run/debug configuration working directory.
Use defaultCheckmark to specify the local directory or uncheck to specify a different workspace, a file system location, or variable.
Workspace...Specifies the path of, or browse to, a workspace relative working directory.
File System...Specifies the path of, or browse to, a file system directory.
Variables...Select variables by name to include in the working directory.
- - -

Related concepts -
-Debug overview
-Debug information

-

Related tasks -
-Running and debugging

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_comm.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_comm.htm deleted file mode 100644 index d53384739f4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_comm.htm +++ /dev/null @@ -1,52 +0,0 @@ - - - - - - - - -Common page, Run or Debug dialog box - - - - -

Common page, Run or Debug dialog box

- -

The Common page of the Run and Debug dialog boxes lets you specify -the location in which to store your run configuration and how you access it, how standard input and output is handled, and if background launches are enabled or not.

- -Common page, Run or Debug dialog box -

- - - - - -

- - - - - - - - -
ComponentDescription
Local fileSaves the launch configuration locally.
Shared fileSpecifies the path of, or browse to, a workspace to store the launch configuration file, and be able to commit it to CVS.
Display in favorites menuAdd configuration name to Run or Debug menus for easy selection.
Console EncodingSpecify encoding scheme to use for console output.
Allocate Console (necessary for input)Check to assign a console view to receive the output.
FileSpecify file name to save output.
Browse Workspace...Specifies the path of, or browse to, a workspace to store the output file.
Browse File System...Specifies the path of, or browse to, a file system directory to store the output file.
Variables...Select variables by name to include in the output file.
AppendCheck to append output. Uncheck to recreate file each time.
Launch in backgroundCheck to launch configuration in background mode.
- - -

Related concepts -
-Debug overview
-Debug information

-

Related tasks -
-Running and debugging

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_dbg.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_dbg.htm deleted file mode 100644 index 96a090fd041..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_dbg.htm +++ /dev/null @@ -1,46 +0,0 @@ - - - - - - - - -Debugger page, Run or Debug dialog box - - - - -

Debugger page, Run or Debug dialog box

- -

The Debugger page of the Run and Debug dialog boxes lets you select a debugger to use when debugging an application.

- -Debugger page, Run or Debug dialog box -

- - - - - -

- -
ComponentDescription
DebuggerSelects debugger type from the list.
Stop on startup atStops program at specified location.
AdvancedOpens the Advanced Options dialog.

-

Debugger OptionsDisplays options specific to the selected debugger type.
- - -

Related concepts -
-Debug overview
-Debug information

-

Related tasks -
-Running and debugging

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_env.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_env.htm deleted file mode 100644 index c3c88273d59..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_env.htm +++ /dev/null @@ -1,49 +0,0 @@ - - - - - - - - -Environment page, Run or Debug dialog box - - - - -

Environment page, Run or Debug dialog box

- -

The Environment page of the Run and Debug dialog boxes lets you -set environment variables and values to use when an application runs.

- -Environment page, Run or Debug dialog box -

- - - - - - - - - - - -
ComponentDescription
NameDisplays the name of environment variables.
ValueDisplays the value of environment variables.
NewCreates a new environment variable.
Select...Select one or more environment variables to set.
EditModifies the name and value of an environment variable.
RemoveRemoves selected environment variables from the list.
Append environment to native environmentAppend the environment variables shown to the current native environment.
Replace native environment with specified environmentReplaces the current native environment with the specified environment set shown.
- - -

Related concepts -
-Debug overview
-Debug information

-

Related tasks -
-Running and debugging

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_launch_group.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_launch_group.htm deleted file mode 100644 index b8559e891c5..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_launch_group.htm +++ /dev/null @@ -1,123 +0,0 @@ - - - - - - - - -Group Launch Configuration - - - - -

Launch Group

- -

The user can launch multiple applications at the same time or in sequential order. This is made possible by the launch configuration type: Launch Group.

- -

Launches tab

-

- -The Launches tab lets you add and delete launch configurations to the group. -It also allows you to temporarily disable, re-order and edit properties of the elements in the group. - -

-Run Configuration dialog, Launch group -

- - - - - - - - - - - - -
ComponentDescription
NameDisplays the name of the launch configuration and a checkbox for enabling or disabling the configuration.
ModeDisplays the mode the configuration will run in when the group is launched.
ActionDisplays the optional action that will be carried after the configuration is launched.
UpMove selected configuration(s) up
DownMove selected configuration(s) down
Add...Opens a dialog to add a new configuration.
Edit...Opens a dialog to edit values for configuration(s).
RemoveRemoves selected configuration(s) from the list.
- - -

Common tab

- -The Common tab lets you select where the configuration is stored, see Common tab reference page for details. - -

Add and Edit launch configuration Dialog

-

-Edit Launch Configuration dialog -

- - - - - - - - - - - -
ComponentDescription
Launch ModeThe Launch Mode combobox at the top of the dialog serves a dual purpose. -
    -
  1. - It dictates the desired mode for the launch configuration being added, -and
  2. -
  3. - It establishes a 'mode' filter for the launch configurations that are -exposed to the user (for selection) in the area below the combobox -
  4. -
-

-For example, when the 'debug' mode is selected, (1) only launch configurations -that support being invoked in 'debug' mode appear. Also, (2) when the launch -group is invoked, that particular child launch configuration will be invoked in -'debug' mode. -

Filter inputType in filter input to filter list of configurations by name
Configurations treeLists all available launch configurations for the selected Launch Mode, filtered by Filter input.
Use default mode when launching -This checkbox acts as a sort of override to whatever mode is set in the Launch Mode -combobox. Checking this option indicates that the child launch configuration -should be launched in the mode used to initiate the launch group launch. This -needs some clarification. First, realize that a launch configuration can be -invoked from either the 'Debug' or the 'Run' actions (and some comparable -'profile' action in certain Eclipse configurations/products). That means, the -launch group itself can be launched either in debug or run mode. When you check -the Use default... checkbox, you're saying: launch this particular child -configuration in the mode that the parent (launch group) is launched with. If -you do not have that checkbox checked, then the child configurations will be -invoked in whatever mode each individual child is configured with. -

-Note that Use default... control can allow you to create a launch group -that will not be successful. For example when one or more launch configurations -selected cannot be launched in the mode dictated by launch group mode. -

Post launch action -There are several actions available that control what should be done after each launch: -
    -
  • Delay - Waits a specified number of second before launching the next configuration in the group
  • -
  • Wait until terminated - Waits until current launch is terminated
  • -
  • None - Proceeds to launch next configuration immediately
  • -
-
- - - -

- - - - - -

Related concepts -
-Debug overview
-Debug information

-

Related tasks -
-Running and debugging

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_main.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_main.htm deleted file mode 100644 index 3ebb7382f52..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_main.htm +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - -Main page, Run or Debug dialog box - - - - -

Main page, Run or Debug dialog boxes

- -

The Main page of the Run dialog box and the Debug dialog box, identifies the project and application you want to run or debug.

- -Main page, Run or Debug dialog box -

- - - - - - - -
ComponentDescription
ProjectSpecifies the name of the project.
C/C++ ApplicationSpecifies the name of the application.
Search Project...Specifies the binary or binaries to run within the project.
Connect process input output to a terminal 
- - -

Related concepts -
-Debug overview
-Debug information

-

Related tasks -
-Running and debugging

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_srce.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_srce.htm deleted file mode 100644 index c1d51fb4923..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_run_dbg_srce.htm +++ /dev/null @@ -1,49 +0,0 @@ - - - - - - - - -Source page, Run or Debug dialog box - - - - -

Source page, Run or Debug dialog box

- -

The Source page of the Run and Debug dialog boxes lets you specify the location of source files used when debugging a C or C++ -application. By default, this information is taken from the build path of your project.

- - -Source page, Run or Debug dialog box -

- - - - - -

- - - - -
ComponentDescription
AddAdds new source containers to the Source Lookup Path search list.
Edit...Modifies the content of the selected source container.
RemoveRemoves selected items from the Source Lookup Path list.
UpMoves selected items up the Source Lookup Path list.
DownMoves selected items down the Source Lookup Path list.
Restore DefaultRestores the default source search list.
Search for duplicate source files on the pathControls whether to continue search for files with the same name.
- - -

Related concepts -
-Debug overview
-Debug information

-

Related tasks -
-Running and debugging

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_scanner_cfg_disc.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_scanner_cfg_disc.htm deleted file mode 100644 index e67e7bc9afd..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_scanner_cfg_disc.htm +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - -Paths and symbols page, C/C++ Properties window - - - - -

Scanner Configuration Discovery

- -

You can configure various options for the scanner configuration on the Scanner Configuration Discovery page of the C/C++ Properties window.

-

Editor General Preferences Window

-
-
Enable build output parser
-
Select this checkbox to configure the scanner to parse the output from a build.
-
Make build output parser:
-
Select a build output parser from the list.
-
Enable generate scanner info command
-
Select this checkbox to enable retrieval of information from the scanner
-
Use default
-
Select this checkbox to use the default scanner information command.
-
Generate scanner info command
-
If you did not select Use default checkbox, you can specify the scanner information command.
-
Command output parser
-
Select a command output parser from the list.
- -
- -

Related concepts -
-Build overview

-

Related tasks -
-Including paths and symbols

-

Related reference -
-Project properties

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_search.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_search.htm deleted file mode 100644 index 43d0109e04d..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_search.htm +++ /dev/null @@ -1,202 +0,0 @@ - - - - - - C/C++ search - - - -

C/C++ search

-

Search Dialog Box

-

-
-
Search string
-
Specifies a search string.
-
The search functions support the following wildcards: -
    -
  • Use * to represent any series of characters
  • - -
  • Use ? to represent any single character
  • - -
  • Use \* to find an asterisk character (*)
  • - -
-

-
- -
Case sensitive
-
Searches will return results which match capitalization specified -in the search string precisely.

- -
Search for
-
Specify the types of elements to include in the search:
-

-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Search forDescription
Class/StructIncludes classes and structs in your search.
FunctionSearches for global functions or functions in a namespace -(functions that are not members of a class, struct, or union).
VariableSearches for variables that are not members of a class, -struct, or union.
UnionSearches for unions.
MethodSearches for methods that are members of a class, struct, -or union.
FieldSearches for fields that are members of a class, struct, or -union.
EnumerationSearches for enumerations.
EnumeratorSearches for enumerators.
NamespaceSearches for namespaces.
Typedef
-
Searches for typedef.
-
Macro
-
Searches for macro.
-
Any ElementIncludes all elements in the search.
-
-
- -
Limit to
-
Specify the types of context to search:
-

-
-
- - - - - - - - - - - - - - - - - - - - - - - -
Limit toDescription
DeclarationsLimits the search to declarations.
DefinitionsLimits the search to definitions (for functions, methods, -variables, and fields).
ReferencesLimits the search to references.
All OccurrencesIncludes declarations, definitions, and references in the -search.

-
- -
Scope
-
Choose the scope of the search:
-

-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ScopeAvailabilityDescription
Workspaceall elementsSearches in the full workspace
Selected Resourcesall elementsSearches the resources selected in the Projects view
Enclosing Projects
-
all elements
-
Searches in the enclosing -projects (plus the include paths) of the selected resource
-
Workings Setall elementsSearches in a working set

-
- -
Working sets can be created and used from within the search dialog.
-
-

Related concepts
-Coding aids
-C/C++ search

-

Related tasks
-Searching for C/C++ elements
-Customizing the C/C++ -editor

-

Related reference -
-C/C++ editor preferences
-Search action
-Search view

-

-Red Hat Copyright Statement
-IBM Copyright Statement

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_search_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_search_view.htm deleted file mode 100644 index 8634a6f204b..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_search_view.htm +++ /dev/null @@ -1,125 +0,0 @@ - - - - - - - Search view - - - - - -

Search view

-

Any matches are reported in the Search view.

-

Search View

- -

When you have completed a search and have results in the -Search view, -you can put the focus on that view and get more options on the -Search menu. -

-

- A C/C++ search can also be conducted via the context menu of selected resources and elements in the following views: -

-
    -
  • Project Explorer
  • -
  • C/C++ Projects
  • -
  • Outline view
  • -
  • Search result view
  • -
-

The search context menu is also available in the C/C++ editor. The search is only performed if the currently selected text can be resolved to a C/C++ element.

-

The type of the selected C/C++ element defines which search context menus are available. The C/C++ editor does not constrain the list of available C/C++ searches based on the - selection.

- - -

Search view toolbar options

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconCommandDescription
Next iconNextNavigates to the next search result.
Previous iconPreviousNavigates to the previous search result.
Remote the Selected Matches iconRemove Selected Matches (Delete)Removes user selected matches from the search console.
Remove all Matches iconRemove All MatchesClears the search console.
Expand All iconExpand AllExpands all search results.
Collapse All iconCollapse AllCollapses all search results.
Cancel Search iconCancel Current SearchTerminates the current search.
Repeat Search iconRun the Current Search AgainRepeat the search using the same criteria.
Show Previous Searches iconShow Previous SearchesShows the list of previously run searches which can be reselected.
Pin view iconPin the Search ViewForces the Search view to remain on top of other views in the workbench area.
Menu iconMenuDisplays assorted options available for the Search view, including:
-
    -
  • Show as List
  • -
  • Show as Tree (default)
  • -
  • Hide Potential Method Calls
  • -
  • Filters...
  • -
  • Show Enclosing Definitions
  • -
-
- -

Related concepts
-Coding aids
-C/C++ search

-

Related tasks
-Searching for C/C++ elements
-Customizing the C/C++ editor

-

Related reference -
-C/C++ editor preferences
-Search action
-Search dialog

- -
-

-Red Hat Copyright Statement
-IBM Copyright Statement
-Nokia Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_signals_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_signals_view.htm deleted file mode 100644 index 3fd2ea50d07..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_signals_view.htm +++ /dev/null @@ -1,111 +0,0 @@ - - - - - - - - -Signals view - - - - - -

Signals view

- -

The Signals view of the Debug perspective lets you view the signals defined on the selected debug target and how the -debugger handles each one.

-

Signals View

- -

Signals view toolbar options

-

The table below lists the toolbar options displayed in the Signals view.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Signals Columns -
NameDisplays the name of the signal.
PassWhere "yes" is displayed, the debugger lets your program see the - signal. Your program can handle the signal, or else it may terminate if the - signal is fatal and not handled.
SuspendWhere "yes" is displayed, the debugger suspends your program when this - signal is handled.
DescriptionDisplays a description of the signal.
-

Signals view context menu commands

-

The Signals view context menu commands include:

- - - - - - - - - - - - - - - - - - - - - - - -
- Icon - - Name - - Description -
 Signal Properties...

Opens the properties window for the selected signal enabling you to: -

    -
  • pass or not pass the signal to the program
  • -
  • suspend the program when the signal occurs
  • -

- Resume with Signal Icon - Resume With SignalResume program execution after receiving the signal.
-

Related concepts -
- Debug information

-

Related tasks -
-Debugging

-

Related reference -
-C/C++ Views

-
-

-IBM Copyright Statement
-Nokia Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_tasks_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_tasks_view.htm deleted file mode 100644 index f0779b42baf..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_tasks_view.htm +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - -Tasks View - - - - - -

Tasks View

- -

The Tasks view lets you create your own tasks. In addition to having the Tasks view -automatically add TODO and FIXME tasks from comments in code, -you can set personal reminders for tasks, such as unfinished functions that you write or error -handling routines that you want to verify. -

- -

To set a reminder:

- -
    -
  1. In Tasks view, right-click the Tasks pane, and select New Task.
  2. -
  3. In the Description box, type a new task.
  4. -
  5. Click OK.
  6. -
- -

Related concepts -
Tasks View (Workbench concept) -

- -

Related references -
C/C++ Views -

- -
-

IBM Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_toolbar.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_toolbar.htm deleted file mode 100644 index 12c38fc8818..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_toolbar.htm +++ /dev/null @@ -1,67 +0,0 @@ - - - - - - - C/C++ Toolbar - - - - -

C/C++ Toolbar

-

C/C++ Toolbar

-

-

C/C++ Toolbar icons

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IconCommandDescription
Debug iconDebugLaunches the Debug dialog box.
Run iconRunLaunches the Run dialog box
Open Element iconOpen ElementBrings up the Open Element selection dialog to open an element in the editor. - The Open Elements selection dialog shows all elements existing in the workspace.
Search iconSearchLaunches the C/C++ Search dialog box
Toggle Mark Occurrences iconToggle Mark OccurrencesTurns mark occurrences on and off in the C/C++ editor.
Next annotation iconNext annotationGo to the next annotation in the editor.
Previous annotation iconPrevious annotationGo to the previous annotation in the editor.
Go to Last Edit Location iconGo to Last Edit LocationReturns editor view to the last line edited, if the file that was last edited was closed it will be re-opened.
-

- -

-IBM Copyright Statement -

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_type_hierarchy_view.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_type_hierarchy_view.htm deleted file mode 100644 index 844d7503639..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_type_hierarchy_view.htm +++ /dev/null @@ -1,228 +0,0 @@ - - - - - - Type Hierarchy View - - - - - -

- Type Hierarchy view -

-

- The Type Hierarchy view shows a tree display of the selected type or method. The Type Hierarchy view consists of two panes: -

-
    -
  • - Type Hierarchy tree pane -
  • -
  • - Member list pane (optional) -
  • -
-

- Type Hierarchy view toolbar -

-

- The type hierarchy tree shows supertypes, subtypes or both of a given type depending on the selection made in the - toolbar. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Type Hierarchy Toolbar Options
IconCommandDescription
Show Hierarchy icon -

- Show the Type Hierarchy -

-
-

- This command displays the type in its full context (i.e., superclasses and subclasses) in the Hierarchy view. -

-
Show Supertype Hierarchy icon -

- Show the Supertype Hierarchy -

-
-

- This command displays the supertypes in the Hierarchy view. The tree starts at the selected type and - displays the result of traversing up the hierarchy. -

- Note: The selected type is always at the top level, in the upper-left corner. -
Show Subtype Hierarchy icon -

- Show the Subtype Hierarchy -

-
-

- This command displays the subtypes of the selected type in the Hierarchy view. The tree starts at the selected type and - displays the result of traversing down the hierarchy -

- Note: The selected type is always at the top level, in the upper-left corner. -
History List icon -

- Show History List -

-
-

- This menu displays a history of previously displayed type hierarchies. -

-
Refresh icon -

- Refresh -

-
-

- This command updates the view content by running a new query on the index database. -

-
Cancel icon -

- Cancel -

-
-

- This command cancels a currently running query. -

-
Menu icon -

- View Menu -

-
-

- Shows additional options to manage the Type Hierarchy view including:
-

    -
  • Select Working Set...
  • -
  • Deselect Working Set
  • -
  • Edit Active Working Set...
  • -
  • Type Hierarchy
  • -
  • Supertype Hierarchy
  • -
  • Subtype Hierarchy
  • -
  • Layout
  • -
  • Show File Names
  • -
-

-
-

- Member list pane toolbar buttons -

-

- The member list pane displays the members of the currently selected type in the type hierarchy tree pane. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Type Hierarchy Member Options
CommandDescription
-

- Show All Inherited Members -

-
-

- Shows or hides all methods and fields inherited by base classes. When this option is set, the name of the type that defines the method is appended to the method - name. -

-
-

- Hide Fields -

-
-

- Shows or hides the fields. -

-
-

- Hide Static Fields and Methods -

-
-

- Shows or hides the static fields and methods. -

-
-

- Hide Non-Public Members -

-
-

- Shows or hides the static fields and methods. -

-
-

- Related reference
- Views -

-
-Nokia Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_view_executables.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_view_executables.htm deleted file mode 100644 index fe975a16a0f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_view_executables.htm +++ /dev/null @@ -1,100 +0,0 @@ - - - - - - - Executables view - - - - - -

Executables view

-

The Executables view provides a dynamic list of executables and their related source files. The Executables view makes it easy to:

-
    -
  • target all binaries for debugging because the symbolics are automatically loaded when a bld.inf is imported or a project is created from a template
  • -
  • debug a binary that is not part of a project in the workspace by importing it into the Executables view to load the symbolics
  • -
  • debug a process running on a device by attaching to the process and importing the binaries associated with the process into the Executables view to load the symbolics. For example, you to debug a library loaded by the process, you would need to import the libary and the process executable.
  • -
  • remove binaries when a project is closed or deleted from the workspace
  • -
  • remove binaries imported from outside the workspace by deleting the binary from the Executables project in the Project Explorer view
  • -
  • locate and manage which source and resource files are associated with each executable. Paths shown in black text have been resolved, those in gray text cannot be found.
  • -
  • identify and correct any path issues with missing source files (shown in gray text). Double-click the missing source file to open a Locate File editor view which enables you to find the missing file.
  • -
  • view routines and header files used by the source file. Click the tree control to expand or collapse a list of included header files and routine names for fast navigation.
  • -
  • find and set breakpoints, watchpoints, and eventpoints in source files. Double-click a source file to open it in an editor view and to review the status of its breakpoints.
  • -
-

In addition, an Executables project is created in the Project Explorer view. The binaries shown in the Executables project can be deleted which also removes them from the Executables view. For binaries outside the workspace you must import them into the Executables view so their symbolics can be used during the debug session. You can also drag and drop executables into the view.

-

Executables view

-

The Executables view consists of the Executable Name and Source File Name panes described in the table below. Use the Columns button in the toolbar to show or hide specific columns in each pane. Columns can be sorted and rearranged in the order desired.

- - - - - - - - - - - - - - -
Executables View Options
PaneExplanation
Executable Name

Displays a list of executables in the workspace as well as other files added by the user. Select an executable to update the Source File Name pane with related files. The executable information shown can include:

-
    -
  • Executable Name - (default) Name of the executable file.
  • -
  • Executable Project - (default) The project associated with the executable.
  • -
  • Executable Location - (default) The current location of the executable.
  • -
  • Executable Size - The executable size shown in bytes.
  • -
  • Executable Date - The source file's modification date.
  • -
  • Executable Type - The executable type (.exe, etc.)
  • -
-

Click the Columns icon (columns icon) to set which columns to show in this pane.

Source File Name

Displays a list of source files for the selected executable as extracted from the symbol table. The source file information shown can include:

-
    -
  • Source File Name - (default) Name of the source file used by the executable. If no binary files are in the project the message No source files found in <project_name> is shown.
  • -
  • Source File Location - (default) The current location of the source file. If the path is shown in gray text the source file was not located. To locate it, double-click to open a new editor, then click Locate File... to locate the missing file. The new path is compared to the old one and all files located in the same directory are automatically updated to use the new path.
  • -
  • Source File Original Location - (default) The original location of the source file which may be different than the current location.
  • -
  • Source File Size - The source file size shown in bytes.
  • -
  • Source File Date - The source file's modification date.
  • -
  • Source File Type - The source type (.h, .inc, etc.)
  • -
  • Missing Source Files - Gray text indicates files not found. Double-click the file to browse for the missing file.
  • -
-

Expand a file's tree control to view the functions and header files used by the file. Double-click to open the source file for editing or to set breakpoints.

-

Click the Columns icon (columns icon) to set which columns to show in this pane.

-

Executables view toolbar icons

-

The table below lists the unique icons displayed in the Executables view toolbar.

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Executables View Toolbar Options
CommandNameDescription
refresh executables icon
Refresh the list of executables
Click to refresh the executables list.
import executables icon
Import an executable file Click to import an executable not in the workspace into the executables list.
remove executables icon
Remove the selected executables Click to remove the selected executables from the executables list.
columns icon
ColumnsOpens the Configure Columns dialog for configuring which columns appear in the Executable and Source File panes.
-

- Related reference
- Views -

-
- Nokia Copyright Statement
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_views.htm b/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_views.htm deleted file mode 100644 index 2a54629c285..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/reference/cdt_u_views.htm +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - -Selecting Views and Editors - - - - -

Selecting Views and Editors

- -

To see a list of all views, from the menu bar choose Window > Show View.

-

Show View Dialog Box

- -The following views comprise the C/C++ Projects View: - -

Basic views

-
-
Console
Displays the application's output.
-
Project Explorer
Displays the file system under the launchdir/workspace directory.
-
Outline
Displays the functions and header files in your source files. Open a source file in an editor to view its outline.
-
Problems
Displays problems.
-
Properties
Displays the name, path, size, permissions, and last modified date of the resource highlighted in the Project Explorer view.
-
Search
Displays the results of file or text searches.
-
- -

C views

-
-
C/C++ Projects
Displays your current projects. This is similar to the Project Explorer view.
-
- - -

Editor view

-The Editor view is not listed under Window > Show View , it is opened automatically by the -Stand-alone Debugger when displaying files and whenever an editable file is opened from the C/C++ Projects or Project Explorer views. - -

-Red Hat Copyright Statement
-IBM Copyright Statement -

- -
- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_brkpnts_watch.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_brkpnts_watch.htm deleted file mode 100644 index 6a64116ea1a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_brkpnts_watch.htm +++ /dev/null @@ -1,28 +0,0 @@ - - - - - - -Using breakpoints, watchpoints, and breakpoint actions - - - - - -

Using breakpoints, watchpoints, and breakpoint actions

- -

The following topics explain how to use breakpoints, watchpoints, and breakpoint actions:

- -

Adding breakpoints
- Adding watchpoints
- Adding breakpoint actions
- Removing breakpoints and watchpoints
- Enabling and disabling breakpoints and watchpoints
- Attaching or removing breakpoint actions
-

-

QNX Copyright Statement

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_build_task.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_build_task.htm deleted file mode 100644 index 2211edbf908..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_build_task.htm +++ /dev/null @@ -1,35 +0,0 @@ - - - - - - -Building projects - - - - -

Building projects

-

The following topics explain how to build a project, and to manage compile errors:

- Renaming a project
- Defining Project Build settings
- Adding and Editing Build Variables
- Tuning Error Parsers
- Selecting a binary parser
- Adding include paths and symbols
- Selecting a project type
- Building manually
- Removing the Build Automatically setting
- Autosaving on a build
- Creating a make target
- Configuring Project References
- Customizing the Console view
- Tracking down compilation errors
- Jumping to errors
- Filtering the Problems view
- - -

QNX Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_builderrors.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_builderrors.htm deleted file mode 100644 index bb6d4b439ed..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_builderrors.htm +++ /dev/null @@ -1,61 +0,0 @@ - - - - - - -Tracking down compilation errors - - - - - -

Tracking down compilation errors

- -

After a build finishes, CDT displays the build output in the Console View. The build output shows -the result of build and a user can inspect it to find out if it was successful or not. To assist with that -CDT Error Parsers scan build output and create Problem Markers which are presented in a variety of ways: -

-

-

    -
  • as highlighted lines on the console,
  • -
  • in the Problems View,
  • -
  • as icon decorators in the Project Explorer on the file, its parent folders and the project,
  • -
  • icons in editor's overview rulers,
  • -
  • as squiggly line marking the problematic code in editor.
  • -
-

-

-There are 3 types of Problem Markers: Errors Error, -Warnings Warning and InfoInfo. -A user can control how the markers are -generated on "Error Parsers" Preference page. -

- -

The following topics describe how to view and manage compile errors: -
Jumping to errors -
Filtering the Problems view -

- -

Related concepts -
Build overview

-

- -

Related tasks -
Tuning Error Parsers -
Defining Project Build settings -
Building projects -

- -

Related reference -
Error Parsers tab -
Console View -
Problems View -

- - -

QNX Copyright Statement

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_con_assist.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_con_assist.htm deleted file mode 100644 index 650f32b4797..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_con_assist.htm +++ /dev/null @@ -1,23 +0,0 @@ - - - - - - -Working with Content Assist - - - - - -

Working with Content Assist

-

The following topics provide information about code entry aids:

- Using Content Assist
- Creating and editing templates
- Importing and exporting templates
- - -

QNX Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_debug.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_debug.htm deleted file mode 100644 index 83024519892..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_debug.htm +++ /dev/null @@ -1,35 +0,0 @@ - - - - - - -Debugging - - - - - -

Debugging

- -

The following topics explain how to debug your project:

- - Debugging a program
- Debugging an existing executable
- Using breakpoints and watchpoints
- Adding breakpoints
- Adding watchpoints
- Removing breakpoints and watchpoints
- Enabling and disabling breakpoints and watchpoints
- Controlling debug execution
- Stepping into assembler functions
- Working with variables
- Adding expressions
- Working with registers
- Working with memory
- -

QNX Copyright Statement

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_proj_files.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_proj_files.htm deleted file mode 100644 index b06b5a1fbae..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_proj_files.htm +++ /dev/null @@ -1,28 +0,0 @@ - - - - - - -Working with C/C++ project files - - - - - -

Working with C/C++ project files

-

The following topics explain how to create and manage project files:

- Displaying C/C++ file components in the C/C++ Projects view
- Converting a C or C++ nature for a project
- Creating a C/C++ file
- Creating a makefile
- Hiding files by type in the C/C++ Projects view
- Converting CDT 1.x Projects
- Converting CDT Managed Make Projects
- Adding Convert to a C/C++ Make Project to the New menu
- Setting up include paths and macros for C/C++ indexer
- -

QNX Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_run.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_run.htm deleted file mode 100644 index cec3403bab4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_run.htm +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - -Using Run/Debug Configurations - - - - - -

Using Run/Debug Configurations

-

The following topics explain how to run or debug a C or C++ application using an existing run/debug configuration, and how to create a new run/debug configuration.

- Creating or editing a run/debug configuration
- Selecting a run or debug configuration
- Creating a run or debug configuration
- Selecting an application to run or debug
- Specifying execution arguments
- Setting environment variables
- Defining debug settings
- Specifying the location of source files
- Specifying the location of the run configuration
- Debugging
- Debugging a program
- Using breakpoints and watchpoints
- Adding breakpoints
- Adding watchpoints
- Removing breakpoints and watchpoints
- Enabling and disabling breakpoints and watchpoints
- Controlling debug execution
- Stepping into assembler functions
- Working with variables
- Adding expressions
- Working with registers
- Working with memory
- - -

QNX Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_run_config.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_run_config.htm deleted file mode 100644 index f00e1c90cc7..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_run_config.htm +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - -Creating or editing a run/debug configuration - - - - - -

Creating or editing a run/debug configuration

-

While the Stand-alone Debugger creates a run/debug configuration for you automatically, -advanced users or those familiar with the full C/C++ IDE may wish to create and run -their own configuration. You may think of a run configuration as a subset of the debug -configuration whereby the application is run without stopping for breakpoints/etc.. All the -common settings are shared. You can create a run configure a run environment with -which to run your application.

- -

The Run and Debug pages of the configuration wizard contain the following tabs:

- -

Run and Debug tabs

- -

You will use these tabs to customize your run and debug configurations.

- -

The following topics explain how to create a run or debug configuration:

- Selecting a run or debug configuration
- Creating a run or debug configuration
- Selecting an application to run or debug
- Specifying execution arguments
- Setting environment variables
- Defining debug settings
- Specifying the location of source files
- Specifying the location of the run configuration
- - 

- -QNX Copyright Statement -

- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_tasks.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_tasks.htm deleted file mode 100644 index 336973b40d7..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_tasks.htm +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - -Tasks - - - - - -

Tasks

-

The following topics provide step-by-step procedural instructions to help you perform various activities with the CDT:

- -Creating a project
-Creating a project via a project template
-Working with C/C++ project files
- Displaying C/C++ file components in the C/C++ Projects view
- Converting a C or C++ nature for a project
- Creating a C/C++ file
- Creating a makefile
- Hiding files by type in the C/C++ Projects view
- Converting CDT 1.x Projects
- Converting CDT 2.x Managed Make Projects
- Adding Convert to a C/C++ Make Project to the New menu
- Set Discovery Options
-Writing code
- Customizing the C/C++ editor
- Commenting out code
- Working with Content Assist
- Using Content Assist
- Creating and editing templates
- Importing and exporting templates
- Shifting lines of code to the right or left
- Navigating to C/C++ declarations
- Refactoring
- Rename
- Toggle Function Definition
-Building projects
- Renaming a project
- Selecting referenced projects
- Defining Project Build settings
- Tuning Error Parsers
- Selecting a binary parser
- Adding Include paths and symbols
- Selecting a deployment platform
- Building Manually
- Removing Build Automatically
- Autosaving on a build
- Creating a make target
- Customizing the Console view
- Tracking down compilation errors
- Jumping to errors
- Filtering the Problems view
-Running and debugging projects
- Creating or editing a run/debug configuration
- Selecting a run or debug configuration
- Creating a run or debug configuration
- Selecting an application to run or debug
- Specifying execution arguments
- Setting environment variables
- Defining debug settings
- Specifying the location of source files
- Specifying the location of the run configuration
- Debugging
- Debugging a program
- Using breakpoints and watchpoints
- Adding breakpoints
- Adding watchpoints
- Removing breakpoints and watchpoints
- Enabling and disabling breakpoints and watchpoints
- Controlling debug execution
- Stepping into assembler functions
- Working with variables
- Adding expressions
- Working with registers
- Working with memory
-Searching for C/C++ elements
- Selection Searching for C/C++ elements
- Setting Source Folders
-Include paths and macros for C/C++ indexer
- -

QNX Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_write_code.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_write_code.htm deleted file mode 100644 index c508b936f6e..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_o_write_code.htm +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - -Writing code - - - - - -

Writing code

-

The following topics explain how to work with the C/C++ editor:

- Customizing the C/C++ editor
- Commenting out code
- Working with Content Assist
- Using Content Assist
- Creating and editing templates
- Importing and exporting templates
- Shifting lines of code to the right or left
- Searching for C/C++ elements
- Selection Searching for C/C++ elements
- Navigating to C/C++ declarations
- Refactoring
- Rename
- Toggle Function Definition
-

QNX Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_brk_action.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_brk_action.htm deleted file mode 100644 index cab9e8f382a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_brk_action.htm +++ /dev/null @@ -1,49 +0,0 @@ - - - - - - -Adding breakpoint actions - - - - - -

Adding breakpoint actions

- -

To add a new breakpoint action:

-
    -
  1. Click Window > Preferences.
  2. -
  3. Expand C/C++ > Debug and click Breakpoint Actions.


    Breakpoint Actions preference dialog

  4. -
  5. In the Breakpoint Actions page, click New.


    - New Breakpoint Action dialog

    -
  6. -
  7. In the New Breakpoint Action dialog box, type a name for the action in the Action name box.
  8. -
  9. Select an action from the Action type list.
  10. -
  11. Set the action's attributes: -
      -
    • For a sound action, select a sound file.
    • -
    • For a log action, type the message to appear in the Log Action Messages console.
    • -
    • For a resume action, set the Resume after time in seconds.
    • -
    • For an external tool action, click Choose to select a program.
    • -
    -
  12. -
  13. Click OK.
  14. -
-

The new breakpoint actions appears in the Actions available for any breakpoint in the workspace list.

-

Related concepts -
-C/C++ Development perspective

-

Related tasks -
- Using breakpoints, watchpoints, and breakpoint actions

-

Related reference -
-Debug preferences

-
-Nokia Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_brkpnts.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_brkpnts.htm deleted file mode 100644 index e0297a338d0..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_brkpnts.htm +++ /dev/null @@ -1,51 +0,0 @@ - - - - - - -Adding breakpoints - - - - - - -

Adding breakpoints

- -

A breakpoint is set on an executable line of a program. If the breakpoint is -enabled when you debug, the execution suspends before that line of code -executes.

- -

To add a breakpoint point, double click the marker bar located in the left margin of the - C/C++ Editor beside the line of code where you want to add a breakpoint. A dot - Icon: Breakpoint object is - displayed in the marker bar and in the Breakpoints view, along with the name of the associated file.

- -

Edit view with the cursor highlighting a breakpoint

- -

For more information on marker bar icons, see Workbench User Guide > -Reference > User interface information > Icons and buttons > Editor area -marker bar.

-

Related concepts -
-C/C++ Development perspective
-

-

Related tasks -
-Using breakpoints and watchpoints

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_build_var.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_build_var.htm deleted file mode 100644 index 77a55d45012..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_build_var.htm +++ /dev/null @@ -1,81 +0,0 @@ - - - - - - - - -Adding and Editing Build Variables - - - - - - -

Adding and Editing Build Variables

- -

Use the Define a New Build Variable dialog box to add local build variables or the Edit Existing Build Variable -dialog box to edit a previously defined variable. Both are accessible from the Build Variables preference panel.

- -

Define a New Build Variable

-

    -
  1. Click Window > Preferences > C/C++ > Build > Build Variables
  2. -
  3. Click Add... in the Build Variables preference panel to open the Define a New Build Variables dialog box
  4. -
  5. Enter the variable name
  6. -
  7. Choose a variable type
  8. -
  9. Enter the variables value
  10. -
  11. Click OK
  12. -

- -

Define a New Build Variable dialog box

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Define a New Build Variable/Edit Existing Build Variable Dialog Box Options
OptionDescription
Variable nameEnter the variable name.
TypeChoose the variable type from the available list.
ValueEnter or edit the value of the variable.
- -

Edit Existing Build Variable

-

    -
  1. Click Window > Preferences > C/C++ > Build > Build Variables
  2. -
  3. Select the local build variable to edit in the Build Variables preference panel
  4. -
  5. Click Edit... to open the Edit Existing Build Variable dialog box
  6. -
  7. Change the variable type (optional)
  8. -
  9. Edit the variables value (optional)
  10. -
  11. Click OK
  12. -

- -

Define a New Build Variable dialog box

- -

Related reference
-Build Variables preferences

- -
-Nokia Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_codetemp.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_codetemp.htm deleted file mode 100644 index 2138bc6becc..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_codetemp.htm +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - -Creating and editing templates - - - - - -

Creating and editing templates

-

Content Assist uses templates to enable you to quickly make use of commonly used code segments.

-

To create a template:

- -
    -
  1. Click Window > Preferences.
  2. -
  3. Expand C/C++, expand Editor and select Templates.
  4. -
  5. Click New.


    - Creating a new Code Template Window

    -
    -
  6. -
  7. Do the following: (if required)

    -
      -
    • In the Name field, type a template name.
    • -
    • In the Context drop down list, select the context type for the new template; either C/C++ or a Comment.
    • -
    • In the Description field, type a description for the new template.
    • -
    • In the Pattern field, type the code for this template.
    • -
    • Click Insert Variable to add a variable from the list to the code you have entered in the Pattern field.
    • -
    -
  8. -
  9. Click OK.
    - The new template displays in the Templates list.
  10. -
- -

To edit a template:

- -
    -
  1. Click Window > Preferences.
  2. -
  3. Expand C/C++, expand Editor and select Templates.
  4. -
  5. Click Edit. The Edit Template dialog opens.


    - Editing a Code Template

    -
  6. -
  7. Do the following:

    -
      -
    • In the Name field, change the template name to create a new - template based on the current template.
    • -
    • In the Context drop down list, select the context type for the new template; either C/C++ or a Comment.
    • -
    • In the Description field, change the description of the code - template to reflect your changes.
    • -
    • In the Pattern field, edit the code.
    • -
    • Click Insert Variable to add a variable from the list to the - code you edited in the Pattern field.
    • -
    -
  8. -
  9. Click OK.
  10. -
- -

Related concepts -
-Content Assist

-

Related tasks -
-Using Content Assist
-Importing and exporting templates

-

Related reference
-Templates page

-

-QNX Copyright Statement - -

- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_custom_persp.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_custom_persp.htm deleted file mode 100644 index 92b1e7e9b74..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_custom_persp.htm +++ /dev/null @@ -1,35 +0,0 @@ - - - - - - -Adding Convert to a C/C++ Make Project to the New menu - - - - - -

Adding Convert to a C/C++ Project to the New menu

- -

If Convert to a C/C++ Project is not available in your menubar, you can add it by clicking Window > Customize Perspective

-

NOTE: This feature can update some managed make projects created by earlier versions of CDT.

-

Window - Customize Perspective menu selection

- - -

From the Customize Perspective Wizard select Convert to a C/C++ Project and click OK.

-

NOTE: Ensure New is selected in the Submenus: list.

-

Customize Perspective Wizard

- - -

The File > New > Convert to a C/C++ Project option will now be available.

-

File New Menu showing Convert to a C/C++ Project

- -

Related tasks
-Converting CDT 1.x Projects

- -

IBM Copyright Statement

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_watch.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_watch.htm deleted file mode 100644 index dc543ca28cf..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_add_watch.htm +++ /dev/null @@ -1,52 +0,0 @@ - - - - - - - - -Adding watchpoints - - - - - -

Adding watchpoints

- -

A watchpoint is a special breakpoint that stops the execution of an -application whenever the value of a given expression changes, without specifying -where it might occur. Unlike breakpoints (which are line-specific), watchpoints -are associated with files. They take effect whenever a specified condition is -true, regardless of when or where it occurred. You can set a watchpoint on a global variable by highlighting the variable in the editor, or by selecting it in the Outline view.

- -

To set a watchpoint on a global variable:

- -
    -
  1. Highlight the variable in the editor, or select it in the Outline view.
  2. -
  3. Click Run > Toggle Watchpoint.
  4. -
  5. Do any of the following: -
    • To stop execution when the watch expression is read, select the - Read check box.
    • -
    • To stop execution when the watch expression is written to, select the Write - check box.
    -
  6. -
  7. The watchpoint appears in the Breakpoints view - list.
  8. -
- -

Related concepts -
-C/C++ Development perspective

-

Related tasks -
-Using breakpoints and watchpoints

-

Related reference -
-Run and Debug dialog box

- -QNX Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_addmaketarget.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_addmaketarget.htm deleted file mode 100644 index 99da47437af..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_addmaketarget.htm +++ /dev/null @@ -1,40 +0,0 @@ - - - - - - -Creating a Make Target - - - - - -

Creating a make target

- -

-

To create a make target:

-
    -
  1. Right click on a project and select Make Target > Create.
  2. -
  3. Enter the Target name and build options then click Create.

    - Create Make Target Window
     
  4. -
  5. The make target appear in the Make Target view.

    - Make Targets View
     
  6. -
- -

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference
-Create a Make Target
-Make Target View

-
-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_addrmv_brk_action.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_addrmv_brk_action.htm deleted file mode 100644 index 3e6c573a510..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_addrmv_brk_action.htm +++ /dev/null @@ -1,54 +0,0 @@ - - - - - - -Attaching or removing breakpoint actions - - - - - -

Attaching or removing breakpoint actions

- -

You can attach one or more breakpoint actions to a single breakpoint. For example, when the breakpoint is hit you could both log a message and play a sound. Actions are executed in the order they appear in the Actions for this breakpoint list.

-

To attach or remove a breakpoint action from a breakpoint:

-
    -
  1. In the Breakpoints view, right-click the breakpoint, and select Properties.
  2. -
  3. In the Properties for C/C++ Breakpoint dialog box, click Actions.
    - Actions page in Breakpoint Properties Dialog Box
  4. -
  5. In the Available actions list: -
      -
    • Select an action and click Attach to link it to the breakpoint. Repeat as required.
    • -
    • To add a new breakpoint action, click New.
    • -
    • To edit the selected breakpoint action, click Edit.
    • -
    • To delete the selected action, click Delete.
      -

      NOTE: Deleting a breakpoint action removes it from the workspace.

      -
    • -
    -
  6. - -
  7. In the Actions for this breakpoint list you can: -
      -
    • Click Remove to delete the selected action from the list.
    • -
    • Click Up to move the selected action up in the list.
    • -
    • Click Down to move the selected action down in the list.
    • -
    -
  8. - -
  9. Click OK.
  10. -
- -

Related tasks -
- Using breakpoints, watchpoints, and breakpoint actions

-

Related reference -
-Debug preferences

-
-Nokia Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_autobuild.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_autobuild.htm deleted file mode 100644 index 56e650a51cd..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_autobuild.htm +++ /dev/null @@ -1,36 +0,0 @@ - - - - - - Removing Build Automatically - - - -

Disabling the Build Automatically option

-

By default, the Eclipse workbench is configured to build projects automatically. -However, for C/C++ development you should disable this option, -otherwise your entire project will be rebuilt whenever, for example, -you save a change to your makefile or source files. -Click Project > Build Automatically and ensure there is no -checkmark beside the Build Automatically menu item.

-

Menubar showing Project selection

-

Related concepts -
-Build overview

-

Related tasks -
-Building Manually
-Defining Project Build settings
-Building projects

-

Related reference -
-Make Builder page, -C/C++ Properties window

-IBM Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_autosave.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_autosave.htm deleted file mode 100644 index ece0b7ea303..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_autosave.htm +++ /dev/null @@ -1,44 +0,0 @@ - - - - - -Autosaving on a build - - - - - -

Autosaving on a build

- -

You can let Eclipse save modified files whenever you perform a manual build. -The files are saved before the build is performed so that the latest -version of your files is built. You can view the output of the make -utility in the Console view.

- -

To save resources before manual builds:

-
    -
  1. Click Window > Preferences.
  2. -
  3. Select General > Workspace from the list.
    - Workbench Properties options window
  4. -
  5. On the Workspace page, select the Save automatically before build check box. -
  6. Click OK.
  7. -
-

Eclipse will now save your resources when you build a project.

- -

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference -
-Make Builder page, C/C++ Properties window

- -IBM Copyright Statement - -

- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_build_process.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_build_process.htm deleted file mode 100644 index 3e97596c007..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_build_process.htm +++ /dev/null @@ -1,35 +0,0 @@ - - - - - - - - -Building a CDT project - - - - - -

Building a CDT project

- -

Provide roadmap whereby a link is provided to each build setting-related -task.

- -

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference -
-Make Builder page, C/C++ Properties window

- -IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_cbuild_pref.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_cbuild_pref.htm deleted file mode 100644 index acbe5d95dd2..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_cbuild_pref.htm +++ /dev/null @@ -1,41 +0,0 @@ - - - - - - Customizing the Console view - - - -

Customizing the Console view

-

The Console view displays the output of the utilities invoked when -building a project or the programs output when running/debugging.

-

To set Console view preferences

-
    -
  1. Click Window > Preferences.
  2. -
  3. Expand C/C++ and Build, then click Console.
    - Console Properties
  4. -
  5. To display information on the latest build only, select the Always clear console before building check box.
  6. -
  7. To open the Console view when a project is built, select the Open console when building check box.
  8. -
  9. To display the console if it is already open when a project is built, select the Bring console to top when building (if present) check box.
  10. -
  11. To change the number of lines the console stores in its history, enter a new value in the text field next to Limit console output (#lines).
  12. -
  13. To change the number of spaces displayed by a tab, enter the number in the txt field next to Display tab width.
  14. -
  15. To customize the colors used in the Console view, click a color control and select the new color.
  16. -
  17. Click OK.
  18. -
-

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference
-Views

-
-IBM Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_comment_out.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_comment_out.htm deleted file mode 100644 index c62ddfd792c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_comment_out.htm +++ /dev/null @@ -1,57 +0,0 @@ - - - - - - -Commenting out code - - - - - -

Commenting out code

- -

You can comment out one or more lines of code in any C/C++ editor view. -The leading characters // are added to the beginning of each line when commenting one or more lines of code. -You can also block comment multiple lines of code using the characters /* */.

- -

Tip: The characters /* */ on lines that already are -already commented out are not affected when you comment and uncomment code as -described above.

- -

Commenting out code menu choices

- -

To toggle // comments on code:

- -
    -
  1. In the C/C++ editor, select the line(s) of code that you want to comment out. If no lines are selected comments will be added (or removed) at the start of the lines containing the cursor.
  2. -
  3. Right-click and select Source > Toggle Comment. (CTRL+/)
  4. - -
- -

To block comment /* */ code:

- -
    -
  1. In the C/C++ editor, select multiple line(s) of code to comment out.
  2. -
  3. To comment out multiple code lines right-click and select Source > Add Block Comment. (CTRL+SHIFT+/)
  4. -
  5. To uncomment multiple code lines right-click and select Source > Remove Block Comment. (CTRL+SHIFT+\)
  6. - -
- -

Related concepts -
- Code entry

-

Related tasks -
-Customizing the C/C++ editor
-Working with Content Assist

-

Related reference -
-C/C++ editor preferences

-
-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_contentassist.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_contentassist.htm deleted file mode 100644 index 68a0c1a02c7..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_contentassist.htm +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - -Using Content Assist - - - - - -

Using Content Assist

- -

Use Content Assist to insert C/C++ elements of your project, and templates into your code. You can insert a template into your source code rather than retyping -commonly-used snippets of code.

- -

To insert a template or element:

- -
    -
  1. In the C/C++ editor, type at least the first letter of a template or - element then Ctrl+Space.
    - A list displays the templates - Templates icon followed by the elements that start with the letter combination you typed.

    - Editor View showing Content Assist Example -
  2. -
  3. Do one of the following: -
      -
    • Continue typing. The list shortens. When there is only one item in the - list, it is automatically inserted.
    • -
    • Double-click an item in the list to insert it into your code.
    • -
    • Press Esc to close the Content Assist Window.
    • -
    -
  4. -
- -

To set Content Assist preferences:

-
    -
  1. Click Window > Preferences.
  2. -
  3. Expand C/C++ and Editor.
  4. -
  5. Select Content Assist.
    - Content Assist Preferences
  6. -
  7. Do the following: -
      -
    • To insert an element when you open Content Assist and it is the only - item in the list, select the Insert single proposals automatically check box.
    • -
    • To automatically insert a common prefix of all proposals, select the Insert common prefixes automatically checkbox.
    • -
    • To display proposals in alphabetical order, rather than by relevance, select the Present proposals in alphabetical order checkbox.
    • -
    • To change Auto-Activation of content assist for ".", "->" or "::" triggers, select the appropriate checkboxes.
    • -
    -
  8. -
  9. Click OK.
  10. -
-

Related concepts -
-Content Assist

-

Related tasks -
-Creating and editing templates
-Importing and exporting templates

-

Related reference -
-Content Assist page
-Templates page

-

-IBM Copyright Statement - -

- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_controldebug.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_controldebug.htm deleted file mode 100644 index a12ec534194..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_controldebug.htm +++ /dev/null @@ -1,52 +0,0 @@ - - - - - - - - -Controlling debug execution - - - - - -

Controlling debug execution

- -

The debug execution controls are superceded by breakpoints. For example, if -you attempt to step over a function and the program hits a breakpoint, -it pauses, regardless of whether the function is completed. You can control your debug execution in various ways, but they all rely on a -core set of debug controls.

- -

To control a debug execution:

- -
    -
  1. In the Debug view, select a thread.
  2. -
  3. To control the debug session, click: -
    • Run > Resume
    • -
    • Run > Suspend
    • -
    • Run > Terminate
    • -
    • Run > Disconnect
    • -
    • Run > Remove All Terminated Launches
    • -
    • Run > Restart
    • -
    -
  4. -
- -

Related concepts -
-C/C++ Development perspective
-

-

Related tasks -
-Debugging

-

Related reference -
-Debug launch controls
-Debug view

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_conv_proj.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_conv_proj.htm deleted file mode 100644 index a043680dbc4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_conv_proj.htm +++ /dev/null @@ -1,46 +0,0 @@ - - - - - - -Converting a C or C++ nature for a project - - - - - -

Converting a C or C++ nature for a project

- -

Use the Convert to a C/C++ Project wizard to assign a C nature to a C++ project or vice versa.

- -

To assign a C or C++ nature to a project

- -
    -
  1. Click File > New > Other.
    - New Project window
  2. -
  3. Click C or C++.
  4. -
  5. Click Convert to C/C++ Make Project.
  6. -
  7. Click Next.
    - Convert C/C++ Project window
  8. -
  9. In the Candidates for conversion list, select the projects to convert.
  10. -
  11. In the Convert to C or C++ group, click C Project or C++ Project.
  12. -
  13. In the Project options group, you can specify the Project Type and Toolchain if the Specify project type option is enabled.
  14. -
  15. Click Finish
  16. -
-

Related concepts -
- CDT Projects
- Project file views -

-

Related tasks -
Writing code

-

Related reference -
-Project properties

-
-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_convert_cdt_proj.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_convert_cdt_proj.htm deleted file mode 100644 index 1d98ac8e6f4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_convert_cdt_proj.htm +++ /dev/null @@ -1,51 +0,0 @@ - - - - - - -Converting CDT 1.x Projects - - - - - -

Converting CDT 1.x Projects

- -

How you update your CDT 1.x project to the current CDT project format depends upon whether the -project is a Standard Make project or a Managed Make project. For a Standard -Make project, see Convert to C/C++ Project Wizard below.

-

Updating a Managed Make Project

- -

For a Managed Make project, the Managed Build system will prompt you to -convert your project when it attempts to read the Managed Build project -information and discovers that the project needs to be updated.  You will be prompted to update the project.

-

Update Managed Builder dialog box

-

Click Yes and the project will be updated.  The updated Managed -Build information can no longer be loaded by CDT 1.x or CDT 2.x.  Select -No and the project will not be updated.  You will be able to view the -Managed Build settings, but no changes will be saved when you close the project -or exit Eclipse.

- -

Convert to a C/C++ Project Wizard

- -

Select File > New > Convert to a C/C++ Project. If that selection is not available, you can find the instructions for adding it here.

-

File - New - Convert to a C/C++ Project menu selection

- -

From the Convert to C/C++ Make Project Wizard select the project you want to convert and click Finish.

-

Convert to C/C++ Project Wizard

- -

Note: You may need to manually enable Path Discovery for CDT 1.x Standard Make projects, depending on how your CDT project was configured. -See Set Discovery Options for details.

- - -

Related tasks
-Adding Convert to a C/C++ Project to the New menu
-Set Discovery Options
-Converting CDT 2.x Managed Make Projects

- -

IBM Copyright Statement

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_convert_mbs20_proj.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_convert_mbs20_proj.htm deleted file mode 100644 index 3b16481f6ae..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_convert_mbs20_proj.htm +++ /dev/null @@ -1,32 +0,0 @@ - - - - - - -Converting CDT 2.x Managed Make Projects - - - - - -

Converting CDT 2.x Managed Make Projects

- -

For a CDT 2.x Managed Make project, the Managed Build system will prompt you to -convert your project when it attempts to read the Managed Build project -information and discovers that the project needs to be updated.  You will be prompted to update the project.

-

Update CDT 2.x Managed Builder dialog box

-

Click Yes and the project will be updated.  The updated Managed -Build information can no longer be loaded by CDT 2.x.  Select -No and the project will not be updated.  You will be able to view the -Managed Build settings, but no changes will be saved when you close the project -or exit Eclipse.

- -

Related tasks
-Converting CDT 1.x Projects

- -

IBM Copyright Statement

- -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_create_make_target.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_create_make_target.htm deleted file mode 100644 index 74560a7a15c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_create_make_target.htm +++ /dev/null @@ -1,38 +0,0 @@ - - - - - - -Creating a Make Target - - - - - -

Creating a Make Target

- -

To create a make target:

-
    -
  1. Right click on the project and select Make Targets > Create...

    - Select Make Target, then Create
     
  2. -
  3. Enter the Target name and build options and click OK.
    - Create Make Target Window
     
  4. -
  5. The make target appear in the Make Targets view.
    - Make Targets View
     
  6. -
-

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference
-Create a Make Target
-Make Target View

-
-IBM Copyright Statement -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_cust_cpp_editor.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_cust_cpp_editor.htm deleted file mode 100644 index 763b6a242f7..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_cust_cpp_editor.htm +++ /dev/null @@ -1,55 +0,0 @@ - - - - - - Customizing the C/C++ editor - - - - - - -

Customizing the C/C++ editor

- -

You can change many of the C/C++ editor preferences.

- -

To customize the C/C++ editor preferences:

- -
    -
  1. Click Window > Preferences.
  2. -
  3. Expand C/C++, and click C/C++ Editor.
  4. -
  5. To set general preferences for the editor click the General tab.
    - Editor General Preferences Window
  6. -
  7. On the General Page set your preferences and click Apply. For a description of the General preferences click here.
  8. - -
  9. To customize the color of the text in the editable area of the C/C++ editor, click the Colors tab.
    - Editor Color Preferences Window
  10. - -
  11. On the Colors page set your preferences and click Apply. For a description of the Color preferences click here.
  12. -
  13. To customize Content Assist preferences, click the Content Assist tab. For more information, see Using Content Assist
  14. -
  15. Click OK.
  16. -
- -

Related concepts
-Coding aids

-

Related tasks -
-Customizing the C/C++ editor

-

Related reference -
-C/C++ editor preferences

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_debug_exes.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_debug_exes.htm deleted file mode 100644 index 65c7cff9cba..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_debug_exes.htm +++ /dev/null @@ -1,66 +0,0 @@ - - - - - - -Debugging Existing Executables - - - - - - -

Debugging an Existing Executable

-

Use the import feature to import and debug an executable you have already built. This feature will automatically create a project and debug configuration for you. This is helpful if you have an executable built with debug symbols but may not have the project used to build the executable.

- -

Importing Executables for Debugging

-
    -
  1. Select the File > Import... menu item.
  2. -
  3. In the Import wizard dialog, click C/C++ and select C/C++ Executable.
    -

    Import dialog

  4. -
  5. Click Next.
  6. -
  7. In the Import C/C++ Executable Files page of the Import Executable dialog:
    -
      -
    • Choose a parser from the Select binary parser list.
    • -
    • Type the executable path in the Select executable box or click Browse to locate the executable.
    • -
    • Type or click Browse to enter a directory path in the Search directory box, then select one or more executables from the C/C++ Executable Files list.
    • -
    -

    Import Executable dialog

    -

    NOTE You can import any executable, but only those built with debug symbols will be let you step through source code and see variable values.

    -
  8. -
  9. Click Next.
  10. -
  11. In the Choose Project page of the Import Executable dialog:
    -
      -
    • To import as a new project, activate New project name and type the project name.
    • -
    • To import into an existing project, activate Existing project and click Search.
    • -
    • To add a launch configuration, activate Create a Launch Configuration and select the configuration from the list, then type a name into the Name box.
    • -
    -

    Import Executable dialog

    -
  12. -
  13. Click Finish.
    -

    The executable is added to the C/C++ Projects view.

  14. -
  15. If Create a Launch Configuration was activated, the Debug dialog appears.
    -

    Debug launch configuration dialog

    -
  16. -
  17. Click Debug.
    -

    The debugger launches and you can begin debugging the executable.

  18. -
- -

Setting breakpoints

-

Expand the executable in the C++ Projects view to see the list of source files. Only executables built with debug symbols will show a list of source files. The source files can be opened in the editor so you can set breakpoints. Use these files only for debugging, you can not change them and rebuild the executable with this project.

-

C++ Projects View

- -

Related concepts
- Debug overview
- Debug information

-

Related tasks
- Debugging

-

Related reference
- Run and Debug dialog box

-
-Nokia Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_debug_prog.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_debug_prog.htm deleted file mode 100644 index 3a4ce998d11..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_debug_prog.htm +++ /dev/null @@ -1,101 +0,0 @@ - - - - - - - - -Debugging a program - - - - - -

Debugging a program

- -

To debug a program, a debug launch configuration is used. The debug configuration contains information -such as the executable being debugged, how to run the executable, and parameters for the debugger itself (in this -case: gdb). Once a launch configuration is created, it can be used again (e.g. relaunching the executable after -the debug session is terminated). By default, the Stand-alone Debugger creates a debug launch configuration for -you when you specify an executable on the command-line or if you use the New Executable... dialog.

-

There are multiple debug launch configuration types. The most common, is the Local C/C++ Application configuration -which is for running local applications and this is the configuration that the Stand-alone Debugger will set up -for you when you specify an executable in either of the aforementioned ways. - -A local C/C++ launch configuration is normally tied to an Eclipse project which -contains the executable you wish to debug. You do not have to create an Eclipse project because the Stand-alone debugger also creates the Eclipse project on your behalf as part -of importing your executable. By default, this is usually the special Executablesproject which is set aside for this purpose, but if you have imported multiple -executables at the same time, additional ExecutablesNNNN projects will be created to keep each executable -in a separate project. This is done to help the indexer keep track of the executable and all its associated source fiels.

-

There are other C/C++ debug configuration types that you may wish to use such as: -

    -
  • C/C++ Attach to Application
  • -
  • C/C++ Postmortem Debugger
  • -
-

These additional launch configurations require that you create them manually. To do this:

- -
    -
  1. In C/C++ Projects view, select a project. The C/C++ Projects view is not visible by default when you - start the Stand-alone debugger. You can access it - by using Window > Show View > C/C++ > C/C++ Projects. As mentioned, in most cases, - you will only see the Executables project. -
  2. -
  3. Click Run > Debug Configurations....
  4. -
  5. In the Debug Configurations dialog box, select a desired debug configuration type from the Configurations - list.
  6. -
  7. Click the New button in the top left.

  8. -
  9. In the Name box, type a descriptive name for this debug configuration.
  10. -
  11. In the Project box, type the name of the project containing - the application you want to debug. If you had selected a project, this project will be filled - in for you. In almost all cases, this will be the Executables project.
  12. -
  13. In the C/C++ Application box, type the name of the executable - that you want to run. This must be an application that has been imported into the project - or in the case of an Attach to Application configuration, this field can be empty.
  14. -
  15. Click Debug.

    -

    The debug perspective is opened and the application window opens on - top. In the case of an attach configuration, a dialog will pop up to allow you to select a running application.

  16. -
- -

For more information:

- - -

To use a debug configuration:

- -

You can reuse a previously created debug launch configuration to debug your -program.

- -
    -
  1. Click Run > Debug.
  2. -
  3. In the Debug dialog box, select a debug configuration from the Configurations - list.
  4. -
  5. Click Debug.
  6. -
- -

Related concepts -
-Debug overview
-Debug information

-

Related tasks -
-Debugging

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_disassembly.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_disassembly.htm deleted file mode 100644 index 8a7d8effc47..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_disassembly.htm +++ /dev/null @@ -1,41 +0,0 @@ - - - - - - - - -Stepping into disassembled code - - - - - -

Stepping into disassembled code

- -

The Disassembly view lets you examine your program as it steps into -disassembled code. This is useful when the instruction pointer enters a function for which it does not have the source. -To open the Disassembly view select Window > Show View > -Disassembly menu.

- -

To activate the instruction step mode check the Instruction Stepping Mode option (Instruction Stepping Mode icon) -on the Debug view toolbar. The Debugger switches to the instruction stepping mode automatically -when the Disassembly view has focus.

- -

Related concepts -
-C/C++ Development perspective
-

-

Related tasks -
-Debugging

-

Related reference -
-Debug views

-
-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_discovery.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_discovery.htm deleted file mode 100644 index 70b666d33d5..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_discovery.htm +++ /dev/null @@ -1,47 +0,0 @@ - - - - - - Set Discovery Options - - - -

Set Discovery Options

-

WarningNote that this functionality has been deprecated and not fully supported anymore

-

For most make projects, you will want to parse the output of -the build to populate your paths and symbols tables.

-

To populate your tables:

-
    -
  1. Right-click on a project and select Properties. -
  2. Expand C/C++ Build and select Discovery options. -
  3. Select the Automate discovery of paths and symbols option so that it is enabled. -
  4. For the scanner configuration on the Discovery Options page of the C/C++ Properties window, you have the following options: - -

    There are various discovery profiles available on a Per project basis - all discovered paths and symbols are associated with the project; all files use this information.
    - -

    -
    Enable generate scanner info command
    -
    Enables the retrieval of information from the scanner.
    -
    -

    -

    C/C++ Project Properties, Discovery Options
    -
    -
    -

    For both profiles, there is an option to discover paths and symbols -based on a previous builds' output. To activate the discovery, click Browse to select a -build log file, and then click the Load -button.
    -

    -
-
-

Related reference
-Converting CDT 1.x Projects
-C/C++ Project -Properties, Discovery Options

-QNX Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_endis_able_brk_wtch.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_endis_able_brk_wtch.htm deleted file mode 100644 index 38c1d87183a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_endis_able_brk_wtch.htm +++ /dev/null @@ -1,49 +0,0 @@ - - - - - - - - -Enabling and disabling breakpoints and watchpoints - - - - - -

Enabling and disabling breakpoints and watchpoints

- -

You can temporarily disable a breakpoint or watchpoint without losing the -information it contains.

- -

To enable or disable breakpoints or watchpoints:

-
    -
  1. In the Breakpoints view, do one of the following: -
      -
    • Select the breakpoints and watchpoints that you want to remove.
    • -
    • Click Edit > Select All.
    • -
    • Right-click, and select Select All.
    • -
    -
  2. -
  3. In the Breakpoints view, right-click the highlighted breakpoints and watchpoints and - click - Disable or Enable.
  4. -
- -

Related concepts -
-C/C++ Development perspective
-

-

Related tasks -
-Using breakpoints and watchpoints

-

Related reference -
-Run and Debug dialog box

- -IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_expressions.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_expressions.htm deleted file mode 100644 index 83a9ba183a4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_expressions.htm +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - -Adding expressions - - - - - -

Adding expressions

- -

You can add and view expressions in the Expressions view. The Expressions -view is part of the Debug perspective.

- -

To add an expression:

- -
    -
  1. Select Add Watch Expression in the context menu of the Expressions view.
  2. -
  3. Type the expression that you want to evaluate. For example, (x-5)*3 .
  4. -
  5. Click OK.

    The expression and its value appear in the - Expressions view. When the execution of a program is suspended, all expressions - are reevaluated.

  6. -
- -

Related concepts -
-C/C++ Development perspective
-

-

Related tasks -
-Debugging

-

Related reference -
-Debug views

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_filtererror.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_filtererror.htm deleted file mode 100644 index d71b0bba1b4..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_filtererror.htm +++ /dev/null @@ -1,48 +0,0 @@ - - - - - - - - -Filtering the Problems view - - - - - -

Filtering the Problems view

- -

Depending on the complexity and stage of your program, an overwhelming number of errors can be generated. You can customize Problems view to only view certain types of errors.

- -

To filter errors:

- -
    -
  1. In Problems view, click the View Menu icon - View Menu icon - in the top right corner of the view.
  2. -
  3. Use Configure Contents... to define your custom filter and click OK.
  4. -
  5. In View Menu select Show and then your filter.
  6. -
- - -

Related concepts -
Build overview -
Problems View (Workbench concept) -

- -

Related tasks -
Tracking down compilation errors -
Tuning Error Parsers -

- -

Related reference -
Problems View (Workbench reference) -

- -IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_imp_code_temp.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_imp_code_temp.htm deleted file mode 100644 index bc23bff3271..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_imp_code_temp.htm +++ /dev/null @@ -1,59 +0,0 @@ - - - - - -Importing and exporting templates - - - - - -

Importing and exporting templates

- -

You can import and export templates.

- -

Note: A template must be an .xml file formatted as follows:

- -
<?xml version="1.0" encoding="UTF-8" ?> 
-<templates>
-<template name="author" description="author name" context="C" enabled="true">author ${user}</template> 
-</templates>
-Templates Preferences - -

To import a template

-
    -
  1. Click Window > Preferences.
  2. -
  3. Expand C/C++, expand Editor and click Templates. -
  4. -
  5. Click Import.
  6. -
  7. Select the template file that you want to import.
  8. -
  9. Click OK.
    - The template list is updated to include the template that you imported.
  10. -
-

To export a template

- -
    -
  1. Click Window > Preferences.
  2. -
  3. Expand C/C++, expand Editor and click Templates.
  4. -
  5. Select the templates that you want to export and click the Export... button. The Export Templates dialog opens.
  6. -
  7. In File name box, type the path  where you want your templates file to be saved.
  8. -
  9. Click Save.
    - The templates.xml file containing the templates you exported is saved in your file system.
  10. -
- -

Related concepts -
-Content Assist

-

Related tasks -
-Using Content Assist
-Creating and editing templates

-

Related reference -
-Templates page

- -IBM Copyright Statement - -

- \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_jumperror.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_jumperror.htm deleted file mode 100644 index aaf286536a6..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_jumperror.htm +++ /dev/null @@ -1,58 +0,0 @@ - - - - - - - - -Jumping to errors - - - - - -

Jumping to errors

- -

The CDT will parse the output from the make and compiler/linker. If the CDT can -determine an error or a warning, the line is highlighted in the Console view and added -to the Problems view as a Problem Marker decorated with -error Error or warning Warning icon. -Informational messages are marked with Info Info icon. -

- -

To jump to the source of an error do one of the following:

-
    -
  • In the Console view, double-click the highlighted line.

  • -
  • In the Problems view, double-click the row of the specific error in the table.

  • -
  • If in the Problems view the error is identified as External Location in Location column, - use mouse right-click on it, then click on Open external location item in the context menu.

  • -
-

If CDT can determine file and error line and the file exists - the file opens in the C/C++ editor and the cursor moves to the line with the error.

- -

To jump to errors sequentially:

-
    -
  • In Editor use Next Annotation Next Annotation - or Previous Annotation Previous Annotation icons on the toolbar.
  • -
  • In Console view use Next Error Next Error - or Previous Error Previous Error buttons.
  • -
- -

Related concepts -
Build overview -

- -

Related tasks -
Tracking down compilation errors -
Tuning Error Parsers -

- -

Related reference -
Console View -
Problems View -

- -IBM Copyright Statement -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_manualbuild.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_manualbuild.htm deleted file mode 100644 index 3c6545e0f06..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_manualbuild.htm +++ /dev/null @@ -1,60 +0,0 @@ - - - - - - Building Manually - - - -

Building Manually

-

Manual builds let you choose the scope of a build, as well as -options for building, or rebuilding projects. You can view the output -of the make utility in the console.

-

Sample build in console view

-
-
Incremental Builds
-
To incrementally build all open projects, you can select Project -> Build All or type CTRL+B.
-
Build Individual Projects
-
To build individual projects click Project > Build Project.
-
Rebuild Projects
-
To rebuild a project right click on the project and select Rebuild -Project.
- Note: This will rebuild projects that this project -references as well, but will not rebuild projects that references this -one.
-
Build Automatically
-
This performs a Build All whenever any project file is saved, -such as your makefile.
- Tip: For C/C++ projects, this feature should be turned off. -If there is a checkmark beside Build Automatically the feature -is on. To turn it off, select Build Automatically.
-
-

Tip: If you get the error message:

-

Exec error:Launching failed

-

then CDT cannot locate the build command, (usually make). -Either your path is not configured correctly or you do not have make -installed on your system.

-

Tip: The menubar item Project > Build Working Set -submenu for C/C++ projects simply creates a link to the build all -target as defined in your makefile, and is no different from an Incremental -Build.

-

Related concepts -
-Build overview

-

Related tasks -
-Defining Project Build settings
-Building projects

-

Related reference -
-Make Builder page, -C/C++ Properties window

-IBM Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_memory.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_memory.htm deleted file mode 100644 index 971fa708642..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_memory.htm +++ /dev/null @@ -1,82 +0,0 @@ - - - - - - - - -Working with memory - - - - - -

Working with memory

- -

You can inspect and change process memory.

- -

The Memory view supports the same addressing as the C and C++ languages. You can address memory using expressions -such as:

- -
    -
  • 0x0847d3c
  • -
  • (&y)+1024
  • -
  • *ptr
  • -
- -

You can configure your output to -display hexadecimal, ascii and/or signed/unsigned decimal. You can also set the -size of the rendering columns. You can configure each memory monitor renderings -independently.

- -

You can customize the Memory view to colors and fonts displayed.

- -

To monitor process memory:

-
    -
  1. In the Debug view, select a debug session. Selecting a thread or stack frame automatically -selects the associated session.
  2. - -
  3. Select Add Memory Monitor in the context menu of the Memory Monitors pane. -The Memory Monitor dialog appears.
  4. - -
  5. Type the address or expression that specifies the memory section you want to monitor and -press "OK". The monitor appears in the monitor list and the Memory Renderings -pane displays the contents of memory locations beginning at the specified address.
  6. - -
-

To view memory in a different rendering:

-
    -
  1. Select Add Rendering in the context menu of the Memory Renderings pane. -The Add Memory Rendering dialog appears.
  2. - -
  3. Select renderings from the list and press "OK".
  4. -
-

To change process memory:

- -

Warning: -Changing process memory can cause a program to crash.

- -
    -
  1. In the Debug view, select a debug session. Selecting a thread or stack frame automatically - selects the associated session.
  2. -
  3. In the Memory Monitors pane, add a new monitor or select an existing monitor.
  4. -
  5. In the Memory Renderings pane add a new rendering or select an existing one.
  6. -
  7. Type a new value for memory.
  8. -
- -

Related concepts -
-C/C++ Development perspective
-

-

Related tasks -
-Debugging

-

Related reference -
-Debug views

-IBM Copyright Statement - -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_new_cpp.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_new_cpp.htm deleted file mode 100644 index d929a1ffd67..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_new_cpp.htm +++ /dev/null @@ -1,64 +0,0 @@ - - - - - - Creating a C/C++ file - - - - -

Creating a C/C++ file

-

Files are edited in the C/C++ editor that is, by default, located in -the editor area to the right of the Project Explorer or C/C++ Projects views.

-

The marker bar on the left margin of the C/C++ editor, displays -icons for errors, warnings, bookmarks, breakpoints and tasks.

-

For more information on the marker bar, see Workbench User Guide -> Reference > User interface information > Views and editors -> Editor area.

-

To create a C++ file:

-
    -
  1. In the Project Explorer or C++ Projects view, right-click a project, and -select New > File.
    - New > File in Projects View
  2. -
  3. In the list of projects, verify that the correct project is -selected.
  4. -
  5. In the File name box, type a name followed by the -appropriate extension.
  6. -
  7. Click Finish.
    - New File Wizard

    -

    The file will open in the C/C++ editor.

  8. -
  9. Enter your code in the editor view.
    - Editor view with a sample code
  10. -
  11. Type CTRL+S to save the file.
  12. -
-

Related concepts -
-CDT Projects
-Project file views -

-

Related tasks -
-Displaying C/C++ file components in -the C/C++ Projects view
-Hiding files by type in the C/C++ -Projects view

-

Related reference -
-Project properties

-
-

-IBM Copyright Statement

-
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_new_make.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_new_make.htm deleted file mode 100644 index d465916f26c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_new_make.htm +++ /dev/null @@ -1,57 +0,0 @@ - - - - - - -Creating a makefile - - - - - - -

Creating a makefile

- -

If you have created a Standard Make C/C++ Project, you need to provide a makefile.

- -

When you build a project, output from make is displayed in the Console view. Makefile actions are displayed in the Make Targets -view.

-

To create a makefile:

-
    -
  1. In the C++ Projects view, right-click a project, and select New > File.
    - New > File in Projects View
  2. -
  3. In the File name box, type makefile.
  4. -
  5. In the list of projects, verify that the correct project is selected.
  6. -
  7. Click Finish.
    - New File Wizard
  8. -
  9. The C/C++ editor opens. Type makefile instructions in the C/C++ editor.
    - Editor view with a sample code
  10. -
  11. Click File > - Save.
-

Related concepts -
-Makefile
-Working with C/C++ project files -

-

Related tasks -
-Displaying C/C++ file components in the -C/C++ Projects view
-Hiding files by type in the C/C++ Projects -view

-

Related reference -
-Views

-

-IBM Copyright Statement

-
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_new_run_config.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_new_run_config.htm deleted file mode 100644 index e0535e88d49..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_new_run_config.htm +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - -Creating a run or debug configuration - - - - -

Creating a run or debug configuration

- -

You can create customized run configuration which you can save for reuse.

- -

To create a run configuration:

- -
    -
  1. In the C/C++ Projects view, select a project.
  2. -
  3. Click Run > Run or Run > Debug.
  4. -
  5. In the Configurations box, expand C/C++ Local.
  6. -
  7. Click New. The name of the new project is displayed in the - Configurations box. The default name is the name of the project.
    - Run Configuration window
  8. -
  9. To change the default name of the new run/debug configuration, see - Selecting an application to run or debug.
  10. -
- -

Related concepts -
-C/C++ Projects
-Project file views

-

Related tasks -
-Creating or editing a run configuration

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_open_declarations.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_open_declarations.htm deleted file mode 100644 index 4a71dcc5ee0..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_open_declarations.htm +++ /dev/null @@ -1,48 +0,0 @@ - - - - - - -Navigating to C/C++ declarations - - - - - -

Navigating to C/C++ declarations

- -

The Open Declaration feature lets you navigate to the declaration that matches a -selected element in the C/C++ editor. It is recommended that you look for -element declarations on successfully compiled programs.

- -

To navigate to C/C++ declaration:

- -
    -
  1. In the C/C++ editor, select an object.
  2. -
  3. Right-click the selected element, select Open Declaration.
    - Editor View showing Open Declaration option -
  4. -
- -

For more information, see:

    -
  • Workbench User Guide > Tasks> Navigating and finding resources
  • -
- -

Related concepts -
-Open Declaration
-CDT Projects
-C/C++ search

-

Related tasks -
-Searching for C/C++ elements

-

Related reference -
-C/C++ search page, Search dialog box

- -IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_build_set.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_build_set.htm deleted file mode 100644 index f6b7dfefec7..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_build_set.htm +++ /dev/null @@ -1,67 +0,0 @@ - - - - - - Defining Project Build settings - - - -

Defining Project Build settings

-

The Builder Settings page lets you:

-
    -
  • Select whether CDT-generated makefile should be used or custom one.
  • -
  • Select internal or external builder (for generated makefile only).
  • -
  • Change the default build command (for external builder or for custom makefile).
  • -
  • Configure how the CDT handles make errors.
  • -
  • Change parallel build settings.
  • -
  • Map the target passed to make when you select build or rebuild.
  • -
  • Redefine build directory (for custom makefile only)
  • -
- -

To define build settings:
-In the C/C++ Projects view, right-click your project, and select Properties. -Select C/C++ Build from the list. -

- -

Defining Project Build settings

- -
    -
  • To stop the build when an error is encountered, select Stop -on first build error.
  • -
  • Select one of the following build command settings: -
      -
    • To use the default make command, select the Use Default -check box.
    • -
    • To use a build utility other than the default make command Build -Command box, clear the Use Default check box .
    • -
    -
  • -
  • In the Workbench Build Behavior box, do the following: -
      -
    • To build your project when resources are saved and change the -default make build target, select the Build on resource save (Auto -Build) check box. Enter a new build target in the Make build -target box.
    • -
    • To change the build default make build target, select the Build -(Incremental Build) check box. Enter a new build target in the Make -build target box.
    • -
    • To change the rebuild default make build target, select the Rebuild -(Full Build) check box. Enter a new build target in the Make -build target box.
    • -
    -
  • -
  • Click OK.
  • -
-

Related concepts
-CDT Projects
-Project file views

-

Related tasks -
-Working with C/C++ project files

-IBM Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_error_parser.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_error_parser.htm deleted file mode 100644 index 94932cbc4e3..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_error_parser.htm +++ /dev/null @@ -1,95 +0,0 @@ - - - - - - - - -Tuning Error Parsers - - - - - -

Tuning Error Parsers

- -

Error Parsers scan build output line by line looking for errors and warnings - (also for certain informational messages). They generate Problem Markers - which visually indicate those problems to a user. The problems are highlighted on the Console, - populate the Problems view and shown in the editor. Problem markers are organized - into Error Error, - Warning Warning - and InfoInfocategories. -

- -

There are several predefined Error Parsers where each one can handle output of a specific tool. -Normally a toolchain defines a set of Error Parsers to deal with output of each tool. It is possible -to redefine that set on a per-project basis in project properties: -

-

-

    -
  1. In the C/C++ Projects view, right-click the project, and select Properties.
  2. -
  3. Expand C/C++ Build.
  4. -
  5. Select Settings.
  6. -
  7. Click the Error Parsers tab.
  8. -
  9. In the Error parsers list, select error parsers.
  10. -
  11. Click OK.
  12. -
-

-

Note that the order of error parsers is significant. Normally an error parser will consume -the line where it spotted an error/warning and the others down the line won't get a chance to parse it. -

- -

CDT provides one special kind of error parser, CDT pushd/popd CWD Locator. -This parser does not create problem markers but it is looking for output of pushd -and popd commands which are commonly used in makefiles to print the Current Working Directory (CWD). -CDT can use this information to associate the file names appearing in the output relative to the CWD. -Note that that kind of parser needs to be the first to be able to provide the CWD to the other parsers. -

- -

Most of the error parsers are configurable via regular expression patterns and a user can: -

-

-

    -
  • Adjust a pattern to detect a problem more accurately,
  • -
  • Disable useless or proliferating problems (Note that it can have positive effect on performance of the console),
  • -
  • Create own error parser for a custom tool. Hint: To run a custom tool you can use Make Targets View.
  • -
-

- -

To customize error parsers do following: -

-

-

    -
  1. Select Window > Preferences .
  2. -
  3. Expand C/C++.
  4. -
  5. Select Error Parsers tab.
  6. -
  7. Select error parser or Add a new one.
  8. -
  9. Follow Error Parser Options to define your custom patterns
  10. -
-

- -

Related concepts -
CDT Projects -
Project file views -

- -

Related tasks -
Tracking down compilation errors -
Tuning Error Parsers -

- -

Related reference -
Console View -
Problems View -
Make Targets View -
Error Parsers tab -
Error Parser Options -

- -QNX Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_new.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_new.htm deleted file mode 100644 index 0965ff7bc8c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_new.htm +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - -Creating a project - - - - - -

Creating a project

- -

You can create a standard make or managed make C or C++ project.

- -

To create a project:

- -
    -
  1. Click File > New > Project. -
    -
    - File >New > Project -
    -
  2. -
  3. In the New Project wizard, open C or C++ folder and select corresponding project. -
    -
    - New Project Wizard
  4. - -
  5. Click Next.
  6. -
  7. In the Project Name box, type a name.
  8. -
  9. To specify a different directory in which to save your project, clear the - Use Default Location check box, and enter the path in the Location - box.
  10. -
  11. Select Project type on the left pane. For more information, see Selecting a - project type.
  12. -
  13. Select one or more toolchains from the list on the right pane.
  14. -
  15. You can change build configurations list for the project. To do it, press Next. - But usually you need not to do it.
  16. -
  17. To create your project, click Finish. -
    -
    - New Project Wizard
  18. - - -
  19. If a message box prompts - you to switch perspectives, click Yes.
  20. -
  21. Define your project - properties. For more information, - see Defining project properties.
  22. -
- -

Related concepts -
CDT Projects -
Project file views

- -

Related tasks -
Working with C/C++ project files -
Creating a project via a project template

- -

Related reference -
Project properties -
Views

- - -IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_new_with_template.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_new_with_template.htm deleted file mode 100644 index f35eae834a9..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_new_with_template.htm +++ /dev/null @@ -1,91 +0,0 @@ - - - - - - -Creating a project - - - - - -

Creating a project via a project template

- -

From CDT 4.0 its possible to create projects based upon templates defined by the IDE supplier. What this means is -that you can easily create a project which contains customized source code and is ready for use in a few clicks. Some -aspects of the generated project may be customized by the user as part of the new project wizard.

- -

To create a project from a template:

- -
    - -
  1. Click File > New > C Project or File > New > C++ Project. -
    -
    - File >New > C++ Project -
    -
  2. - -
  3. The wizard will open as shown below.
    - Expand the project type that you are interested in. For more information on project types, see Selecting a - project type This shows the template projects that you can use as a basis - for your new project. CDT comes with some simple templates, but ISVs can add further templates by using the - org.eclipse.cdt.core.templates extension point.
    - In the Project Name box, type a name. The example uses "HelloWorld" -
    -
    - New Project Wizard -
    -
  4. - -
  5. Click Next.
  6. -
  7. The next page is dependent on the type of template you selected. It will consist of a number of input fields, maybe with - default values, that will be fed into the template you create. -
    -
    - New Project Wizard -
    -
  8. - -
  9. This last page "Select Configurations" can be skipped, or allows further project configuration in the same way as non-template-based projects. -
    -
    - New Project Wizard -
    -
  10. -
  11. To create your project, click Finish. - -
  12. In the Project Explorer you will see that the new project has been created. You will see that the source file has - been customized with the values you entered earlier in the wizard. -
    -
    - The project created by the wizard -
    -
  13. - -
  14. Sometimes values you enter into the template wizard will be remembered between sessions in order that you do not - need enter them each time. If you want to change these you can use Window > Preferences > C/C++ > Template Default Values -
    -
    - New Project Wizard -
    -
  15. -
- -

Related concepts -
CDT Projects -
Project file views

- -

Related tasks -
Working with C/C++ project files -
Creating a project

- -

Related reference -
Project properties -
Views

- -IBM Copyright Statement -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_parser.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_parser.htm deleted file mode 100644 index 3591289af52..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_parser.htm +++ /dev/null @@ -1,63 +0,0 @@ - - - - - - Selecting a binary parser - - - -

Selecting a binary parser

-

Selecting the correct binary parser is important to ensure the -accuracy of the C/C++ Projects view and to successfully run and debug -your programs. Windows users should select the PE64 Windows Parser. UNIX -and Linux users should select the Elf Parser. When you select the -correct parser for your development environment and build your project, -you can view the components of the .o file in the C/C++ Projects view -and view the contents of the .o file in the C/C++ editor. You can also -easily browse for the executable when defining run/debug configurations.

-

If you use CDT-generated makefile to build your project, appropriate -binary parsers are set according to selected toolchain during creation.

-

If you use your own makefile to build, default settings -for binary parser are got from Preferences during project creation.

-

You can modify these settings in the Preferences window, to be used in future projects.

-

To set properties for future projects with user-provided Makefile :

-
    -
  1. Click Window > Preferences > C/C++ > New CDT Project wizard > Makefile project
  2. -
  3. Click the Binary Parser tab.
    - Select Binary Parser window
  4. -
  5. In the Binary Parser list, click: -
      -
    • Elf Parser, if you are a Solaris, UNIX, or Linux user.
    • -
    • PE64 Windows Parser, if you are a Windows user.
    • -
    • Cygwin PE64 Parser, if you are using Cygwin.
    • -
    -
  6. -
  7. Click OK.
  8. -
-

To change binary parsers for existing project:

-
    -
  1. In the C/C++ Projects view, right-click the project, and select Properties.
  2. -
  3. Select C/C++ Build > Settings from the list.
  4. -
  5. Click the Binary Parser tab.
    -Select Binary Parser window -
  6. -
-
-

Related concepts
-CDT Projects
-Project file views

-

Related tasks
-Working with C/C++ project files

-

Related reference -
-Binary Parser, -C/C++ Properties window

-IBM Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_paths.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_paths.htm deleted file mode 100644 index 6e6a6ccad16..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_paths.htm +++ /dev/null @@ -1,55 +0,0 @@ - - - - - - Adding Include paths and symbols - - - - -

Adding Include paths and symbols in Managed Build System

-

For CDT projects, you can define include paths and -preprocessor symbols for the parser. This lets the parser understand the contents of the C/C++ source code so that you can more effectively use the search and code completion features.

- -

If Autodiscovery is enabled, after a build finishes, any -discovered paths and symbols will be displayed in the Discovered Paths -section. You can also define the properties on a per project basis in -the C/C++ Projects or Navigator views.

-

To add include paths and symbols:

-
    -
  1. To set properties for your project, right-click your CDT -project and select Properties. Alternatively, to set properties -for a specific source file in your project, right-click a source file -within your make project and select Properties.
  2. -
  3. Expand C/C++ General and select Paths and Symbols. -


    Click here to see an illustration (displayed in a separate window).


    -
  4. -
  5. Click Add to define new element (Include Path, Symbol, Library path etc). -
  6. -
  7. Click Edit to change selected element (Include Path, Symbol, Library path etc). -
  8. -
  9. Click Delete to remove selected element (Include Path, Symbol, Library path etc). -
  10. -
  11. Click Export to make selected element (Include Path, Symbol, Library path etc) exported. -
  12. -
  13. Click Unexport to remove selected element (Include Path, Symbol, Library path etc) from export list. -
  14. -
  15. Click Move up and Move down to set elements (Include Paths, Library paths etc) order. -
  16. -
-

Related concepts
-CDT Projects
-Project file views

-

Related tasks
-Working with C/C++ project files

-QNX Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_platf.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_platf.htm deleted file mode 100644 index a09359294e6..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_platf.htm +++ /dev/null @@ -1,62 +0,0 @@ - - - - - - - - -Selecting a project type - - - - - -

Selecting a project type

- -

-While creating CDT project project, you need to select its type. -

-

-Select project type -

- -

There can be the following types: -

    -
  • Executable - makefile is generated automatically -
  • Shared library - makefile is generated automatically -
  • Static library - makefile is generated automatically -
  • Several specific types marked with rhombuses - makefile is generated automatically -
  • Makefile project - requires user's makefile; output type depends of makefile contents. -
- -

- By default, this dialog displays only the project types - that are buildable on the system on which Eclipse is running. - You can view all installed project types by unchecking the - Show Project Types and toolchains only if they are supported on the platform box. -

-

- Some project types (Executable and Makefile, in our case) can contain one or more templates - (marked by disk). If you select template belonging to some project type, project of such type - (executable, in our case) will be created, and additional template-specific source code will - be generated. -

- - -

- Related concepts -
- CDT Projects
- Project file views -

-

Related tasks -
-Working with C/C++ project files

- - -IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_referenced_configs.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_referenced_configs.htm deleted file mode 100644 index f1b9d93d960..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_referenced_configs.htm +++ /dev/null @@ -1,53 +0,0 @@ - - - - - - -Project References - - - - - -

Project References

- -

Project References are a powerful way of expressing dependencies between your CDT projects, allowing you to -write modular software built with CDT's managedbuild. - -

Two main pages control project references: -

    -
  • -Project References Page under
    -Right click > Properties > C/C++ General > Paths and Symbols -
  • -
  • -Export Settings Page under
    -Right click > Properties > C/C++ General > Export Settings
    -If this page is missing, enable it under Window > Preferences > C/C++ > Property Page Settings -
  • -
- -

-The export settings page gives you fine grained control of which paths, preprocessor symbols, and -library files are exported by a given project's configuration. -

-When another project's configuration, in the workspace, references a configuration with exported settings, those settings -are automatically propagated into the dependent project configuration. CDT also ensures that referenced projects are -built as a prerequisite for building dependent projects. -

-This functionality prevents you from needing to maintain and update the build settings manually between all the -dependent projects in your workspace. Simply configure the exported settings, setup the references, and the settings -are propagated and kept in sync for you. - -

Related concepts -
- -

Related reference -
-Project References Page
-Export Settings Page - -

- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_rename.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_rename.htm deleted file mode 100644 index 3e613571405..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_proj_rename.htm +++ /dev/null @@ -1,53 +0,0 @@ - - - - - - -Renaming a project - - - - - -

Renaming a project

- -

You can rename a project, and have all references changed using the refactoring engine.

- -

To rename a project:

- -
    -
  1. In the C/C++ Projects view, right-click a project, and select Rename. -
    -
    - Project Properties menu highlighting Rename -
    -
    -
  2. -
  3. The edit box is activated for the selected project. Type a new name. -
  4. -
  5. Press Enter.
  6. -
- -

Note: -Renaming a project causes it to be re-indexed. -This can take a significant amount of time for very large projects. The new name must be unique within the workspace. -

- -

Related concepts -
- CDT Projects
- Project file views

-

Related tasks -
-Working with C/C++ project files

-

Related reference -
-Project properties

- - -QNX Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_prvw_hide_files.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_prvw_hide_files.htm deleted file mode 100644 index a83e4c9b6ef..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_prvw_hide_files.htm +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - -Hiding files by type in the C/C++ Projects view - - - - - -

Hiding files by type in the C/C++ Projects view

- -

You can hide files by type that you do not want to see in the C/C++ Projects -view.

-

To hide files by type:

-
    -
  1. In the C/C++ Projects view, click the Menu iconC/C++ Projects view, Menu.
    - Filters from Projects View
  2. -
  3. Click Filters.
    - C Element Filters Window
  4. -
  5. Select the file types that you want to hide.
  6. -
  7. Click OK. -

    The C/C++ Projects view refreshes automatically.

- -

Related concepts -
-CDT Projects
-Project file views -

-

Related tasks -
-Displaying C/C++ file components in the -C/C++ Projects view
-Hiding files by type in the C/C++ Projects -view

-

Related reference -
-Views

-

-IBM Copyright Statement -

- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_refactoring.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_refactoring.htm deleted file mode 100644 index 8852cb5de93..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_refactoring.htm +++ /dev/null @@ -1,26 +0,0 @@ - - - - - - -Refactoring - - - - - -

Refactoring

- -

The following topics provide information about refactoring:

- Rename Refactoring
- Toggle Function Refactoring
- - -

- -IBM Copyright Statement - -

- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_registers.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_registers.htm deleted file mode 100644 index d4a6052b4de..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_registers.htm +++ /dev/null @@ -1,55 +0,0 @@ - - - - - - - - -Working with registers - - - - - -

Working with registers

- -

You can modify registers in the Registers view.

- -

To modify Registers:

- -
    -
  1. In the Registers view, right-click a register and click Change Register Value.
  2. -
  3. Type a new value.
  4. -
  5. Press Enter.
    -

    The Register value is highlighted in red whether or not it was changed.

  6. -
- -

To change the number system displayed:

- -

You can change the number system used to display register values.

- -
    -
  1. In the Registers view, right-click a register, and select Format.
  2. -
  3. Type a new value.
  4. -
  5. Do one of the following: -
    • Click Default.
    • Click Decimal.
    • Click - Hexadecimal.
    • Click Octal.
    • Click Binary.
    -
  6. -
- -

Related concepts -
-C/C++ Development perspective
-

-

Related tasks -
-Debugging

-

Related reference -
-Debug views

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_rem_wtch_brk.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_rem_wtch_brk.htm deleted file mode 100644 index 6eace510a5a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_rem_wtch_brk.htm +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - - -Removing breakpoints and watchpoints - - - - - -

Removing breakpoints and watchpoints

- -

When you remove a breakpoint or watchpoint, the corresponding icon is removed from the marker bar -where it was inserted and the Breakpoints view.

- -

To remove breakpoints or watchpoints:

-
    -
  1. In the Breakpoints view, do one of the following: -
      -
    • Select the breakpoints and watchpoints you want to remove.
    • -
    • Right-click, click Select All.
    • -
    -
  2. -
  3. In the Breakpoints view, right-click and select - Remove or Remove All.
  4. -
- -

For more information on marker bar icons, see Workbench User Guide > -Reference > User interface information > Icons and buttons > Editor area -marker bar.

- -

Related concepts -
-C/C++ Development perspective
-

-

Related tasks -
-Using breakpoints and watchpoints

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_rename.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_rename.htm deleted file mode 100644 index 2f96212125a..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_rename.htm +++ /dev/null @@ -1,55 +0,0 @@ - - - - - -Rename Refactoring - - - -
-

Rename Refactoring

-

- Use the Refactor > Rename command to rename - variables, functions, classes, methods, fields or typedefs. -

-

- In an Editor window, select an item and run Refactor - > Rename... from the context menu. -

-

- Example of inline renaming. -

-

All uses of the name are highlighted, and updated in real time - as you type. If you want to view the preview, or change any options, - simply click on the triangle, or press the keyboard shortcut again. - Otherwise, the options are the same as the last time a rename - refactoring was done.

-

When you hit Enter, all the item's declarations, definitions - and references will be changed to use the new name. The standard Undo - command can be used to revert the changes, if necessary.

-

The options can be set using a dialog box, where you can - specify the new name, and set various options affecting how hard to - look for uses of the name that should be updated. From there you can - also view the Preview of the changes that will be made by the - refactoring.

-

- Rename dialog box -

-

Items to be renamed can also be selected from the Project - Explorer window, although inline renaming is not available in this - case, so the dialog box comes up immediately.

-

- Project Explorer context menu Refactor > Rename command -

-

- Related reference
Refactor Menu actions -

- IBM Copyright Statement -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_arg.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_arg.htm deleted file mode 100644 index 3b520e644d5..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_arg.htm +++ /dev/null @@ -1,61 +0,0 @@ - - - - - - -Specifying execution arguments - - - - - -

Specifying execution arguments

- -

You can specify the execution arguments that an application uses and the working directory -for a run configuration.

- -

To specify execution arguments:

- -
    -
  1. In the C/C++ Projects view, select a project.
  2. -
  3. Click Run > Run or Run > Debug.
  4. -
  5. In the Configurations box, expand C/C++ Local.
  6. -
  7. Select a run or debug configuration.
  8. -
  9. Click the Arguments tab.
    - Run Arguments window - - -
  10. -
  11. In the C/C++ Program Arguments box, type the arguments that you - want to pass to the command line.
  12. -
  13. To specify a local directory or a different project in your workspace, - clear the Use default working directory check box.
  14. -
  15. Click Run or do the following, as required: -
- -

Related concepts -
-C/C++ projects
-Project file views

-

Related tasks -
-Creating or editing a run configuration

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_com.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_com.htm deleted file mode 100644 index 2e5f7f8e910..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_com.htm +++ /dev/null @@ -1,65 +0,0 @@ - - - - - - -Specifying the location of the run configuration - - - - - -

Specifying the location of the run configuration

- -

When you create a run configuration, it is saved with the extension .launch in org.eclipse.debug.core. -You can specify an alternate location in which to store your run configuration. You can -also specify how you access it and what -perspective to open when running an application.

-

To specify the location of a run configuration:

- -
    -
  1. In the C/C++ Projects view, select a project.
  2. -
  3. Click Run > Run or Run > Debug.
  4. -
  5. In the Configurations box, expand C/C++ Local.
  6. -
  7. Click the Common tab.
    - Run Common window -
  8. -
  9. To save .launch to a project in your workspace, and to be able - to commit it to CVS, click Shared.
  10. -
  11. In the Folder Selection window, select a project, and click OK.
    - Run Common Folder Selection window -
  12. -
  13. To specify which perspective opens when you run, select a perspective - from the Run mode list.
  14. -
  15. To specify which perspective opens when you run, select a perspective - from the Debug mode list.
  16. -
  17. Click Run, or do the following, as required: - -
- -

Related concepts -
-C/C++ Projects
-Project file views

-

Related tasks -
-Creating or editing a run configuration

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_config.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_config.htm deleted file mode 100644 index a459a051891..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_config.htm +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - -Selecting a run or debug configuration - - - - - -

Selecting a run or debug configuration

- -

You can select an existing run configuration to use to run your program.

- -

To select a run configuration:

- -
    -
  1. In the C/C++ Projects view, select a project.
  2. -
  3. Click Run > Run or Run > Debug.
  4. -
  5. In the Configurations box, expand C/C++ Local.
  6. -
  7. Select a run or debug configuration.
    - Run Configuration Window
  8. -
  9. Select a configuration from the Configurations list.
  10. -
  11. Click Run or Debug.
  12. -
- -

Related concepts -
-C/C++ Projects
-Project file views

-

Related tasks -
-Creating or editing a run configuration

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_dbg.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_dbg.htm deleted file mode 100644 index bb8cb32027d..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_dbg.htm +++ /dev/null @@ -1,68 +0,0 @@ - - - - - - -Defining debug settings - - - - - - -

Defining debug settings

- -

Select a debugger to use when debugging an application.

- -

To select a debugger:

- -
    -
  1. In the C/C++ Projects view, select a project.
  2. -
  3. Click Run > Run or Run > Debug.
  4. -
  5. In the Configurations box, expand C/C++ Local.
  6. -
  7. Select a run or debug configuration.
  8. -
  9. Click the Debugger tab..
    - Run Debugger window -
  10. -
  11. Select a debugger from the Debugger list.
  12. -
  13. To let your program run until you interrupt it manually, or until it - hits a breakpoint, clear the Stop at main() on startup check box .
  14. -
  15. Specify debug options in the Debugger Options box.
  16. -
  17. Click Run or do the following, as required: -
- -

Related concepts -
-C/C++ Projects
-Project file views
-Debug overview
-Debug information

-

Related tasks -
-Creating or editing a run configuration

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_env.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_env.htm deleted file mode 100644 index a6c1abebce7..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_env.htm +++ /dev/null @@ -1,65 +0,0 @@ - - - - - - -Setting environment variables - - - - - -

Setting environment variables

- -

You can set the environment variables and values to use when an application -runs.

- -

To set environment variables:

- -
    -
  1. In the C/C++ Projects view, select a project.
  2. -
  3. Click Run > Run or Run > Debug.
  4. -
  5. In the Configurations box, expand C/C++ Local.
  6. -
  7. Select a run or debug configuration.
  8. -
  9. Click the Environment tab..
    - Run Environment Window -
  10. -
  11. Do one of the following: -
      -
    • To create a new environment variable, click New.
    • -
    • To import an environment variable, click Import.
    • -
    • To edit an existing environment variable, select an item from the list and click Edit.
    • -
    • To remove an existing environment variable, select an item from the list and click Remove.
    • -
    -
  12. Type a name in the Name box.
  13. -
  14. Type a value in the Value box.
  15. -
  16. Click Run or do the following, as required: - -
- -

Related concepts -
-C/C++ Projects
-Project file views

-

Related tasks -
-Creating or editing a run configuration

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_main.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_main.htm deleted file mode 100644 index cdb734c443c..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_main.htm +++ /dev/null @@ -1,65 +0,0 @@ - - - - - - -Selecting an application to run or debug - - - - - - -

Selecting an application to run or debug

- -

You need to specify the project or program that you want to run or debug for -this run configuration.

- -

To select an application to run:

- -
    -
  1. In the C/C++ Projects view, select a project.
  2. -
  3. Click Run > Run or Run > Debug.
  4. -
  5. In the Configurations box, expand C/C++ Local.
  6. -
  7. Select a run or debug configuration.
  8. -
  9. Click the Main tab.
    - Run Configuration Window -
  10. -
  11. Do the following: -
    • In the Name box, type a descriptive name for this new a - descriptive name for this launch configuration.
    • -
    • In the Project box, type the name of the project containing - the application that you want to run.
    • -
    • In the C/C++ Application box, type the name of the executable - that you want to run.
    • -
  12. -
  13. Click Run or do the following, as required: -
- -

Related concepts -
-C/C++ projects
-Project file views

-

Related tasks -
-Creating or editing a run configuration

-

Related reference
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_source.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_source.htm deleted file mode 100644 index 2cef12267d6..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_run_source.htm +++ /dev/null @@ -1,53 +0,0 @@ - - - - - - -Specifying the location of source files - - - - - - -

Specifying the location of source files

- -

You can specify the locations of source files used when debugging a C or C++ -application. By default, this information is taken from your project.

- -

To specify the locations of source files:

- -
    -
  1. In the C/C++ Projects view, select a project.
  2. -
  3. Click Run > Run or Run > Debug.
  4. -
  5. In the Configurations box, expand C/C++ Local.
  6. -
  7. Select a run or debug configuration.
  8. -
  9. Click the Source tab.
  10. -
  11. To add a source container to the source locations list: -
      -
    • Click Add to open the Add Source dialog box
    • -
    • Select a container type.
    • -
    • Select a container from the list of available containers of the selected type.
    • -
    -
  12. You can remove or modify a source container by selecting a container and clicking the Remove or Edit button.
  13. -
  14. You can change the order of source containers by selecting a container and clicking - the Up or Down buttons.
  15. -
  16. To search for duplications in your source locations select the Search for duplicate source files on the path checkbox.
  17. -
- -

Related concepts -
-C/C++ Projects
-Project file views

-

Related tasks -
-Creating or editing a run configuration

-

Related reference -
-Run and Debug dialog box

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_sd.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_sd.htm deleted file mode 100644 index d48aa936b15..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_sd.htm +++ /dev/null @@ -1,59 +0,0 @@ - - - - - - - - -Setting up include paths and macros for C/C++ indexer - - - - -
-

Setting up include paths and macros for C/C++ indexer

- -

-The Stand-alone Debugger supports a number of actions based on the application's code such as code highlighting, navigation, content assist and static analysis. -Normally, C/C++ projects have to be configured to enjoy those features due to the fact that most real life C/C++ projects heavily depend on code outside of the project itself, -such as system headers or third party libraries. The C/C++ indexer needs to process those to provide an accurate index. -

- -

The Stand-alone Debugger will try to discover include paths and preprocessor symbols automatically. This process is known as Scanner Discovery or Autodiscovery. -This discovery of symbols is twofold. -The first method is that the Stand-alone Debugger will try to detect built-in compiler symbols and include paths running the compiler with special options and parse the output. -Another method that the Stand-alone Debugger employs is to analyze the output generated from a Makefile build. Since the -Stand-alone Debugger does not contain build support, this output must be saved externally and passed to the debugger either -on the command line using the -b option or else by specifying the build log using the File > New Executable... -dialog. Often, include paths are supplied to the compiler with -I options, and macros with -D options. -That relies on verbose build output of your build where all these options are actually printed by make. -

- -

-Scanner Discovery uses Language Settings Providers to find include paths and preprocessor symbols. -Language Settings Providers can be configured on project properties page "Preprocessor Include Paths, Macros, etc.", Providers tab for a configuration -and on preference page C/C++ Preferences: Scanner Discovery for shared providers. -

-

-If information retrieved by auto-discovery is insufficient a user can inspect discovered entries and enter additional include paths and macros manually -on the property page "Preprocessor Include Paths, Macros, etc.", Entries tab. -

- - -

Related concepts
-Scanner Discovery
-C/C++ Indexer
-

- -

Related tasks
-Searching for C/C++ elements

-

- -

Related reference
-C/C++ Project properties: Preprocessor Include Paths, Macros, etc.
-

- -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_search.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_search.htm deleted file mode 100644 index 99c40072734..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_search.htm +++ /dev/null @@ -1,150 +0,0 @@ - - - - - - -Searching for C/C++ elements - - - - - -

Searching for C/C++ elements

- -

The Stand-alone Debugger provides the ability to search through the source code of your -application. To do this, the Debugger indexes the source code using the include paths and -macros used to build the application. If your application is built using the default include -paths and no additional user-defined flags, then there is nothing you need to do to make the -search work accurately. In the case where your application has additional include paths and -user-defined flags specified in the build, you need to either use the -g3 flag to include macro -information or else you need to provide the Stand-alone Debugger with a copy of the build log. -The build log can be provided on the command line using the -b option or via -the File > New Executable... dialog. If you do not set this up properly, -various operations such as searching, type hierarchy, and hover display may be inaccurate.

- -

See C/C++ search, for more information on:

- -
    -
  • What you can search for
  • -
  • How to limit your search
  • -
  • How to use wildcard characters in your search
  • -
  • Syntax examples
  • -
- - - -

Performing a C/C++ Search can be done in a number of different ways but regardless of the manner chosen the same information must be provided to C/C++ Search.

- -The info required to do a search is: - - - - - - - - - - - - - - - - - - - - - - -
OptionExplanation
Search stringthis is the name of the element you are looking for. See C/C++ search for more information on how to specify wildcard searches and how to further refine your searches by using fully qualified names
Search For this is the element type that you wish to search for. You can also select to search on 'Any Element' which will perform the search on a combination of all elements
Limit Tothis allows you to limit your search to declarations, definitions or references. You can also select 'All Occurrences' which will search for declarations, definitions and references that match the element
Scopethis allows the user to limit the scope of the search. The three available scopes are: - - - - - - - - - - - - - - - - - -
Workspacethis searches all of the open projects in the workspace
Selected Resourcesthis option becomes enabled whenever something is selected in one of the following views in the C/C++ perspective: -
    -
  • C/C++ Projects
  • -
  • Project Explorer
  • -
  • Search
  • -
  • Outline
  • -
-

The scope will be limited to whatever element is selected in the view.

-
Working Setworking sets can be selected and created
-
- -

There are 3 main ways for initiating a C/C++ search: -

    -
  • Using the C/C++ Search dialog
  • -
  • Selecting an element in the Editor view
  • -
  • Selecting an element in the C/C++ Projects view or Selecting an element from the Outline view
  • -
-
-
- -

Using the C/C++ Search dialog

-

Search dialog box

- -
    -
  1. Enter the search string in the Search String field (optional mark it case sensitive).
    - Note: that previous search queries (from the same work session) are remembered and can be accessed via the drop down list.
  2. -
  3. Select the Search For element.
  4. -
  5. Select the Limit To.
  6. -
  7. Select the Scope.
  8. -
  9. Press Search.
  10. -
-

Results are displayed in the Search view.

- - -

Selecting an element in the Editor view

-
    -
  1. Select the desired element in the editor.
  2. -
  3. Right click and select All Declarations or All References and the scope you wish to search.
  4. -
-

Results are displayed in the Search view.

- -

Selecting an element in C/C++ Projects or Outline View

- -
    -
  1. Select the desired element in the tree.
  2. -
  3. Right click and select All Declarations or All References and the scope you wish to search.
  4. -
-

Results are displayed in the Search view.

- - -

Related concepts -
-C/C++ search
-C/C++ Indexer
-C/C++ Projects
-Open Declaration
-

- -

Related tasks
-Selection Searching for C/C++ elements
-Navigate to C/C++ declarations
-

- -

Related reference -
-C/C++ search page, Search dialog box

-
-IBM Copyright Statement -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_sel_search.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_sel_search.htm deleted file mode 100644 index 0b2a11c3018..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_sel_search.htm +++ /dev/null @@ -1,64 +0,0 @@ - - - - - - -Selection Searching for C/C++ elements - - - - - -

Selection Searching for C/C++ elements

- -

It is recommended that you perform searches on successfully compiled -programs to ensure the accuracy of search results. It is important to familiarize yourself with the correct search syntax -to use to complete an effective search. It is also important to ensure that -include paths and symbols are correctly defined. For more information, see -Setting up include paths and macros for C/C++ indexer.

- -

See C/C++ search, for more information on:

- -
    -
  • What you can search for
  • -
  • How to limit your search
  • -
  • How to use wildcard characters in your search
  • -
  • Syntax examples
  • -
- -

To search for an element in your project:

- -
    -
  1. Highlight the element you want to search.
  2. -
  3. Right click and select Search For from the context menu.
    - Editor View showing Selection Search options
  4. -
  5. Select All Declarations or All References.
  6. -
  7. Select Workspace or Working Set....
  8. -
  9. The search results will appear in the Search View
    - Search View Selection Search options
  10. -
-

For more information, see: -

    -
  • Workbench User Guide > Concepts > Views > Search view
  • -
  • Workbench User Guide > Tasks > Navigating and finding resources
  • -
- -

Related concepts -
-C/C++ search
-C/C++ Projects
-Open Declaration
-

-

Related tasks
-Searching for C/C++ elements
-Navigate to C/C++ declarations
-

-

Related reference
-C/C++ search page, Search dialog box

-

 

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_set_src_fold.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_set_src_fold.htm deleted file mode 100644 index d70f6e4d9e8..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_set_src_fold.htm +++ /dev/null @@ -1,64 +0,0 @@ - - - - - - Setting Source Folders - - - -

Setting Source Folders

-

Note that source folders can only be currently used with Standard -Make projects. Managed Make projects treat the entire project as a -source folder.

-

Source folders are a way to cut down on a project's indexing scope. -You can mark the folders that are part of your day to day work or part -of a subsystem that you work on. All files inside source folders will -be indexed and are, thus, searchable. Note that any files pulled in by -a file inside a source folder will also be indexed.

-

Set source folder

-

To setup source folders: -

-
    -
  1. Right click on the project and select Properties > C/C++ -Project Paths
  2. -
  3. Click on the Source tab
    -By default the entire project is a source folder, which means -everything will be indexed. This is reasonable for smaller projects but -definitely not recommended for large projects.
  4. -
  5. Click Add folder to add the folders. A dialog will -explain exclusion filters have been added to nesting folders. You will -see that the folder you added will be excluded from the project folder -(in order to avoid including a folder twice). Repeat until all the -folders have been added.
    - Note: Don't forget to remove the project folder (which -appears by default) otherwise everything will be indexed.
  6. -
  7. Click OK. Your view in C/C++ projects will now change. -You should see your source folders designated with a "C" and all other -source and header files icons that are in a non-source folder will -change to a "hollow" C or H.
  8. -
-

Related concepts -
-C/C++ search
-C/C++ Indexer
-C/C++ Indexer Progress -Bar

-

Related tasks
-Selection Searching for C/C++ -elements
-

-

Related reference -
-C/C++ search page, Search -dialog box -
-C/C++ Project Properties, Indexer -

-

 

-IBM Copyright Statement -
- diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_shift_code.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_shift_code.htm deleted file mode 100644 index 840c8ec11b6..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_shift_code.htm +++ /dev/null @@ -1,46 +0,0 @@ - - - - - - -Shifting lines of code to the right or left - - - - - -

Shifting lines of code to the right or left

- -

You can shift lines of code to the left or right in the C/C++ editor. You can -change the tab width in the C/C++ editor preferences window. For more -information, see Customizing the C/C++ -editor.

- -

To shift lines of code to the right or left:

- -
    -
  1. In the C/C++ editor, select the full length of the lines that you want to shift.
  2. -
  3. Do one of the following: -
    • To move the text to the right, press Tab.
    • -
    • To move the text to the right, click Edit > Shift Right.
    • -
    • To move the text to the left, press Shift+Tab.
    • -
    • To move the text to the left, click Edit > Shift Left.
    • -
    -
  4. -
- -

Related concepts -
- Code entry

-

Related tasks -
-Customizing the C/C++ editor

-

Related reference -
-C/C++ editor preferences

-IBM Copyright Statement - -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_show_proj_files.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_show_proj_files.htm deleted file mode 100644 index a11845cf30d..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_show_proj_files.htm +++ /dev/null @@ -1,54 +0,0 @@ - - - - - - -Displaying C/C++ file components in the C/C++ Projects view - - - - - -

Displaying C/C++ file components in the C/C++ Projects view

- -

File components are displayed in the C/C++ Projects view and in the Outline -view. You can display or hide all file components in the C/C++ Projects view.

- -

To display file components

- -
    -
  1. Click Window > Preferences.
  2. -
  3. In the Preferences dialog box, select C/C++ > Appearance from the list.
    - Screen Capture of the C/C++ Appearance Preferences dialog box
  4. -
  5. Select the Show translation unit members check box.
  6. -
  7. Click OK.
  8. -
  9. In the C/C++ Projects view, double-click a file component.
    - The component is highlighted in the C/C++ editor.
    - C/C++ Projects view with file components
  10. -
- -

The C/C++ Projects view can also be filtered to show certain types of file -components. For more information, see Hiding -files by type in the C/C++ Projects view.

- -

Related concepts -
-CDT Projects
-Project file views -

-

Related tasks -
-Hiding files by type in the C/C++ Projects -view
-Searching for C/C++ elements
-Navigate to C/C++ declarations
-

-

Related reference -
-C/C++ editor preferences

-
-IBM Copyright Statement -
- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_standalone_startup.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_standalone_startup.htm deleted file mode 100644 index beb53fc2789..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_standalone_startup.htm +++ /dev/null @@ -1,118 +0,0 @@ - - - - - - - Starting The Debugger - - - -
- -

Starting The Debugger

- -

The debugger is started from the command-line using the cdtdebug.sh script or using the cdtdebug executable. -Your installation will contain either the script or the executable depending on which package you have downloaded. -The script contains the command-line needed to start Eclipse and to pass appropriate -parameters at start-up. The following are the command-line options supported: - -

-a [pid]

-

This option specifies that you want to attach and debug an existing executable that is running on your system. -If no pid is specified or an invalid pid is specified, the option will bring up a dialog which contains a list of current executables running and you may choose the -executable(s) you wish to attach to. The dialog will also give you the option of starting a new executable, if desired, but you -cannot specify a build log using this method. When used at the same as the -r option, the pid argument is ignored. - -

-b <build log>

-

This option specifies an optional build log to use for indexing the source. The build log -is simply the output of a makefile build where the options used to compile the various source files -are displayed. The indexer uses these options to figure out what flags and include paths were used -and thus can properly parse the code to match the executable. The parsed tree is used to navigate -within the code to search for C/C++ elements or to calculate a call hierarchy. If this log is -not provided, the Stand-alone Debugger has only the compiler built-ins and default include paths -to use which means it may not search properly.

- -

-c <core file>

-

This option specifies a path to a core file to debug for an executable. The core file should have been created -by the specified executable. The executable is specified using the -e option, which is later described. -If the core file is invalid or no valid executable is also specified, a dialog will be brought up to allow -you to enter the required information.

- -

-e <executable> [args*]

-

This option specifies a path to an executable to be debugged. If the -c option is previously specified, -the executable will be used in conjunction with the core file specified by the -c option. If the -c option is -not used, then any additional arguments on the command line will be passed to the main method -of the C/C++ application when it is debugged. If you do not specify any of the -a, -c, or -e options (e.g. starting up the Stand-alone Debugger -with no arguments), the last valid executable used invoking the debugger (if this isn't the first invocation) -will be offered to you via a dialog, which includes the original program arguments and build log. -You then have the choice of simply hitting the OK button to debug the last executable again or to change the arguments -as desired. If the executable location you specify is invalid or no executable is specified and no previous executable exists, -a dialog will be brought up to allow you to enter the required information. The dialog will be appropriate to whether -you have selected to debug a core file (-c specified) or not.

- -

-r <addr:port>

-

This option specified a hostname or IP address and and IP port to connect to to perform remote debugging. -The gdbserver must be running on the target and waiting for a connection on the specified port. -This option can be used at the same time as the -a option. In such a case -a Remote-Attach session will be started allowing the user to attach to -different processes on the remote target. The user will need to press -the 'connect' button or use the context-menu of the Debug view to choose one or more processes -to attach to. In this case the -e flag is optional, and when not specified, -a dialog will be used instead to prompt for the binary's location. -This option, when used without -a, will trigger a manual Remote debugging session towards -a single, pre-selected binary and therefore requires the use of the -e option -to specify the location of the binary on the local machine that matches the one on the -remote target.

- - -

Automated Set-up

- -

As mentioned, the Stand-alone Debugger will initialize Eclipse objects on your behalf on -start-up so you can immediately start debugging. For starters, the executable you specify -is imported on your behalf into an Eclipse -C/C++ project within the Workspace. An Eclipse project is a virtual container object that contains folders, files, etc. and has a particular -nature. Folders and files may be virtual and may actually link to objects outside of the workspace. In this particular -case, the debug info of the executable specified is used to determine the location of the source files. Each source -file is imported in the project, virtually, via a link. This is done so that the C/C++ indexer, which usually works on -a project being developed within Eclipse, has access to all code when it is parsing. Usually, the name of the default C/C++ project -will be Executables, the default project for importing executables into the CDT via the Executables view. -

The nature of a project determines what menus, actions, and views are valid for that project. -Menus, actions, and views that are not valid are not made visible. -This helps to remove the clutter of all contributed plug-ins to what is pertinent to the task at hand -(e.g. if the C/C++ and Java IDE plug-ins are both present, one does not want to see Java tasks when -working on a C/C++ project). Many of the plug-ins being used in the Stand-alone debugger only -work on C/C++ projects anyway.

-

Another Eclipse concept is the Perspective. An Eclipse perspective defines the set of views and how they are placed in the -main Eclipse Window. A perspective will have a default layout associated with it which can be modified and saved by the end-user for -future reference (e.g. adding or removing -views). For the purposes of debugging, -the Debug Perspective is the appropriate perspective to use and therefore the Stand-alone Debugger opens the Debug Perspective automatically for -you. The perspective has all the various views needed to debug your program.

-

To debug an executable, one needs to launch it via the debugger and to provide options both for the executable and the -debugger (in this case, GDB). All the information required to launch and debug is stored -in an Eclipse object known as a Launch Configuration. Various plug-ins can contribute different forms of Launch Configuration -which can in turn provide UI elements for settings. In the case of the Stand-alone Debugger, debugging an executable -results in the automatic creation of a C/C++ Local Application Launch configuration. This type of launch is meant -for launching an executable that is local to the current host. Additional parameters are available via the Launch Configuration -View such as gdb settings (e.g. gdb path, reverse debugging) and environment variables.

- -

Initial Debugger Layout

- -

Stand-alone Debugger

- -

Related concepts
-CDT Overview
-C/C++ Projects
-C/C++ Perspectives
-C/C++ Indexer
-C/C++ Search

-

Related reference -
-Views
-Intel Copyright Statement - -

- - - diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_toggle.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_toggle.htm deleted file mode 100644 index a62fd373ff8..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_toggle.htm +++ /dev/null @@ -1,43 +0,0 @@ - - - - - -Toggle Function Definition Refactoring - - - -
-

Toggle Function Definition

-

- Use the Refactor > Toggle Function Definition - command to toggle the location where a function is defined. -

-

- In an Editor window, place the cursor inside a function declaration - or definition, then run Refactor > Toggle - Function Definition from the context menu. Any cursor position - between the first and the last characters of the function definition - (but not including comments preceding the function) will cause that - function to be selected for the refactoring. -

-

- -

-

This refactoring switches a function definition from a header - file to a correspondingly-named implementation file. If the necessary - file does not exist, it will be created (after a confirmation - dialog).

-

- -

-

For methods, it can also switch the method from being defined - within its parent class declaration to being defined using an inline - definition in the same header file.

-

- -

- IBM Copyright Statement -
- - diff --git a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_variables.htm b/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_variables.htm deleted file mode 100644 index 0302356be57..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/tasks/cdt_t_variables.htm +++ /dev/null @@ -1,62 +0,0 @@ - - - - - - - - -Working with variables - - - - - -

Working with variables

- -

During a debug session, you can display variable types, and change -or disable variable values.

- -

To display variable type names:

- -
    -
  • In Variables view, click the Show Type Names toggle button.
  • -
- -

To change a variable value while debugging:

- -

During a debug, you can change the value of a variable to test how your -program handles a particular value or to speed through a loop.

- -
    -
  1. In Variables view, right-click a variable, and select Change Value.
  2. -
  3. Type a value.
  4. -
- -

To disable a variable value while debugging:

- -

You can disable a variable so that the debugger does not read the variable's -value from the target. This is useful if the target is very sensitive or the -variable is specified as volatile.

- -
    -
  • In Variables view, right-click a variable, and select Disable.
  • -
- -

Related concepts -
-C/C++ Development perspective
-

-

Related tasks -
-Debugging

-

Related reference -
-Debug views

- -

-IBM Copyright Statement - -

- - \ No newline at end of file diff --git a/debug/org.eclipse.cdt.debug.application.doc/testToc.xml b/debug/org.eclipse.cdt.debug.application.doc/testToc.xml deleted file mode 100644 index 82897fefaeb..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/testToc.xml +++ /dev/null @@ -1,6 +0,0 @@ - - - - - - diff --git a/debug/org.eclipse.cdt.debug.application.doc/toc.xml b/debug/org.eclipse.cdt.debug.application.doc/toc.xml deleted file mode 100644 index c3c5983971f..00000000000 --- a/debug/org.eclipse.cdt.debug.application.doc/toc.xml +++ /dev/null @@ -1,224 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/debug/org.eclipse.cdt.debug.application.product/README b/debug/org.eclipse.cdt.debug.application.product/README index a00f2412d20..0439252fa71 100644 --- a/debug/org.eclipse.cdt.debug.application.product/README +++ b/debug/org.eclipse.cdt.debug.application.product/README @@ -1,5 +1,5 @@ This product is based on the CDT Stand-alone Debugger application found in -org.eclipse.cdt.debug.application. This product can be downloaded on its own, without the rest of +org.eclipse.cdt.debug.application. This product can be built on its own, without the rest of the C/C++ package which makes it much smaller. It also makes it easier to use because the user only has to launch the executable after extracting the product. For example the product can be launched by simply running: ./cdtdebug -e ~/myproject/bin/a.out arg1 arg2 diff --git a/debug/org.eclipse.cdt.debug.application.product/debug.product b/debug/org.eclipse.cdt.debug.application.product/debug.product index ba8cdd69975..642acb19953 100644 --- a/debug/org.eclipse.cdt.debug.application.product/debug.product +++ b/debug/org.eclipse.cdt.debug.application.product/debug.product @@ -2,7 +2,7 @@ - + @@ -26,12 +26,23 @@ -data @noDefault - -Xms100m -Xmx512m -Dosgi.requiredJavaVersion=17 - - -Xms100m -Xmx512m -XstartOnFirstThread -Dosgi.requiredJavaVersion=17 -Dorg.eclipse.swt.internal.carbon.smallFonts + -Dosgi.requiredJavaVersion=21 +-Dosgi.dataAreaRequiresExplicitInit=true +-Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=false +-Declipse.e4.inject.javax.warning=false +-Dorg.slf4j.simpleLogger.defaultLogLevel=off +-Dsun.java.command=Eclipse +-Xms100m +-Xmx512m +-XX:+UseG1GC +-XX:+UseStringDeduplication +--add-modules=ALL-SYSTEM +-Djava.security.manager=allow + + -XstartOnFirstThread +-Dorg.eclipse.swt.internal.carbon.smallFonts +-Xdock:icon=../Resources/Eclipse.icns - -Xms100m -Xmx512m -Dosgi.requiredJavaVersion=17 - @@ -46,423 +57,191 @@ - org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-17 - org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-17 - org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-17 + org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-21 + org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-21 + org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-21 http://eclipse.org/legal/epl/notice.php Eclipse Foundation Software User Agreement -April 9, 2014 + +November 22, 2017 Usage Of Content -THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR -OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT"). -USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS -AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR -NOTICES INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU -AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT -AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS -OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE -TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS -OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED -BELOW, THEN YOU MAY NOT USE THE CONTENT. +THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION +AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT"). USE OF +THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE +TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED +BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED +BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE +AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW. IF YOU DO NOT AGREE TO THE +TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS OF ANY +APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU +MAY NOT USE THE CONTENT. Applicable Licenses -Unless otherwise indicated, all Content made available by the -Eclipse Foundation is provided to you under the terms and conditions of -the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is -provided with this Content and is also available at https://www.eclipse.org/legal/epl-2.0/. -For purposes of the EPL, "Program" will mean the Content. - -Content includes, but is not limited to, source code, object code, -documentation and other files maintained in the Eclipse Foundation source code -repository ("Repository") in software modules ("Modules") and made available -as downloadable archives ("Downloads"). - - - Content may be structured and packaged into modules to facilitate delivering, - extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"), - plug-in fragments ("Fragments"), and features ("Features"). - - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive) - in a directory named "plugins". - - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material. - Each Feature may be packaged as a sub-directory in a directory named "features". - Within a Feature, files named "feature.xml" may contain a list of the names and version - numbers of the Plug-ins and/or Fragments associated with that Feature. - - Features may also include other Features ("Included Features"). Within a Feature, files - named "feature.xml" may contain a list of the names and version numbers of Included Features. - -The terms and conditions governing Plug-ins and Fragments should be -contained in files named "about.html" ("Abouts"). The terms and -conditions governing Features and Included Features should be contained -in files named "license.html" ("Feature Licenses"). Abouts and Feature -Licenses may be located in any directory of a Download or Module -including, but not limited to the following locations: - - - The top-level (root) directory - - Plug-in and Fragment directories - - Inside Plug-ins and Fragments packaged as JARs - - Sub-directories of the directory named "src" of certain Plug-ins - - Feature directories - -Note: if a Feature made available by the Eclipse Foundation is installed using the -Provisioning Technology (as defined below), you must agree to a license ("Feature -Update License") during the installation process. If the Feature contains -Included Features, the Feature Update License should either provide you -with the terms and conditions governing the Included Features or inform -you where you can locate them. Feature Update Licenses may be found in -the "license" property of files named "feature.properties" found within a Feature. -Such Abouts, Feature Licenses, and Feature Update Licenses contain the -terms and conditions (or references to such terms and conditions) that -govern your use of the associated Content in that directory. - -THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER -TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. -SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO): - - - Eclipse Distribution License Version 1.0 (available at http://www.eclipse.org/licenses/edl-v1.0.html) - - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html) - - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE) - - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0) - - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html) - -IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR -TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License -is provided, please contact the Eclipse Foundation to determine what terms and conditions -govern that particular Content. - +Unless otherwise indicated, all Content made available by the Eclipse Foundation +is provided to you under the terms and conditions of the Eclipse Public License +Version 2.0 ("EPL"). A copy of the EPL is provided with this Content and is also +available at http://www.eclipse.org/legal/epl-2.0. For purposes of the EPL, +"Program" will mean the Content. + +Content includes, but is not limited to, source code, object code, documentation +and other files maintained in the Eclipse Foundation source code repository +("Repository") in software modules ("Modules") and made available as +downloadable archives ("Downloads"). + +- Content may be structured and packaged into modules to facilitate + delivering, extending, and upgrading the Content. Typical modules may + include plug-ins ("Plug-ins"), plug-in fragments ("Fragments"), and + features ("Features"). +- Each Plug-in or Fragment may be packaged as a sub-directory or JAR + (Java™ ARchive) in a directory named "plugins". +- A Feature is a bundle of one or more Plug-ins and/or Fragments and + associated material. Each Feature may be packaged as a sub-directory in a + directory named "features". Within a Feature, files named "feature.xml" may + contain a list of the names and version numbers of the Plug-ins and/or + Fragments associated with that Feature. +- Features may also include other Features ("Included Features"). Within a + Feature, files named "feature.xml" may contain a list of the names and + version numbers of Included Features. + +The terms and conditions governing Plug-ins and Fragments should be contained in +files named "about.html" ("Abouts"). The terms and conditions governing Features +and Included Features should be contained in files named "license.html" +("Feature Licenses"). Abouts and Feature Licenses may be located in any +directory of a Download or Module including, but not limited to the following +locations: + +- The top-level (root) directory +- Plug-in and Fragment directories +- Inside Plug-ins and Fragments packaged as JARs +- Sub-directories of the directory named "src" of certain Plug-ins +- Feature directories + +Note: if a Feature made available by the Eclipse Foundation is installed using +the Provisioning Technology (as defined below), you must agree to a license +("Feature Update License") during the installation process. If the Feature +contains Included Features, the Feature Update License should either provide you +with the terms and conditions governing the Included Features or inform you +where you can locate them. Feature Update Licenses may be found in the "license" +property of files named "feature.properties" found within a Feature. Such +Abouts, Feature Licenses, and Feature Update Licenses contain the terms and +conditions (or references to such terms and conditions) that govern your use of +the associated Content in that directory. + +THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL +OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS. SOME OF THESE +OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO): + +- Eclipse Public License Version 1.0 (available at + http://www.eclipse.org/legal/epl-v10.html) +- Eclipse Distribution License Version 1.0 (available at + http://www.eclipse.org/licenses/edl-v1.0.html) +- Common Public License Version 1.0 (available at + http://www.eclipse.org/legal/cpl-v10.html) +- Apache Software License 1.1 (available at + http://www.apache.org/licenses/LICENSE) +- Apache Software License 2.0 (available at + http://www.apache.org/licenses/LICENSE-2.0) +- Mozilla Public License Version 1.1 (available at + http://www.mozilla.org/MPL/MPL-1.1.html) + +IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO +USE OF THE CONTENT. If no About, Feature License, or Feature Update License is +provided, please contact the Eclipse Foundation to determine what terms and +conditions govern that particular Content. Use of Provisioning Technology -The Eclipse Foundation makes available provisioning software, examples of which include, -but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for -the purpose of allowing users to install software, documentation, information and/or -other materials (collectively "Installable Software"). This capability is provided with -the intent of allowing such users to install, extend and update Eclipse-based products. -Information about packaging Installable Software is available at +The Eclipse Foundation makes available provisioning software, examples of which +include, but are not limited to, p2 and the Eclipse Update Manager +("Provisioning Technology") for the purpose of allowing users to install +software, documentation, information and/or other materials (collectively +"Installable Software"). This capability is provided with the intent of allowing +such users to install, extend and update Eclipse-based products. Information +about packaging Installable Software is available at http://eclipse.org/equinox/p2/repository_packaging.html ("Specification"). -You may use Provisioning Technology to allow other parties to install Installable Software. -You shall be responsible for enabling the applicable license agreements relating to the -Installable Software to be presented to, and accepted by, the users of the Provisioning Technology -in accordance with the Specification. By using Provisioning Technology in such a manner and -making it available in accordance with the Specification, you further acknowledge your -agreement to, and the acquisition of all necessary rights to permit the following: - - 1. A series of actions may occur ("Provisioning Process") in which a user may execute - the Provisioning Technology on a machine ("Target Machine") with the intent of installing, - extending or updating the functionality of an Eclipse-based product. - 2. During the Provisioning Process, the Provisioning Technology may cause third party - Installable Software or a portion thereof to be accessed and copied to the Target Machine. - 3. Pursuant to the Specification, you will provide to the user the terms and conditions that - govern the use of the Installable Software ("Installable Software Agreement") and such - Installable Software Agreement shall be accessed from the Target Machine in accordance - with the Specification. Such Installable Software Agreement must inform the user of the - terms and conditions that govern the Installable Software and must solicit acceptance by - the end user in the manner prescribed in such Installable Software Agreement. Upon such - indication of agreement by the user, the provisioning Technology will complete installation - of the Installable Software. +You may use Provisioning Technology to allow other parties to install +Installable Software. You shall be responsible for enabling the applicable +license agreements relating to the Installable Software to be presented to, and +accepted by, the users of the Provisioning Technology in accordance with the +Specification. By using Provisioning Technology in such a manner and making it +available in accordance with the Specification, you further acknowledge your +agreement to, and the acquisition of all necessary rights to permit the +following: + +1. A series of actions may occur ("Provisioning Process") in which a user may + execute the Provisioning Technology on a machine ("Target Machine") with the + intent of installing, extending or updating the functionality of an + Eclipse-based product. +2. During the Provisioning Process, the Provisioning Technology may cause third + party Installable Software or a portion thereof to be accessed and copied to + the Target Machine. +3. Pursuant to the Specification, you will provide to the user the terms and + conditions that govern the use of the Installable Software ("Installable + Software Agreement") and such Installable Software Agreement shall be + accessed from the Target Machine in accordance with the Specification. Such + Installable Software Agreement must inform the user of the terms and + conditions that govern the Installable Software and must solicit acceptance + by the end user in the manner prescribed in such Installable + Software Agreement. Upon such indication of agreement by the user, the + provisioning Technology will complete installation of the + Installable Software. Cryptography -Content may contain encryption software. The country in which you are -currently may have restrictions on the import, possession, and use, -and/or re-export to another country, of encryption software. BEFORE -using any encryption software, please check the country's laws, -regulations and policies concerning the import, possession, or use, and -re-export of encryption software, to see if this is permitted. +Content may contain encryption software. The country in which you are currently +may have restrictions on the import, possession, and use, and/or re-export to +another country, of encryption software. BEFORE using any encryption software, +please check the country's laws, regulations and policies concerning the import, +possession, or use, and re-export of encryption software, to see if this is +permitted. -Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both. +Java and all Java-based trademarks are trademarks of Oracle Corporation in the +United States, other countries, or both. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + - + - - - - - - - - - - - diff --git a/debug/org.eclipse.cdt.debug.application.product/pom.xml b/debug/org.eclipse.cdt.debug.application.product/pom.xml index e52c78be9ee..83e6e7d89ed 100644 --- a/debug/org.eclipse.cdt.debug.application.product/pom.xml +++ b/debug/org.eclipse.cdt.debug.application.product/pom.xml @@ -33,6 +33,14 @@ + + org.eclipse.tycho + tycho-p2-repository-plugin + + true + true + + org.eclipse.tycho tycho-p2-director-plugin @@ -65,7 +73,6 @@ org.eclipse.tycho target-platform-configuration - consider linux diff --git a/debug/org.eclipse.cdt.debug.application.tests/META-INF/MANIFEST.MF b/debug/org.eclipse.cdt.debug.application.tests/META-INF/MANIFEST.MF index 113cd78c6fc..78c903c9f70 100644 --- a/debug/org.eclipse.cdt.debug.application.tests/META-INF/MANIFEST.MF +++ b/debug/org.eclipse.cdt.debug.application.tests/META-INF/MANIFEST.MF @@ -6,7 +6,6 @@ Bundle-Version: 1.0.0.qualifier Bundle-Vendor: %bundleVendor Bundle-RequiredExecutionEnvironment: JavaSE-17 Require-Bundle: org.eclipse.cdt.debug.application, - org.eclipse.cdt.debug.application.doc, org.eclipse.swtbot.eclipse.finder, org.eclipse.swtbot.go, org.eclipse.swtbot.junit4_x, diff --git a/debug/org.eclipse.cdt.debug.application/scripts/cdtdebug.sh b/debug/org.eclipse.cdt.debug.application/scripts/cdtdebug.sh index 9ec3758c8d9..0a982082cf6 100755 --- a/debug/org.eclipse.cdt.debug.application/scripts/cdtdebug.sh +++ b/debug/org.eclipse.cdt.debug.application/scripts/cdtdebug.sh @@ -1,6 +1,6 @@ #!/bin/bash ############################################################################### -# Copyright (c) 2014, 2015 Red Hat, Inc. and others +# Copyright (c) 2014, 2024 Red Hat, Inc. and others # # This program and the accompanying materials # are made available under the terms of the Eclipse Public License 2.0 @@ -97,12 +97,8 @@ case $ECLIPSE_HOME in *MacOS) ECLIPSE_HOME="$ECLIPSE_HOME/../Eclipse" ;; esac -PLUGIN_DIR="$ECLIPSE_HOME/plugins" -OSGI_JAR=`find "$PLUGIN_DIR" -maxdepth 1 -name 'org.eclipse.osgi_*.jar' -not -name '*source*' -exec basename {} \; | tail -1` - # Run eclipse with the Stand-alone Debugger product specified -"$ECLIPSE_EXEC" -clean -product org.eclipse.cdt.debug.application.product \ - -data "$HOME/workspace-cdtdebug" -configuration file\:"$HOME/cdtdebugger" \ - -dev file\:"$HOME/cdtdebugger/dev.properties" "${options[@]}" \ - -vmargs -Dosgi.jar=$OSGI_JAR -Declipse.home="$ECLIPSE_HOME" - +"$ECLIPSE_EXEC" -clean \ + -product org.eclipse.cdt.debug.application.product \ + -data "$HOME/workspace-cdtdebug" \ + "${options[@]}" diff --git a/debug/org.eclipse.cdt.debug.application/scripts/dev.properties b/debug/org.eclipse.cdt.debug.application/scripts/dev.properties deleted file mode 100644 index 40ed577ba02..00000000000 --- a/debug/org.eclipse.cdt.debug.application/scripts/dev.properties +++ /dev/null @@ -1,3 +0,0 @@ -# -#Fri Dec 20 17:22:35 EST 2013 -@ignoredot@=true diff --git a/debug/org.eclipse.cdt.debug.application/scripts/install.sh b/debug/org.eclipse.cdt.debug.application/scripts/install.sh index 15de5af0769..d2f6b0ae655 100755 --- a/debug/org.eclipse.cdt.debug.application/scripts/install.sh +++ b/debug/org.eclipse.cdt.debug.application/scripts/install.sh @@ -1,6 +1,6 @@ #!/bin/bash ############################################################################### -# Copyright (c) 2014 Red Hat, Inc. and others +# Copyright (c) 2014, 2024 Red Hat, Inc. and others # # This program and the accompanying materials # are made available under the terms of the Eclipse Public License 2.0 @@ -41,8 +41,6 @@ fi if [ ! -d "$HOME/cdtdebugger" ]; then mkdir -p "$HOME/cdtdebugger" fi -cp "$SCRIPT_DIR/config.ini" "$HOME/cdtdebugger" -cp "$SCRIPT_DIR/dev.properties" "$HOME/cdtdebugger" cp "$SCRIPT_DIR/cdtdebug.sh" "$HOME/cdtdebugger" chmod +x "$HOME/cdtdebugger/cdtdebug.sh" diff --git a/debug/org.eclipse.cdt.debug.application/src-config-generator/org/eclipse/cdt/debug/application/ConfigGenerator.java b/debug/org.eclipse.cdt.debug.application/src-config-generator/org/eclipse/cdt/debug/application/ConfigGenerator.java deleted file mode 100644 index 812217f93a1..00000000000 --- a/debug/org.eclipse.cdt.debug.application/src-config-generator/org/eclipse/cdt/debug/application/ConfigGenerator.java +++ /dev/null @@ -1,120 +0,0 @@ -/******************************************************************************* - * Copyright (c) 2016 Ericsson. - * - * This program and the accompanying materials - * are made available under the terms of the Eclipse Public License 2.0 - * which accompanies this distribution, and is available at - * https://www.eclipse.org/legal/epl-2.0/ - * - * SPDX-License-Identifier: EPL-2.0 - *******************************************************************************/ - -package org.eclipse.cdt.debug.application; - -import java.io.FileWriter; -import java.io.IOException; -import java.nio.file.Files; -import java.nio.file.Path; -import java.nio.file.Paths; -import java.util.ArrayList; -import java.util.HashMap; -import java.util.HashSet; -import java.util.List; -import java.util.Map; -import java.util.Set; -import java.util.regex.Matcher; -import java.util.regex.Pattern; -import java.util.stream.Stream; - -/** - * A "script" that generates the config.ini used by the stand-alone debugger - * script. This is done by parsing the debug.product file to find the plug-ins. - */ -public class ConfigGenerator { - private static final Pattern PLUGIN_LINE_PATTERN = Pattern.compile("\\s* PLUGINS_WITH_START_LEVEL = new HashMap<>(); - /** Plug-ins that we don't want to load when using the script VS using the product */ - private static final Set PLUGINS_NOT_IN_SCRIPT_VERSION = new HashSet<>(); - - static { - PLUGINS_WITH_START_LEVEL.put("org.apache.felix.scr", "@1\\:start"); //$NON-NLS-1$ //$NON-NLS-2$ - PLUGINS_WITH_START_LEVEL.put("org.eclipse.equinox.common", "@2\\:start"); //$NON-NLS-1$ //$NON-NLS-2$ - PLUGINS_WITH_START_LEVEL.put("org.eclipse.core.runtime", "@start"); //$NON-NLS-1$ //$NON-NLS-2$ - // We don't want the user to do "Check for updates", etc. - PLUGINS_NOT_IN_SCRIPT_VERSION.add("org.eclipse.update.configurator"); //$NON-NLS-1$ - PLUGINS_NOT_IN_SCRIPT_VERSION.add("org.eclipse.equinox.p2.ui"); //$NON-NLS-1$ - PLUGINS_NOT_IN_SCRIPT_VERSION.add("org.eclipse.equinox.p2.ui.sdk"); //$NON-NLS-1$ - } - - public static void main(String[] args) { - if (args.length < 4) { - printUsage(); - System.exit(1); - } - - String productFilePath = args[1]; - List pluginList = parsePluginList(productFilePath); - if (pluginList.isEmpty()) { - System.err.println("No plugins. Something must have gone wrong."); //$NON-NLS-1$ - System.exit(1); - } - - Path configOutputPath = Paths.get(args[3]); - generateConfigIni(pluginList, configOutputPath); - System.exit(0); - } - - private static void generateConfigIni(List pluginList, Path configOutputPath) { - try (FileWriter r = new FileWriter(configOutputPath.toFile())) { - r.write("osgi.install.area=file\\:$eclipse.home$\n"); //$NON-NLS-1$ - r.write("osgi.framework=file\\:$eclipse.home$/plugins/$osgi.jar$\n"); //$NON-NLS-1$ - r.write("osgi.bundles="); //$NON-NLS-1$ - - // Write all plug-in names - for (int i = 0; i < pluginList.size(); i++) { - String pluginName = pluginList.get(i); - if (PLUGINS_NOT_IN_SCRIPT_VERSION.contains(pluginName)) { - continue; - } - - r.write(pluginName); - - // Add start level if necessary - if (PLUGINS_WITH_START_LEVEL.containsKey(pluginName)) { - r.write(PLUGINS_WITH_START_LEVEL.get(pluginName)); - } - - r.write(','); - } - r.write('\n'); - r.write("osgi.configuration.cascaded=false\n"); //$NON-NLS-1$ - r.write("osgi.bundles.defaultStartLevel=4\n"); //$NON-NLS-1$ - } catch (IOException e) { - e.printStackTrace(); - System.exit(1); - } - } - - private static List parsePluginList(String productPath) { - List pluginList = new ArrayList<>(); - try (Stream stream = Files.lines(Paths.get(productPath))) { - stream.forEach((line) -> { - Matcher m = PLUGIN_LINE_PATTERN.matcher(line); - if (m.matches()) { - pluginList.add(m.group(1)); - } - }); - } catch (IOException e) { - e.printStackTrace(); - System.exit(1); - } - return pluginList; - } - - private static void printUsage() { - System.err.println("Usage:"); //$NON-NLS-1$ - System.err.println(" ConfigGenerator -product /path/to/foo.product -out /path/to/config.ini"); //$NON-NLS-1$ - } -} diff --git a/debug/org.eclipse.cdt.debug.standalone-feature/feature.xml b/debug/org.eclipse.cdt.debug.standalone-feature/feature.xml index 1041a4a32a5..c1af9f352e8 100644 --- a/debug/org.eclipse.cdt.debug.standalone-feature/feature.xml +++ b/debug/org.eclipse.cdt.debug.standalone-feature/feature.xml @@ -1,6 +1,6 @@ - - build-standalone-debugger-rcp - - - feature-no-source @@ -739,7 +732,6 @@ - diff --git a/releng/scripts/check_mvn_plugin_versions.sh b/releng/scripts/check_mvn_plugin_versions.sh index 60e2aec0868..0e66334bc1d 100755 --- a/releng/scripts/check_mvn_plugin_versions.sh +++ b/releng/scripts/check_mvn_plugin_versions.sh @@ -23,7 +23,7 @@ set -x # echo all commands used for debugging purposes # Point ourselves to the script's directory (so it can be run "out-of-tree") DIR=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd ) output="$(mktemp /tmp/check_mvn_plugin_versions.output.XXXXXX)" -${MVN:-mvn} versions:display-plugin-updates -P build-standalone-debugger-rcp -U -B -f $DIR/../../pom.xml | tee $output +${MVN:-mvn} versions:display-plugin-updates -U -B -f $DIR/../../pom.xml | tee $output #filter only updates and show unique # XXX: Jonah added the exclusion for sonar-maven-plugin as Eclipse's SonarQube installation is not new enough