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: 3.17.3 -> 3.18.0 #93886

Merged
merged 1 commit into from Jul 26, 2020
Merged

cmake: 3.17.3 -> 3.18.0 #93886

merged 1 commit into from Jul 26, 2020

Conversation

r-burns
Copy link
Contributor

@r-burns r-burns commented Jul 26, 2020

Motivation for this change

New CMake version 3.18 available
https://cmake.org/cmake/help/v3.18/release/3.18.html

Things done

Patches had some conflicts, but they seemed to be trivial to resolve. Did that via git apply and merge on the cmake git itself - let me know if there's a more nixy way to do that.

  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions (Arch Linux)
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@jtojnar
Copy link
Contributor

jtojnar commented Jul 26, 2020

Yeah, git apply and git rebase on the project source tree is what I use myself. Not aware of any better way unfortunately.

Copy link
Contributor

@jtojnar jtojnar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. I did not see anything alarming in the changelog but someone more familiar with CMake should review it too.
  2. The patch needs to be reapplied correctly.
  3. The target branch needs to be changed to staging since this is a mass rebuild (see edit button at the top of this page).

Copy link
Contributor

@jtojnar jtojnar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

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

Successfully merging this pull request may close these issues.

None yet

4 participants