-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[directxmesh, directxtex, directxtk, uvatlas, dxut, effects11] June 2023 update #32033
Conversation
Locally validated all supported triplets and features: DirectXMesh
|
DirectXTex
|
Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags. |
UVAtlas
|
I'm taking a look at rsm-bsa now... |
DirectX Tool Kit for DX11
DirectX Tool Kit for DX12
|
DXUT
Effects11
|
The problem with rsm-bsa was that my CMake targets files were not properly reflecting the optional vs. required package dependencies. This have all been fixed upstream, the tags regenerated, and the portfile SHA512 values updated. microsoft/DirectXTex#369 |
This PR updates the following ports for June 2023 releases on GitHub:
directxmesh, directxtex, directxtk, directxtk12, uvatlas, dxut, effects11
directxtex: A few minor new features for the library and tools
direcxtxtex, directxmesh only require directx-headers for MinGW or Linux scenarios -or- if using the
dx12
feature.command-line tools are now Long Path Aware on Windows 10, Version 1607 or later
command-line tools updated for a minor output quirk when printing system error messages
All ports now have explicit
usage
filesdxut, effects11 now use
vcpkg_install_copyright
All ports updated with CMake fixes for specific issues: