Skip to content

Add HctGen of DXIL.rst back to build without LLVM_BUILD_DOCS required #7346

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

Merged
merged 2 commits into from
Apr 15, 2025

Conversation

tex3d
Copy link
Contributor

@tex3d tex3d commented Apr 15, 2025

HctGen of DXIL.rst should happen on every ordinary build, and be updated with other HctGen modified files.

This isn't about building the doc, it's about updating it when definitions change in hctdb.py.

We've been missing updates to DXIL.rst for quite a while due to this issue, introduced here.

This also brings DXIL.rst up to date.

Copy link
Member

@damyanp damyanp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like this is something we'd want to have happen as a matter of course. Nice catch!

tex3d added 2 commits April 15, 2025 13:45
HctGen of DXIL.rst should happen on every ordinary build, and be updated with other HctGen modified files.

This isn't about building the doc, it's about updating it when definitions change in hctdb.py.

This also brings DXIL.rst up to date.
We've been missing updates to DXIL.rst for quite a while due to this issue.
@tex3d tex3d force-pushed the add-dxil-rst-to-hctgen branch from 9318582 to c362750 Compare April 15, 2025 20:48
@tex3d tex3d merged commit 5f18e2b into microsoft:main Apr 15, 2025
12 checks passed
@github-project-automation github-project-automation bot moved this from New to Done in HLSL Roadmap Apr 15, 2025
@tex3d tex3d deleted the add-dxil-rst-to-hctgen branch April 15, 2025 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants