So far, we’ve talked about .cpp files (implementation) and .h files (declarations). But how do they actually work together to create a complete program?

Think of it like making a movie:

• Header files act as scripts: they describe what exists.
• Source files are the filming: they contain working code.
• The compiler and linker function as editors: they assemble all components into a single finished product.

The Compilation Process – Step by Step

When you build your program, three big things happen:

1. Preprocessing – The compiler first processes all #include statements and any #define macros. It’s like gathering all your materials before starting the build.
2. Compilation – Each .cpp file is compiled separately into something called an object file (.o or .obj depending on your system) This is code the computer understands, but not yet assembled into a full program.
3. Linking – The linker takes all those object files and combines them into a single executable (.exe on Windows, no extension on many Unix systems.)

It’s completely normal to see errors during compilation or linking while learning. Understanding which step failed makes fixing problems much easier.

Pro Tip: If you forget to include a .cpp file in your project, the linker will complain about “undefined references.” That’s just its way of saying, “I can’t find the function you promised me!”

Putting It All Together – A Simple Multi-File Example

Let’s say you’re writing a tiny program to greet a user.

Greet.h

Greet.cpp

main.cpp

When you compile, the build process will:

• See greetUser() in the header
• Find its definition in Greet.cpp
• Link it with main.cpp to create the final program

Why This Matters

When we move into data structures and more complex projects, you’ll have to use multi-file programs - putting everything in one giant .cpp file will become messy fast. Learning this now will make advanced programming much smoother.