c7b53c03ae
Since we clone the environments to build thirdparty code, we don't get an explicit dependency on the build objects produced by that environment. So when we update thirdparty code, Godot code using it is not necessarily rebuilt (I think it is for changed headers, but not for changed .c/.cpp files), which can lead to an invalid compilation output (linking old Godot .o files with a newer, potentially ABI breaking version of thirdparty code). This was only seen as really problematic with bullet updates (leading to crashes when rebuilding Godot after a bullet update without cleaning .o files), but it's safer to fix it everywhere, even if it's a LOT of hacky boilerplate. |
||
|---|---|---|
| .. | ||
| aes_context.cpp | ||
| aes_context.h | ||
| crypto.cpp | ||
| crypto.h | ||
| crypto_core.cpp | ||
| crypto_core.h | ||
| hashing_context.cpp | ||
| hashing_context.h | ||
| SCsub | ||