user-0 提问: 在源程度中调用自己编写的头文件，如何实现

回复:
user: user-1
content: 引用 1 楼 xlshu 的回复:no such file or directory 头文件应该保存到什么位置才能找到？  个人习惯，一般与源文件同目录，也可单独放， #include "\pathname\filename.h" 也可

user: user-2
content: #include <ceshitou.h> 改成 #include "ceshitou.h"  VS把这个头文件添加到工程里面去，把文件拖进去就好 VC++把文件包含到include文件夹中在调用

user: user-3
content: 1.如果文件 ceshitou.h 和被调用它的*.c文件在同一文件夹下，将 #include <ceshitou.h> 改为 #include "ceshitou.h" ； 2.如果文件 ceshitou.h 和被调用它的*.c文件不在同一文件夹下，比如路径为d:\MyCHead\ceshitou.h ，则将 #include <ceshitou.h> 改为 #include "d:\MyCHead\ceshitou.h" ；  注：头文件包含的形式：a.#include <stdio.h> /*stdio.h为IDE自带的头文件库中的头文件*/                       b.#include "school.h" /*school.h为用户自定义的头文件*/ 所以，如果将 #include <stdio.h> 写成 #include "stdio.h",程序编译的效率会降低，因为在编译时，IDE会先在当前目录找 #include "stdio.h" ,但是找不到，所以又会在IDE的库文件系统目录中找，头文件库里存在，编译通过，若当前*.c文件目录和库文件中都不存在，就会报错。

user: user-4
content: #3正解 <>只能从标准目录查找 ""范围比较广

user: user-5
content: 改成 void main() { mytou();   }

user: user-6
content: #include <ceshitou.h> 改成 #include "ceshitou.h"

user: user-7
content: 是不是用VS呢，如果是这样的话可能是你没把这个头文件添加到工程里面去，把文件拖进去就好了

user: user-0
content: no such file or directory 头文件应该保存到什么位置才能找到？

user: user-8
content: 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.   The following example shows file inclusion using angle brackets:  #include <stdio.h>  This example adds the contents of the file named STDIO.H to the source program. The angle brackets cause the preprocessor to search the directories specified by the INCLUDE environment variable for STDIO.H, after searching directories specified by the /I compiler option.  The following example shows file inclusion using the quoted form:  #include "defs.h"  This example adds the contents of the file specified by DEFS.H to the source program. The double quotation marks mean that the preprocessor searches the directory containing the parent source file first.  Nesting of include files can continue up to 10 levels. Once the nested #include is processed, the preprocessor continues to insert the enclosing include file into the original source file.  Microsoft Specific   To locate includable source files, the preprocessor first searches the directories specified by the /I compiler option. If the /I option is not present or fails, the preprocessor uses the INCLUDE environment variable to find any include files within angle brackets. The INCLUDE environment variable and /I compiler option can contain multiple paths separated by semicolons (;). If more than one directory appears as part of the /I option or within the INCLUDE environment variable, the preprocessor searches them in the order in which they appear.  For example, the command  CL /ID:\MSVC\INCLUDE MYPROG.C  causes the preprocessor to search the directory D:\MSVC\INCLUDE for include files such as STDIO.H. The commands  SET INCLUDE=D:\MSVC\INCLUDE CL MYPROG.C  have the same effect. If both sets of searches fail, a fatal compiler error is generated.  If the filename is fully specified for an include file with a path that includes a colon (for example, F:\MSVC\SPECIAL\INCL\TEST.H), the preprocessor follows the path.  For include files specified as #include "path-spec", directory searching begins with the directory of the parent file and then proceeds through the directories of any grandparent files. Thus, searching begins relative to the directory containing the source file containing the #include directive being processed. If there is no grandparent file and the file has not been found, the search continues as if the filename were enclosed in angle brackets.  END Microsoft Specific