无法打开包含文件解决思路
无法打开包含文件
我有一个工程，里面用到了一个库，库在工程的当前目录下。
然后工程里面的代码用到了库里面的头文件，编译说无法打开包含文件，但是右键点击到包含的位置，选择打开 XXX 文档还是可以打开的，这是为毛？
虽然里面的包含是用 #include < ... > 这种形式的，但是写这个工程的人应该是编译通过了的，而且这种方式也是可以的。
------解决方案--------------------
VC6：
工程、设置、C/C++、分类：Preprocessor、附加包含路径：填写附加头文件所在目录 逗号间隔多项
VS20xx：
项目、属性、C/C++、附加包含目录：填写附加头文件所在目录 分号间隔多项
------解决方案--------------------
注意<>和" "两种包含头文件方式的区别。
写这个工程的人修改了一些配置，比如增加了一个<>方式的搜索路径。那么编译器就能找到对应的头文件。而你的编译器并没有这样配置。此时就不能也使用<>方式。
------解决方案--------------------
The #include Directive
The #include directive tells the preprocessor to treat the contents of a specified file as if those contents had appeared in the source program at the point where the directive appears. You can organize constant and macro definitions into include files and then use #include directives to add these definitions to any source file. Include files are also useful for incorporating declarations of external variables and complex data types. You only need to define and name the types once in an include file created for that purpose.
Syntax
#include "path-spec"
#include <path-spec>
The path-spec is a filename optionally preceded by a directory specification. The filename must name an existing file. The syntax of the path-spec depends on the operating system on which the program is compiled.
Both syntax forms cause replacement of that directive by the entire contents of the specified include file. The difference between the two forms is the order in which the preprocessor searches for header files when the path is incompletely specified.
Syntax Form Action
Quoted form This form instructs the preprocessor to look for include files in the same directory of the file that contains the #include statement, and then in the directories of whatever files that include (#include) that file. The preprocessor then searches along the path specified by the /I compiler option, then along paths specified by the INCLUDE environment variable.
Angle-bracket form This form instructs the preprocessor to search for include files first along the path specified by the /I compiler option, then along the path specified by the INCLUDE environment variable.
The preprocessor stops searching as soon as it finds a file with the given name. If you specify a complete, unambiguous path specification for the include file between two sets of double quotation marks (" "), the preprocessor searches only that path specification and ignores the standard directories.
If the filename enclosed in double quotation marks is an incomplete path specification, the preprocessor first searches the “parent” file’s directory. A parent file is the file containing the #include directive. For example, if you include a file named file2 within a file named file1, file1 is the parent file.
Include files can be “nested”; that is, an #include directive can appear in a file named by another #include directive. For example, file2, above, could include file3. In this case, file1 would still be the parent of file2 but would be the “grandparent” of file3.
When include files are nested, directory searching begins with the directories of the parent file and then proceeds through the directories of any grandparent files. Thus, searching begins relative to the directory containing the source currently being processed. If the file is not found, the search moves to directories specified by the /I compiler option. Finally, the directories specified by the INCLUDE environment variable are searched.
我有一个工程，里面用到了一个库，库在工程的当前目录下。
然后工程里面的代码用到了库里面的头文件，编译说无法打开包含文件，但是右键点击到包含的位置，选择打开 XXX 文档还是可以打开的，这是为毛？
虽然里面的包含是用 #include < ... > 这种形式的，但是写这个工程的人应该是编译通过了的，而且这种方式也是可以的。
------解决方案--------------------
VC6：
工程、设置、C/C++、分类：Preprocessor、附加包含路径：填写附加头文件所在目录 逗号间隔多项
VS20xx：
项目、属性、C/C++、附加包含目录：填写附加头文件所在目录 分号间隔多项
------解决方案--------------------
注意<>和" "两种包含头文件方式的区别。
写这个工程的人修改了一些配置，比如增加了一个<>方式的搜索路径。那么编译器就能找到对应的头文件。而你的编译器并没有这样配置。此时就不能也使用<>方式。
------解决方案--------------------
The #include Directive
The #include directive tells the preprocessor to treat the contents of a specified file as if those contents had appeared in the source program at the point where the directive appears. You can organize constant and macro definitions into include files and then use #include directives to add these definitions to any source file. Include files are also useful for incorporating declarations of external variables and complex data types. You only need to define and name the types once in an include file created for that purpose.
Syntax
#include "path-spec"
#include <path-spec>
The path-spec is a filename optionally preceded by a directory specification. The filename must name an existing file. The syntax of the path-spec depends on the operating system on which the program is compiled.
Both syntax forms cause replacement of that directive by the entire contents of the specified include file. The difference between the two forms is the order in which the preprocessor searches for header files when the path is incompletely specified.
Syntax Form Action
Quoted form This form instructs the preprocessor to look for include files in the same directory of the file that contains the #include statement, and then in the directories of whatever files that include (#include) that file. The preprocessor then searches along the path specified by the /I compiler option, then along paths specified by the INCLUDE environment variable.
Angle-bracket form This form instructs the preprocessor to search for include files first along the path specified by the /I compiler option, then along the path specified by the INCLUDE environment variable.
The preprocessor stops searching as soon as it finds a file with the given name. If you specify a complete, unambiguous path specification for the include file between two sets of double quotation marks (" "), the preprocessor searches only that path specification and ignores the standard directories.
If the filename enclosed in double quotation marks is an incomplete path specification, the preprocessor first searches the “parent” file’s directory. A parent file is the file containing the #include directive. For example, if you include a file named file2 within a file named file1, file1 is the parent file.
Include files can be “nested”; that is, an #include directive can appear in a file named by another #include directive. For example, file2, above, could include file3. In this case, file1 would still be the parent of file2 but would be the “grandparent” of file3.
When include files are nested, directory searching begins with the directories of the parent file and then proceeds through the directories of any grandparent files. Thus, searching begins relative to the directory containing the source currently being processed. If the file is not found, the search moves to directories specified by the /I compiler option. Finally, the directories specified by the INCLUDE environment variable are searched.