Downloads:

257,650

Downloads of v 4.9.3:

912

Last Update:

14 Feb 2016

Package Maintainer(s):

Software Author(s):

  • cstrauss
  • cwilso11
  • earnie
  • keithmarshall

Tags:

mingw gnu unix gcc

MinGW

This is not the latest version of MinGW available.

4.9.3 | Updated: 14 Feb 2016

Downloads:

257,650

Downloads of v 4.9.3:

912

Software Author(s):

  • cstrauss
  • cwilso11
  • earnie
  • keithmarshall

Tags:

mingw gnu unix gcc

MinGW 4.9.3

This is not the latest version of MinGW available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install MinGW, run the following command from the command line or from PowerShell:

>

To upgrade MinGW, run the following command from the command line or from PowerShell:

>

To uninstall MinGW, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade mingw -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade mingw -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure mingw installed
  win_chocolatey:
    name: mingw
    state: present
    version: 4.9.3
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'mingw' do
  action    :install
  version  '4.9.3'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: mingw,
    Version: 4.9.3,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller mingw
{
   Name     = 'mingw'
   Ensure   = 'Present'
   Version  = '4.9.3'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'mingw':
  provider => 'chocolatey',
  ensure   => '4.9.3',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install mingw version="4.9.3" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator gep13 on 15 Feb 2016.

Description

MinGW (“Minimalistic GNU for Windows”) is a collection of freely available and freely distributable Windows specific header files and import libraries combined with GNU toolsets that allow one to produce native Windows programs that do not rely on any 3rd-party C runtime DLLs.

Gambit Scheme system, compiler and interpreter.

The default package now uses SJLJ (32-bit) and SEH (64-bit) exception handling and posix threads. Other configurations can be selected using the params:

  • exception: sjlj, seh (64-bit only), dwarf (32-bit only)
  • threads: posix, win32

For example: -params "/exception:sjlj /threads:win32"


tools\chocolateyInclude.ps1
# Default values
$packageName = 'mingw'
$packageVersion = '4.9.3'
$rev = 'v4-rev1'
$threads = 'posix'
$exception = 'default' #dwarf is 32bit only, seh is 64bit only, sjlj works with 32 / 64

$arguments = @{}
$packageParameters = $env:chocolateyPackageParameters

if($packageParameters) {
  $MATCH_PATTERN = "/([a-zA-Z]+):([a-zA-Z0-9]+)"
  $PARAMATER_NAME_INDEX = 1
  $VALUE_INDEX = 2

  if($packageParameters -match $MATCH_PATTERN ){
    $results = $packageParameters | Select-String $MATCH_PATTERN -AllMatches
    $results.matches | % {
      $arguments.Add(
        $_.Groups[$PARAMATER_NAME_INDEX].Value.Trim(),
        $_.Groups[$VALUE_INDEX].Value.Trim())
    }
  }

  if($arguments.ContainsKey("exception")) {
    Write-Host "Exception Argument Found"
    $exception = $arguments["exception"]
  }

  if($arguments.ContainsKey("threads")) {
    Write-Host "Threads Argument Found"
    $threads = $arguments["threads"]
  }
}

# Select 32-bit or 64-bit install. We're explicit here rather than depending on helpers so we can
# accurately set PATH.
$forceX86 = $env:chocolateyForceX86;
if (($forceX86) -or (Get-ProcessorBits 32)) {
  Write-Debug "installing mingw-w64 32-bit"
  if ($exception -eq 'default') {
    $exception = 'sjlj'
  } elseif (($exception -ne 'sjlj') -and ($exception -ne 'dwarf')) {
    Write-Host "Unknown value $exception for exception parameter, expected 'dwarf' or 'sjlj'; using sjlj"
    $exception = 'sjlj'
  }
  $mingwDir = 'mingw32'
  $prefix = 'i686'
} else {
  Write-Debug "installing mingw-w64 64-bit"
  if ($exception -eq 'default') {
    $exception = 'seh'
  } elseif (($exception -ne 'sjlj') -and ($exception -ne 'seh')) {
    Write-Host "Unknown value $exception for exception parameter, expected 'seh' or 'sjlj'; using seh"
    $exception = 'seh'
  }
  $mingwDir = 'mingw64'
  $prefix = 'x86_64'
}

# sha1 checksums
$checksums = @{
  'x86_64'[email protected]{
    'posix'[email protected]{
      'sjlj'='008bd533810a2c8e64c86e671a1c0230d6f521be';
      'seh'='cbaf53864cc4f86a27e0c84b9bdced0b7580dd7c'
    };
    'win32'[email protected]{
      'sjlj'='193af7cf78d3d814ae7e6172cc44d36d59214631';
      'seh'='754fdd027a6378680139914ba4323d99b754bd64'
    }
  };
  'i686'[email protected]{
    'posix'[email protected]{
      'sjlj'='df6ab0f7dd12333a0492c35cd5e85ae003054171';
      'dwarf'='210c177322dec580198cb41862b4ed60a521deb0'
    };
    'win32'[email protected]{
      'sjlj'='3efbd8eaa740da50b1212a76bcad34a59114b644';
      'dwarf'='06b342885f82ed07f114890d4b14e836dae7362e'
    }
  }
}
$checksum = $checksums[$prefix][$threads][$exception]

$zipFile = "$prefix-$packageVersion-release-$threads-$exception-rt_$rev.7z"
tools\chocolateyInstall.ps1
. (Join-Path (Split-Path -parent $MyInvocation.MyCommand.Definition) chocolateyInclude.ps1)

$url = "http://downloads.sourceforge.net/mingw-w64/$zipFile"
#http://downloads.sourceforge.net/mingw-w64/i686-4.8.3-release-posix-sjlj-rt_v3-rev0.7z
#http://downloads.sourceforge.net/mingw-w64/x86_64-4.8.3-release-posix-sjlj-rev0.7z

$binRoot = Get-BinRoot
Write-Debug "Bin Root is $binRoot"

Install-ChocolateyZipPackage "$packageName" "$url" "$binRoot" -checksum "$checksum" -checksumType 'sha1'

$installDir = Join-Path "$binRoot" "$mingwDir"
Write-Host "Adding `'$installDir`' to the path and the current shell path"
Install-ChocolateyPath "$installDir\bin"
$env:Path = "$($env:Path);$installDir\bin"
tools\chocolateyUninstall.ps1
. (Join-Path (Split-Path -parent $MyInvocation.MyCommand.Definition) chocolateyInclude.ps1)

Uninstall-ChocolateyZipPackage "$packageName" "${packageName}Install.zip"

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
MinGW-w64 7.3.0 6684 Tuesday, October 30, 2018 Approved
MinGW-w64 6.4.0 21245 Tuesday, October 30, 2018 Approved
MinGW-w64 5.4.0 461 Tuesday, October 30, 2018 Approved
MinGW 5.3.0 120064 Sunday, February 14, 2016 Approved
MinGW 4.9.3 912 Sunday, February 14, 2016 Approved
MinGW 4.8.5 1226 Saturday, February 13, 2016 Approved
MinGW 4.8.3.20150601 3777 Tuesday, June 2, 2015 Approved
MinGW 4.8.3.20141208 12808 Wednesday, January 7, 2015 Approved
MinGW 4.8.3 2192 Friday, October 17, 2014 Approved

This package has no dependencies.

Discussion for the MinGW Package

Ground Rules:

  • This discussion is only about MinGW and the MinGW package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or MinGW, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus