Skip to content
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

How to handle D3D12 Agility SDK and DirectML redist #580

Closed
damyanp opened this issue Jul 16, 2021 · 7 comments
Closed

How to handle D3D12 Agility SDK and DirectML redist #580

damyanp opened this issue Jul 16, 2021 · 7 comments
Assignees
Labels
missing api Some documented API is missing from the metadata

Comments

@damyanp
Copy link
Member

damyanp commented Jul 16, 2021

The DirectX 12 Agility SDK and DirectML redist both ship their most recent versions of the APIs outside of the SDK.

The model they use is that there's a single, non-branching, versioning of these APIs. But there's a period of time where the most recent version is only available via the redists.

For example, we might have Agility SDK v20 contain an interface that doesn't exist in the Windows SDK until v10.0.xxxxx.x. But we'd want middleware built against Agility SDK v20 to be able to interoperate with applications build against Windows SDK v10.0.xxxxx.x.

@damyanp damyanp changed the title How do handle D3D12 Agility SDK and DirectML redist How to handle D3D12 Agility SDK and DirectML redist Jul 16, 2021
@mikebattista mikebattista added the missing api Some documented API is missing from the metadata label Aug 5, 2021
@mikebattista
Copy link
Collaborator

@sotteson1 sounds like another scenario for enabling other SDKs to produce their own winmd for consumption from our projections (#66 ). Could we try to onboard these to the msbuild tooling?

@DBouma
Copy link

DBouma commented Oct 24, 2022

Currently running into the same issue, are there any updates on this?

@mikebattista
Copy link
Collaborator

@damyanp do you own these redists? The owners would need to use our tooling to produce metadata out of their repos.

@mikebattista
Copy link
Collaborator

Closing out as the corresponding kit owners would need to produce their own metadata. I'd recommend filing issues in the corresponding repos to track the request.

@MarijnS95
Copy link
Contributor

This is related to #998, right? @mikebattista seems the tooling is all there but just waiting for @riverar to document it all?

Is this something external developers can piece together to bind to the Agility SDK in Rust via windows-rs, or should we "wait" for the Agility SDK developers to ship the metadata first? (And then is windows-rs already capable of generating usable bindings out of these files, while relying on / linking against the generated windows crate?)

@MarijnS95
Copy link
Contributor

@mikebattista I opened an issue for the Agility SDK at microsoft/DirectX-Headers#79, as requested. Unfortunately I lack the context to properly describe what needs to happen in this repo for .winmd files to be generated (CC #998/@riverar again for linkable docs) but I hope this gets the ball rolling as we're in need of these bindings for quite some time :)

@riverar
Copy link
Collaborator

riverar commented Nov 16, 2022

I can assist with getting them started with metadata generation, will work with you in that other issue. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
missing api Some documented API is missing from the metadata
Projects
None yet
Development

No branches or pull requests

6 participants