-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
[dxsdk-d3dx] Add new port #17175
[dxsdk-d3dx] Add new port #17175
Conversation
Note I had to make use of |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
No idea what the OSX failures have to do with this port... |
Looks like the disk space ran out on the macOS machine. Not related to this port. |
As @Hoikas said above, I will rerun this PR once the disk space problem solved. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
The failures caused by |
OK. I've rebased against the latest master... |
LGTM now, thanks for adding this port @walbourn. |
This port doesn't support OSX, so no idea why it's failing that check. |
For osx pipeline, there is something wrong with our CI test machine. We're looking into this. You can ignore this failure, which is not related with this PR. I will rerun it once solved. Note: Please don't update changes in a PR unless it's necessary after we have added the label 'reviewed'. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Sorry. I was applying feedback to this open PR that I had been given in another PR about the new version semantics. |
@Hoikas is there something holding up this PR? |
Good question! Hopefully a maintainer will chime in if there are any outstanding other blockers. It LGTM. |
Thanks @walbourn :), sorry it took a little while to merge |
Adds a vcpkg port for the NuGet package Microsoft.DXSDK.D3DX. This provides the D3DX9, D3DX10, and D3DX11 utility libraries, their headers, and SHA-2 signed DLLs which can be redistributed side-by-side with the application per a new license.
Use of these legacy libraries is still not recommended for new projects, but this is a much more supportable way to use legacy D3DX libraries for existing projects that rely on it.
These headers are compatible with the modern Windows SDK, but are located in
include/dxsdk-d3dx
to isolate them.