Using static variables causes linker error

Question

I get the following error with my code when I compile:

Undefined symbols for architecture x86_64:
  "A::MyNumber", referenced from:
      B::setValue(double) in B.o
ld: symbol(s) not found for architecture x86_64

In A's header file:

public:
    static double MyNumber;

In A's class file, above the constructor outside of any functions:

double A::MyNumber = 1.0;

In B's setValue() function:

#include "A.h"

void B::setValue(double val)
{
    double newVal = val * A::MyNumber;

    ...
}

I'm stumped...I looked at other examples in my project of using static variables and did my best to make sure I did it correctly. The only thing I can think of is that A is in a library that is linked by B's project.

Did you `#include A.h` in `B.cpp`? Also, you may want to read through the discussions [here](http://stackoverflow.com/questions/3698043/static-variables-in-c) — Cory Kramer, Aug 14 '14 at 12:44
`A is in a library that is linked by B's project` In this case you need to sign `MyNumber` as exported symbol. The way how to do this is compiler-dependent. For example, in VC++ it should be __declspec(dllexport) — Alex F, Aug 14 '14 at 12:51
Please include details on your compiler version, OS, and compile/link line(s). — Jordan Samuels, Aug 14 '14 at 12:53
The 'for architecture' part of the messages means it might well be Mac OS X, using `clang` (LLVM, derived from GCC, once upon a time). — Jonathan Leffler, Aug 14 '14 at 12:55

Tanuki · Answer 1 · 2014-08-14T15:58:18.247

You have made a typical mistake not to tell the linker about visibility. If you create the library you need to expose so called library symbols. The easiest way to check that is to use nm utility like this (-g means - show extern symbols only):

nm -g <your library>

The solution is quite simple but varies from compiler to compiler. For GCC/CLang it is attribute but almost all support extern. Typical usage looks like that somewhere in your top configuration file:

#if COMPILER_HAS_ATTR_HIDDEN_VISIBILITY   // GCC with -fvisibility=hidden
#define PUBLIC_API            __attribute__((visibility("default")))
#define PRIVATE_API           __attribute__((visibility("hidden")))
#elseif COMPILER_HAS_DECLSPEC_VISIBILITY  // Microsoft C++
#define PUBLIC_API            __declspec(dllexport)
#define PRIVATE_API
#else
#define PUBLIC_API            extern
#define PRIVATE_API
#endif

Now redeclare your class:

// Exposed class
class PUBLIC_API A
{

};

Another question is how to detect that with your building toolchain but that is out of scope of your question. For quick prove - add extern keyword to your class declaration and rebuild the library.

Using static variables causes linker error

1 Answers1