Generate config headers from configs.specification #9587
Closed
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.
Since a41bcb1, configuration headers and sources are generated using a Rust tool rather than being hardcoded. Implement the CMake logic necessary to compile the tool and generate these sources. Use a Python script to extract config section names from the specification file instead of hardcoding them into CMake build files to reduce the chance of the CMake build getting out of a sync.
A followup PR will handle connecting the hackc_options target to the Rust libraries that depend on it.