-
Notifications
You must be signed in to change notification settings - Fork 3.3k
FIX: dxcore include when compiling with older Windows SDK #25297
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
base: main
Are you sure you want to change the base?
Conversation
/azp run Linux QNN CI Pipeline, Win_TRT_Minimal_CUDA_Test_CI, Windows ARM64 QNN CI Pipeline, Windows GPU Doc Gen CI Pipeline, Windows x64 QNN CI Pipeline |
Azure Pipelines successfully started running 5 pipeline(s). |
the change is failing for the existing build. Could you share more information how this change fixed your build? Is there a header file path change for a specific range of SDK? |
@fs-eire That's weird.
Note that with I suppose your pipeline doesn't populate |
Seems currently @skottmckay @snnn do we want to always include "directx_headers" for Windows build so that ORT can build against older Windows SDK |
@fs-eire Do you have a pipeline that builds with |
I don't think we have an active DML CI pipeline. |
For the record, These are my build parameters (when testing without forcing older sdk): |
I see other includes in dml
but if really needed we could have #if __has_include(<directx/dxcore.h>)
#include <directx/dxcore.h>
#else
#include <dxcore.h>
#endif
#if __has_include(<directx/dxcore_interface.h>)
#include <directx/dxcore_interface.h>
#else
#include <dxcore_interface.h>
#endif Also as @fs-eire said, |
Description
Confirmed to work with
Windows 10 SDK, version 1803 (10.0.17134.0)