Closed walbourn closed 1 year ago
See https://github.com/microsoft/DirectXTex/pull/293 for a related PR.
CMake build support and validation has been committed.
DirectXTex parses files, which is why it's important for this mitigation to be supported.
While DirectXMesh does not have much in the way of file parsing features (it's all local to the meshconvert sample), I added opt-in support in CMake and validation for Spectre-mitigations via https://github.com/microsoft/DirectXMesh/commit/133c459a8f6a2cebe16c10f08a3097e83901369e
For the DirectX Tool Kit, most use cases are to parse models and texture files included with the application rather than from untrusted sources. Added opt-in support in CMake and validation for Spectre-mitigations via: https://github.com/microsoft/DirectXTK/commit/0b8ca84069703139234a74ec753e3081651820b1, https://github.com/microsoft/DirectXTK12/commit/9b3bda236e9b14d636ec064953c36a279219633e
Adding pre-built Spectre libs to the DirectXTex, DirectXMesh, and UVAtlas Nuget packages is no biggie as the packages only grow to about ~20 MB.
https://github.com/microsoft/DirectXMesh/pull/78
https://github.com/microsoft/UVAtlas/pull/89
The DirectX Tool Kit packages would exceed 100 MB so I'm not going to add those.
I will add a spectre
feature to all my vcpkg ports though.
For NuGet, add an alternative library built with
/p:SpectreMitigation=Spectre
for Desktop (not supported by UWP).For vcpkg, add a
spectre
feature that sets a CMake build optionENABLE_SPECTRE_MITIGATION=ON
.