Skip to content

Conversation

@rushilmehra
Copy link
Collaborator

There's a bug on OSX that prevents the CMake jobserver from working properly, and so CMake defaults to a single-threaded build. It's not clear when this is actually going to get fixed, so recent versions of cmake-rs just disable the jobserver and have CMake fall back to the number of available cores:
rust-lang/cmake-rs#229

This means we don't need e6833b0

There's a bug on OSX that prevents the CMake jobserver from working
properly, and so CMake defaults to a single-threaded build. It's not
clear when this is actually going to get fixed, so recent versions of
cmake-rs just disable the jobserver and have CMake fall back to the
number of available cores:
rust-lang/cmake-rs#229

This means we don't need e6833b0
@rushilmehra rushilmehra merged commit c3c7e16 into master Feb 19, 2025
23 checks passed
@rushilmehra rushilmehra deleted the bump-cmake branch February 19, 2025 09:30
@jrose-signal
Copy link
Contributor

Ah, can you not make this a requirement? We're stuck on an older version of CMake for Windows cross-compiling: rust-lang/cmake-rs#171. (Well, not "stuck", but it would be more of a pain to work around for little benefit.) Any new client will get the latest cmake 1.x by default, and you can of course update boring's lockfile, which won't affect clients, but setting it in Cargo.toml imposes it on everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants