GLEW技术疑问：为何必须定义GLEW_STATIC宏？

Great question—this is one of those linker gotchas that trips up a lot of folks when working with GLEW, but it’s actually pretty straightforward once you understand how static vs dynamic library linkage works under the hood. Let’s break it down step by step:

• First, what’s the purpose of GLEW_STATIC?
  GLEW’s header files use preprocessor macros to control how function declarations are compiled. Specifically, it’s there to tell the compiler whether you’re linking against the static version of GLEW or the dynamic (shared) version.

  Under the hood, the header looks something like this (simplified):

  #ifdef GLEW_STATIC
  #  define GLEWAPI  // Empty—no special modifiers needed for static linkage
  #else
  // For dynamic libraries, add platform-specific import markers
  #  if defined(_WIN32) && !defined(__GNUC__)
  #    define GLEWAPI __declspec(dllimport)
  #  elif defined(__GNUC__) && (__GNUC__ >= 4)
  #    define GLEWAPI __attribute__((visibility("default")))
  #  endif
  #endif
  
  // Example function declaration using the macro
  GLEWAPI void glewInit(void);
  

• Why does this matter for static linkage?
  When you link statically, you’re essentially copying all of GLEW’s code directly into your final executable. That means every GLEW function is part of your program—there’s no need to mark them as "imported from a DLL/shared library."

  If you don’t define GLEW_STATIC, the compiler will add those dynamic-library import modifiers (like __declspec(dllimport) on Windows) to every GLEW function. The linker will then look for the dynamic import library (e.g., glew32.lib on Windows) instead of the static library (glew32s.lib), leading to "unresolved external symbol" errors because the static library’s symbols don’t match the decorated ones the compiler expects.

• What if you mix it up?

  • If you define GLEW_STATIC but link dynamically: The compiler won’t generate the necessary import markers, so your program will fail at runtime when it tries to load GLEW’s shared library—either it can’t find the functions, or you’ll get duplicate symbol errors if the static code was accidentally linked in too.
  • If you skip GLEW_STATIC but link statically: As mentioned, the linker will hunt for dynamic import symbols that don’t exist in the static library, throwing those frustrating unresolved symbol errors.

At the end of the day, GLEW_STATIC is just a way to align GLEW’s header declarations with the type of library you’re actually linking against. It ensures the compiler and linker speak the same language when resolving GLEW’s functions.

内容的提问来源于stack exchange，提问作者user8539043