-
Notifications
You must be signed in to change notification settings - Fork 126
Create individual Python virtualenv's in cmake builds #908
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
Conversation
❌ Integration test FAILEDRequested by @dconeybe on commit 79b91ca
Add flaky tests to go/fpl-cpp-flake-tracker |
…ause 3.10.2 is not supported on windows-latest GitHub runners
…0.2) because 3.10.2 is not supported on windows-latest GitHub runners" This reverts commit e21af90. Using cmake 3.18.1 from the Android NDK suffered from the bug where the build failed with "Invalid revision: 3.18.1-g262b901". This is a known android studio bug that, for some reason, has never been fixed.
This reverts commit 2836f21. Cmake 3.10.2 is not installed on the windows-latest GitHub Actions runner image.
…n the android sdk
…ith debugging build issues
… arguments in build.gradle files
|
The last of the build errors are related to gradle communicating with cmake. I think those will be fixed once we upgrade the gradle plugin, which will happen after dropping gnustl support (#889). I'm going to put this PR on hold for now. |
Use a Python virtualenv when running Python scripts during a cmake build.
This PR is a copy of firebase/firebase-ios-sdk#9662.
This PR adds a new cmake module,
python_setup, that defines a single function:FirebaseSetupPythonInterpreter(). This function will find a Python interpreter installed on the system, create a virtualenv with it, pip-install dependencies into it, and set a variable to the path of the Python executable. Then, when cmake wants to run a Python script, it uses the one in the virtualenv.This has several benefits compared to the old design: