Sneaky little linker errors...

They always find their way into my programs!

This time I'm getting errors when I try to include my header file in two different files of the same project. The only way it works is if instead of #including "consoletools.h", I #include "consoletools.cpp" in one of the two files. I'm also getting errors when i make a test program for the sole purpose of using the functions. The .h contains just the function definitions, the .cpp has the actual code for the functions.

The consoletools.h file:

Code:

#include <windows.h>
#include <iostream>

using namespace std;

#ifndef CONSOLETOOLS_H
#define CONSOLETOOLS_H

void setTitle(char title[]);

void cls();

void replaceChar(char newChar, int x, int y);

void color(string text, string color);

void toggleCursor();

void pause();

char getYorN();

#endif

The test file:

Code:

#include "consoletools.h"
#include <iostream>
using namespace std;

int main()
{
   string x; 
   while (true)
   {
      cin >> x;
      cin.ignore();  
      setTitle("Test program"); 
      color("Color\n",x);   
      pause();
      cls();
   } 
}

The linker errors:

Code:

  [Linker error] undefined reference to `setTitle(char*)' 
  [Linker error] undefined reference to `color(std::string, std::string)' 
  [Linker error] undefined reference to `pause()' 
  [Linker error] undefined reference to `cls()' 
  ld returned 1 exit status

I'm sure the answer is obvious... but I can't seem to point it out. I hate linker errors!

You need to add consoletools.cpp to the project.
That is, both need to be compiled.

Whaaatt... are you saying i need to add it to every project I use it in? Does that mean I can't use it on programs with only one source file?

That's what it means.

Another option if all those functions have small implementations is to place them inline in the header file. Then you can use the header by itself in a one source file project.

That's strange, I've been able to #include .h files without having to worry about adding their .cpp to the project.

Did those headers have their function implemented in the header file, or a cpp file? Were those headers part of a library that was being linked to the project?

Another option is to build a lib file and add that to the linker options. You won't have to include the source files in each project, but you will have to remember to link to the library.

No, the header files consisted of nothing but the function headers (within a class, however). Their .cpps werent in the same folder, but their object files were.

If you have the object files to link to, then you don't actually need to add the source files. It works the same as the lib stuff I mentioned. You just have to figure out how to get the object files to link to your source file. How you do that depends on your IDE or compilation/link method.

You should've noticed some logic errors there:
You have a header file, with prototypes.
You have a source file, where you call those functions.
You get an undefined reference error and you don't notice there's no function definitions in your files??