Using WXUSINGDLL has no effect on the linkage

Question

my wxWidgets application has multiple C++ projects (one executable and all the other static libraries). I am using Visual Studio 2022 with a solution having Debug and Release configurations only for x64.

I decided to upgrade the wxWidgets version from 3.1.2 to 3.2.8. The Debug configuration builds without any error. The Release, unfortunately, presents a list of unresolved symbols (LINK2001) and redefinitions (LINK2005).

In all these cases, these errors appear during the linkage of the executable project, and are referencing objects existing only in one of those static libraries:

Error LNK2001 unresolved external symbol "void (__cdecl* wxTheAssertHandler)(class wxString const &,int,class wxString const &,class wxString const &,class wxString const &)" (?wxTheAssertHandler@@3P6AXAEBVwxString@@H000@ZEA) wxPgConsole C:\pg\wxPgConsole\wxbase.lib(getTimeString.obj)

According to many posts, the solution for this kind of error is to define the WXUSINGDLL preprocessor symbol.

I have defined this in source code, but I got the same errors.

#define WXUSINGDLL
class wxPgConsole ... {
};

I have set it in the VCXPROJ also, but I got the same errors.

enter image description here

What else can I do to get a working Release build?

• 3CEZVQ: Where do you define that macro? Please post a minimal reproducible example.
• Jesper Juhl: Probably relevant (maybe duplicate): What is an undefined reference/unresolved external symbol error and how do I fix it?.
• 3CEZVQ: It's still unclear where you have defined that macro. This is a common error when users define a macro in the Debug project configuration but build Release
• Igor: Can you build and run minimal sample?