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

Update Mingw64 in windows-2019 image #10352

Closed
3 of 14 tasks
tobil4sk opened this issue Jul 26, 2024 · 4 comments · May be fixed by #10353
Closed
3 of 14 tasks

Update Mingw64 in windows-2019 image #10352

tobil4sk opened this issue Jul 26, 2024 · 4 comments · May be fixed by #10353

Comments

@tobil4sk
Copy link

tobil4sk commented Jul 26, 2024

Tool name

MinGW64

Tool license

GNU

Add or update?

  • Add
  • Update

Desired version

8.5.0

Approximate size

No response

Brief description of tool

No response

URL for tool's homepage

No response

Provide a basic test case to validate the tool's functionality.

No response

Platforms where you need the tool

  • Azure DevOps
  • GitHub Actions

Runner images where you need the tool

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Can this tool be installed during the build?

No response

Tool installation time in runtime

No response

Are you willing to submit a PR?

Yes: #10353

@tobil4sk
Copy link
Author

Currently, the install scripts are using a very old build of mingw from sourceforge with gcc 8.1.0 but v6 of the mingw runtime (from 2018). There is a build here with gcc 8.5.0: https://github.com/niXman/mingw-builds-binaries/releases/tag/8.5.0-rt_v10-rev0. This version is much more up to date with features in windows headers that have been added since 2018.

@ijunaidm
Copy link
Contributor

@tobil4sk - Thank you for bringing this issue to us. We are investigating on this issue , and will get back to you after our findings.

@ijunaidm
Copy link
Contributor

@tobil4sk - We don't want to switch to new installation method because we have concerns about supply chain when we use unofficial build of mingw.

And we prefer to keep using official build distributed via sourceforge even if it is outdated.

Thank you, I am closing the issue.

@tobil4sk
Copy link
Author

We don't want to switch to new installation method because we have concerns about supply chain when we use unofficial build of mingw.

This is the same source that is already being used by the windows-2022 image:

$url = Resolve-GithubReleaseAssetUrl `
-Repo "niXman/mingw-builds-binaries" `
-Version "$version" `
-Asset "$arch-*-release-$threads-$exceptions-$runtime-*.7z"

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

Successfully merging a pull request may close this issue.

3 participants
@tobil4sk @ijunaidm and others