Use uvx for CMake and Server Toolchain for Ninja#2097
Use uvx for CMake and Server Toolchain for Ninja#2097eramongodb merged 4 commits intomongodb:masterfrom
Conversation
kevinAlbs
left a comment
kevinAlbs
left a comment
There was a problem hiding this comment.
LGTM with a possible additional call to InstallUV.
There was a problem hiding this comment.
I neglected to ask in prior related PRs. Is installing uv expected to be removed once DEVPROD-13413 is complete? Or is this intended as a long-term strategy to pin to the version uv used for testing?
There was a problem hiding this comment.
Is installing uv expected to be removed once DEVPROD-13413 is complete?
Yes. I would like to defer the responsibility of maintaining the uv binary to DevProd rather than maintaining it ourselves. If we do want to have more control over the uv binary version, we can/should maintain it via an Evergreen Toolchain project (DEVPROD-19855) instead of CI scripts executed per-build.
vector-of-bool
left a comment
vector-of-bool
left a comment
There was a problem hiding this comment.
Sorry for the very long delay. This LGTM.
3 participants
Followup to #2083. Applies similar EVG configuration updates as done in mongodb/mongo-cxx-driver#1428, but with a drive-by update to bump uv's version to 0.8.13 (latest release).
The old calls to
find_python3andPYTHON3_BINARYare removed in favor of always invoking Python viauv. All calls tofind-cmake-latest.share now replaced withinstall-build-tools.shwhich obtains a latest CMake binary + a ninja binary for (optional) use by CMake. The Ninja generator is now used by default on non-Windows distros.Batch scripts call
uvx cmakerather thanuv tool install cmake->cmaketo avoid dealing withPATH-related complications. These can/should hopefully be converted into Bash scripts and use Ninja+MSVC in the future...