Cpp header and source files

I want to add an other set of functions in different files. So I created a new header file and a new cpp file, but now I don't seem to be able to include the new header file.

Can you please help me understand what I have done wrong? Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 3 years, 8 months ago. Active 3 years, 7 months ago. Viewed 13k times. Sirmyself Sirmyself 1, 1 1 gold badge 11 11 silver badges 25 25 bronze badges. Add the library header folder to your Additional Include Directories for your other projects. Are you sure that 2ndFunctionSet.

This is like saying "Windows knows no difference between a. But Windows is configured to treat them differently. For example, by default Visual Studio puts. Klaim Klaim Why do you say THE. Keand Because the compiler looks at only one.

It reads a. Does this mean that. Marc W Marc W A header. Johannes Schaub - litb Johannes Schaub - litb k gold badges silver badges bronze badges. Whereas: A CPP file includes the definitions from any header which it includes because CPP and header file together become a single 'translation unit' A header file might be included by more than one CPP file The linker typically won't like anything defined in more than one CPP file Therefore any definitions in a header file should be inline or static.

ChrisW ChrisW So I guess. Others have already offered good explanations, but I thought I should clarify the differences between the various extensions: Source Files for C:. Noldorin Noldorin k 56 56 gold badges silver badges bronze badges.

Most people actually use. Zifre: Yes, hence my saying that these are recommended naming conventions , even though many may not follow them. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Visit chat. Linked 7. It is most portable to use only letters, digits, dashes, and underscores in header file names, and at most one dot. It has two variants:. It searches for a file named file in a standard list of system directories.

However, if backslashes occur within file , they are considered ordinary text characters, not escape characters. None of the character escape sequences appropriate to string constants in C are processed. Included files are not limited to declarations and macro definitions; those are merely the typical uses. Any fragment of a C program can be included from another file. The include file could even contain the beginning of a statement that is concluded in the containing file, or the end of a statement that was started in the including file.

However, a comment or a string or character constant may not start in the included file and finish in the including file. An unterminated comment, string constant or character constant in an included file is considered to end with an error message at the end of the file.

To avoid confusion, it is best if header files contain only complete syntactic units--function declarations or definitions, type declarations, etc. In the above, target is the canonical name of the system GCC was configured to compile code for; often but not always the same as the canonical name of the system it runs on.

This is useful when you are compiling an operating system kernel or some other program that does not use the standard C library facilities, or the standard C library itself. GCC looks for headers requested with include " file " first in the directory containing the current file, then in the same places it would have looked for a header requested with angle brackets.

Line Control does not change GCC's idea of the directory containing the current file. This has two effects. That may or may not be the same as the directory containing the current file. There are several more ways to adjust the header search path. They are generally less useful. See section This is very likely to cause an error, e.

Even if it does not, it will certainly waste time. The standard way to prevent this is to enclose the entire real contents of the file in a conditional, like this:. This construct is commonly known as a wrapper ifndef.