cmake: Pass the osquery python path to googletest #8237
Merged
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.
Although googletest uses python only for its own tests, it still searches for it and the search cannot be removed.
In some configuration, like when using pyenv, CMake requires a shell to be able to find Python; this might not be present if run via the VsCode CMake extension.
While we can pass the Python3_EXECUTABLE path to osquery, googletest will still attempt to search Python in the system, slowing down the configuration phase.