Have a stack overflow issue with LimeLM in VS 2019Solved

ignore - figured it's our logger in debug mode that breaks in 2019 - ouf!

//

Investigating, I migrated to VS 2019, and one of the host we support generates a stack overflow applying our plugin when compiled with latest Wyday lib and VS Studio (v142, aka 2019).   It works in other API just one product we support as plugin does not work -   I read on the internet that Optimization method can cause that, and I am seeing this on MS page about 2015-2022 compatibility
 

Static libraries or object files compiled using the /GL (Whole program optimization) compiler switch or linked using /LTCG (Link-time code generation) aren't binary-compatible across versions, including minor version updates. All object files and libraries compiled using /GL and /LTCG must use exactly the same toolset for the compile and the final link. For example, code built by using /GL in the Visual Studio 2019 version 16.7 toolset can't be linked to code built by using /GL in the Visual Studio 2019 version 16.8 toolset.

I see there is some boost 2017 libs in the latest download folder.  Question would be to clear this up:  1) What is the optimization used by Limelm to compile libraries and is it compiled with V141, V142 or V143… ?  Toolset reports 16.11.15 here.