Compatible Compilation Flags

[MrGreenWithAGun]

I found that to use std lib across my DLLs and EXE I needed to compile with /MTDd (multithreaded debug DLL), even my DLL that wraps your LIB. But that required I compile your LIB with /MTDd, which seems not to be the default. Are there any issues that I should be aware of using /MTDd (or the release version of DLL option build, /MD) for your LIB?

[jrouwe]

The default is indeed linking statically, but it is trivial to change it by setting the cmake option USE_STATIC_MSVC_RUNTIME_LIBRARY to OFF. This will require you to install the MSVC redistributables on any machine where your executable needs to run. If your application consists of DLLs then dynamically linking is the best choice.

[gistrec]

Adding to the maintainer's answer — one caveat once Jolt is split across a DLL/EXE boundary: matching the CRT (/MTd vs /MDd) isn't enough, the Jolt configuration defines must also be identical in every module that includes Jolt headers (your EXE, your wrapper DLL, and the Jolt build itself). Defines like JPH_DEBUG_RENDERER, JPH_PROFILE_ENABLED, JPH_DOUBLE_PRECISION and JPH_OBJECT_LAYER_BITS change struct sizes/layout, so a mismatch silently corrupts memory or fails to link.

Their defaults differ per configuration (e.g. JPH_DEBUG_RENDERER and the profiler are on in Debug/Release but off in Distribution), which is easy to trip over. Two safeguards: link the CMake Jolt target — it exposes these as PUBLIC compile definitions, so any module linking it inherits the exact same set — and rely on RegisterTypes(), which checks the important defines at startup and traces/aborts on a mismatch (see [Build/README.md](https://github.com/jrouwe/JoltPhysics/blob/master/Build/README.md)).