I'm trying to figure out why a behavior has changed in the engine since 4.19, and it has something to do with SDL2. But, enabling bDebugBuildsActuallyUseDebugCRT (I get that it is for Windows, but the documentation suggests it should work on Linux too.) does not let me step into SDL2, after rerunning Setup.sh and GenerateProjectFiles.sh. Previously, if a project was incompatible with the current engine I would receive a notification to rebuild it. Now, the engine just defaults to selecting no, whether I start up in a terminal or from the Linux desktop. Have any idea what changed in the engine, or how to get CLion to use debug third party libraries?
I'm trying to figure out why a behavior has changed in the engine since 4.19, and it has something to do with SDL2. But, enabling
bDebugBuildsActuallyUseDebugCRT(I get that it is for Windows, but the documentation suggests it should work on Linux too.) does not let me step into SDL2, after rerunningSetup.shandGenerateProjectFiles.sh. Previously, if a project was incompatible with the current engine I would receive a notification to rebuild it. Now, the engine just defaults to selecting no, whether I start up in a terminal or from the Linux desktop. Have any idea what changed in the engine, or how to get CLion to use debug third party libraries?