windows.mingw_w64: 12.0.0 -> 13.0.0

[RossSmyth]

Things done

1. Add updateScript
2. Add passthru test
3. Update mingw

I ran the test on my computer and it was fine.

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

---

Add a 👍 reaction to pull requests you find important.

[puffnfresh]

Looks good. I like the Nu shell update script.

[RossSmyth]

I find nushell to be quite good for updateScripts because it is good at extracting things from structured data.

[Ericson2314]

We shouldn't be using pkgsCross in packages, even for tests. Otherwise looks good though.

[Ericson2314]

See comment

[RossSmyth]

We shouldn't be using pkgsCross in packages, even for tests. Otherwise looks good though.

The primary consumer of this in nixpkgs is Wine, which definitely uses pkgsCross. How else are we supposed to cross compile?

[RossSmyth]

Besides just saying "no" without any alternative, how should I do about testing this?

[RossSmyth]

treefmt failed on a completely unrelated file

[RossSmyth]

#430675

[Eveeifyeve]

It has been merged, rebase your pr and it should be fixed.

[Ericson2314]

It looks like you changed the test now, but I was thinking that you could simply have the test use the current package set, and if you didn't pull tests from this package in a host=mingw package set they would fail to eval because unsupported system.

[RossSmyth]

I attempted to build the wine tests on my computer, but I just killed the build after 12 hours. Just building wine serially is fine, but I guess when it builds like four or five concurrently the scheduler can't handle it well.