Incorrect settings in Visual studio build files (Issue #23676)
antonyvholmes
After downloading the latest wxWidgets 3.2.2.1 and built the wxWidgets libraries from source in Visual Studio 2019 community. My app had linker errors. Checking the settings for the x64 and Win32 settings, release and debug, the builds for the static libraries were configures to use the DLL (dynamic) runtime libraries in the C++ settings, which meant manually changing the settings and rebuilding the libraries again. Can you take a look at this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
PB
This is not a bug but a feature and is the default for the MSVS solutions, the bundled makefiles, and the cmakefile. Static linking building wxWidgets static libraries, but they still link to the compiler runtimes dynamically (as recommended by Microsoft).
If you really want to build wxWidgets linking with MSVCRT statically using provided MSVS solutions, it would be probably easiest by changing the value of wxRuntimeLibs from dynamic to static, as described here.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
Closed #23676 as completed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
As @PBfordev wrote (thanks!), this is intentional. Using static CRT libraries is officially not recommended and so is not the default, even if you can still change it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
wsu
Vadim Zeitlin
w> Why is this not recommended? Is it a general preference that Microsoft CRT
w> patches are automatically used?
Yes, I think this is the main argument.
Regards,
VZ