diff --git a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_makefile.htm b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_makefile.htm index 50628fd7df9..a87315263c6 100644 --- a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_makefile.htm +++ b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_makefile.htm @@ -3,7 +3,7 @@ - + Makefile @@ -102,35 +102,43 @@ Test2.o : Test2.h

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?

+

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

-Error launching builder (make –k clean all )
+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�.

+

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’�.

+

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'.
+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.

+ +

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

+

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.

+

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

+

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

 make -k clean all 
 make: *** [clean] Error 255
@@ -141,7 +149,7 @@ 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.
+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.
diff --git a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_search.htm b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_search.htm index 9720349d978..58be204a3ad 100644 --- a/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_search.htm +++ b/doc/org.eclipse.cdt.doc.user/concepts/cdt_c_search.htm @@ -215,7 +215,7 @@ 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.�

+

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

diff --git a/doc/org.eclipse.cdt.doc.user/images/discovery_preferences.png b/doc/org.eclipse.cdt.doc.user/images/discovery_preferences.png index 7a2926ec3b4..7efe392b4d9 100644 Binary files a/doc/org.eclipse.cdt.doc.user/images/discovery_preferences.png and b/doc/org.eclipse.cdt.doc.user/images/discovery_preferences.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/mprop_binaryp.png b/doc/org.eclipse.cdt.doc.user/images/mprop_binaryp.png new file mode 100644 index 00000000000..84cef88dff8 Binary files /dev/null and b/doc/org.eclipse.cdt.doc.user/images/mprop_binaryp.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/mprop_build.png b/doc/org.eclipse.cdt.doc.user/images/mprop_build.png index f452e961c08..e7d07328f86 100644 Binary files a/doc/org.eclipse.cdt.doc.user/images/mprop_build.png and b/doc/org.eclipse.cdt.doc.user/images/mprop_build.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/mprop_builders.png b/doc/org.eclipse.cdt.doc.user/images/mprop_builders.png index a52a72f3f4b..b906938cb85 100644 Binary files a/doc/org.eclipse.cdt.doc.user/images/mprop_builders.png and b/doc/org.eclipse.cdt.doc.user/images/mprop_builders.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/mprop_errorp.png b/doc/org.eclipse.cdt.doc.user/images/mprop_errorp.png index 6e045a6de46..fa1b4caba1f 100644 Binary files a/doc/org.eclipse.cdt.doc.user/images/mprop_errorp.png and b/doc/org.eclipse.cdt.doc.user/images/mprop_errorp.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/mprop_file_types.png b/doc/org.eclipse.cdt.doc.user/images/mprop_file_types.png index b88e5365222..105904578b8 100644 Binary files a/doc/org.eclipse.cdt.doc.user/images/mprop_file_types.png and b/doc/org.eclipse.cdt.doc.user/images/mprop_file_types.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/mprop_indexer.png b/doc/org.eclipse.cdt.doc.user/images/mprop_indexer.png index 9bf3f271951..128b282a397 100644 Binary files a/doc/org.eclipse.cdt.doc.user/images/mprop_indexer.png and b/doc/org.eclipse.cdt.doc.user/images/mprop_indexer.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/mprop_info.png b/doc/org.eclipse.cdt.doc.user/images/mprop_info.png index d74c0bbde38..3bd2565ee67 100644 Binary files a/doc/org.eclipse.cdt.doc.user/images/mprop_info.png and b/doc/org.eclipse.cdt.doc.user/images/mprop_info.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/mprop_proref.png b/doc/org.eclipse.cdt.doc.user/images/mprop_proref.png index ef6013d114a..451d440c387 100644 Binary files a/doc/org.eclipse.cdt.doc.user/images/mprop_proref.png and b/doc/org.eclipse.cdt.doc.user/images/mprop_proref.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/new_proj_wz_std_dscovery.png b/doc/org.eclipse.cdt.doc.user/images/new_proj_wz_std_dscovery.png index bd33b72ce97..ca6f4e78c2c 100644 Binary files a/doc/org.eclipse.cdt.doc.user/images/new_proj_wz_std_dscovery.png and b/doc/org.eclipse.cdt.doc.user/images/new_proj_wz_std_dscovery.png differ diff --git a/doc/org.eclipse.cdt.doc.user/images/sprop_make_discovery.png b/doc/org.eclipse.cdt.doc.user/images/sprop_make_discovery.png index 78a967ea549..6fcf2c4c3e4 100644 Binary files a/doc/org.eclipse.cdt.doc.user/images/sprop_make_discovery.png and b/doc/org.eclipse.cdt.doc.user/images/sprop_make_discovery.png differ diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_o_ref.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_o_ref.htm index 3e6693ada56..901f521a7d7 100644 --- a/doc/org.eclipse.cdt.doc.user/reference/cdt_o_ref.htm +++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_o_ref.htm @@ -72,6 +72,7 @@ File Types
Indexer
Error Parser
+ Binary Parser
Project References
Standard Make Projects
Info
diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_mbinary.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_mbinary.htm new file mode 100644 index 00000000000..b68418d48b7 --- /dev/null +++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_mprop_mbinary.htm @@ -0,0 +1,69 @@ + + + + + + + C/C++ Project Properties, Managed, Binary Parser + + + + +

C/C++ Project Properties, Managed, Binary Parser

+

You can select the Binary Parsers you require for the project.

+ +

To ensure the accuracy of the C/C++ Projects view and the ability 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 .o file in the C/C++ Projects view.

+ + + +

C/C++ Project Properties, Managed, Binary Parser

+ + + +
+
Binary Parser
+
Select a binary parser from the list.
+
Binary Parser Options
+
If a binary parser has parser options you can define them in this section.
+
Restore Defaults
Returns any changes back to their default setting.
+
Apply
Applies any changes.
+
+ +

Related concepts +
+Build overview

+

Related tasks +
+Selecting a binary parser

+

Related reference
+C++ Project Properties, Standard, Info
+C++ Project Properties, Standard, Builders
+C++ Project Properties, Standard, File Types
+C++ Project Properties, Standard, Include Paths and Symbols
+C++ Project Properties, Standard, Indexer
+C++ Project Properties, Standard, Make Builder
+C++ Project Properties, Standard, Error Parser
+C++ Project Properties, Standard, Discovery Options
+C++ Project Properties, Standard, Source
+C++ Project Properties, Standard, Output
+C++ Project Properties, Standard, Projects
+C++ Project Properties, Standard, Libraries
+C++ Project Properties, Standard, Path Containers
+C++ Project Properties, Standard, Project References
+C++ Project Properties, Managed, Info
+C++ Project Properties, Managed, Builders
+C++ Project Properties, Managed, Build
+C++ Project Properties, Managed, File Types
+C++ Project Properties, Managed, Indexer
+C++ Project Properties, Managed, Error Parser
+C++ Project Properties, Managed, Project References

+ + +

+IBM Copyright Statement +

+ + + + \ No newline at end of file diff --git a/doc/org.eclipse.cdt.doc.user/topics_Reference.xml b/doc/org.eclipse.cdt.doc.user/topics_Reference.xml index 2d7ef658db5..9827bd51ba4 100644 --- a/doc/org.eclipse.cdt.doc.user/topics_Reference.xml +++ b/doc/org.eclipse.cdt.doc.user/topics_Reference.xml @@ -70,6 +70,7 @@ +