Generate op_enum.h during build rather than a separate step#344
Draft
Dewb wants to merge 3 commits intomonome:mainfrom
Draft
Generate op_enum.h during build rather than a separate step#344Dewb wants to merge 3 commits intomonome:mainfrom
Dewb wants to merge 3 commits intomonome:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This is an illustration of a potential approach to #340.
The changes:
op_enum.pyto generateop_enum.hduring the build process/src/gencodegen.mkProvide links to any related discussion on lines.
How should this be manually tested?
Any background context you want to provide?
If the related Github issues aren't referenced in your commits, please link to them here.
I have,
CHANGELOG.mdandwhats_new.mdhelp_mode.c(if applicable)