Skip to content
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

cmake: Pass the osquery python path to googletest #8237

Merged

Conversation

Smjert
Copy link
Member

@Smjert Smjert commented Jan 5, 2024

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.

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.
@Smjert Smjert added the cmake pure cmake changes label Jan 5, 2024
@Smjert Smjert requested review from a team as code owners January 5, 2024 22:57
@Smjert Smjert merged commit 0dc5af7 into osquery:master Jan 18, 2024
16 checks passed
@Smjert Smjert deleted the stefano/cmake/googletest-config-speed branch January 18, 2024 00:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmake pure cmake changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants