Why do I get "unresolved external symbol" errors when using templates?

When I write C++ code for a class using templates and split the code between a source (CPP) file and a header (H) file, I get a whole lot of "unresolved external symbol" errors when it comes to linking the final executible, despite the object file being correctly built and included in the linking. What's happening here, and how can I fix it?

From stackoverflow

• Templated classes and functions are not instantiated until they are used, typically in a separate .cpp file (e.g. the program source). When the template is used, the compiler needs the full code for that function to be able to build the correct function with the appropriate type. However, in this case the code for that function is detailed in the template's source file and hence unavailable.

  As a result of all this the compiler just assumes that it's defined elsewhere and only inserts the call to the templated function. When it comes to compile the template's source file, the specific template type that is being used in the program source isn't used there so it still won't generate the code required for the function. This results in the unresolved external symbol.

  The solutions available for this are to:

  1. include the full definition of the member function in the template's header file and not have a source file for the template,
  2. define all the member functions in the template's source file as "inline", or
  3. define the member functions in the template's source with the "export" keyword. Unfortunately this isn't supported by a lot of compilers.

  Both 1 and 2 basically address the problem by giving the compiler access to the full code for the templated function when it is attempting to build the typed function in the program source.

  nimrodm : In (3) you have an typing error. You probably meant keyword and not keyboard. I don't see how defining the functions as 'inline' will help. You need to put them in the header or explicitly instantiate the templates using the types you need.

  Johannes Schaub - litb : you should possibly rephrase (2). no idea what you mean by it

  Zan Lynx : The "export" keyword provides the full definition as well. It may be in some slightly encoded form like a compiler parse tree but it isn't very well hidden. Of course I suppose machine code doesn't hide the source very well either.

• Another option is to put the code in the cpp file and in the same cpp file add explicit instantiations of the template with the types you expect to be using. This is useful if you know you're only going to be using it for a couple of types you know in advance.

• what does this even mean: " and in the same cpp file add explicit instantiations of the template with the types you expect to be using. "