Add CI action for pure CMake build#80
Merged
Merged
Conversation
jbcoe
force-pushed
the
jbcoe/cmake-ci
branch
3 times, most recently
from
a81b509 to
edab9b0
Compare
Collaborator
|
I'm curious about why we need this as a separate CI action. |
Collaborator
Author
|
Having an isolated CMake build working is quite useful when debugging changes (like to addition of type stubs in a future PR). The current suite of CI checks only run CMake builds from within ha package install which is done in a temporary directory. I suspect that uv allows the build directory to be specified which might be an alternative to supporting isolated CMake builds. |
StephenOman
approved these changes
Feb 13, 2026
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
2 participants
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.
Ensure that a CMake build works outside of a Python project install.