-
Notifications
You must be signed in to change notification settings - Fork 59
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
built-in gtest cmake find python order of operations suprise #605
Labels
Comments
This is what I am using in VisIt:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In most projects, we use
PYTHON_EXECUTABLE
to point to python.In VisIt we use
PYTHON_DIR
and have logic to derivePYTHON_EXECUTABLE
from that.B/c of this difference - I discovered that gtest will in fact go on to find a python if
PYTHON_EXECUTABLE
is not set.gtest's logic lead to VisIt finding the wrong python.
To protect against this, I had to make sure that
PYTHON_EXECUTABLE
was set before calling BLT.BLT should defend against this.
The text was updated successfully, but these errors were encountered: