Support for MSYS2

Someone's Avatar


24 Mar, 2015 08:28 PM

MSYS2 is awesome, it makes building Windows software much easier. Pidgin++ for example mostly eliminated the need for this thanks to MSYS2:

Showing page 2 out of 2. View the first page

  1. Support Staff 31 Posted by Feodor Fitsner on 05 Apr, 2016 04:04 AM

    Feodor Fitsner's Avatar

    OK, thanks. I've added a new issue: - will try to deliver it in this week update.

  2. 32 Posted by Someone on 05 Apr, 2016 08:13 PM

    Someone's Avatar

    Feodor, a few points:

    • Can you please wait for new installer releases before installing msys32, and then reinstall msys64? I think Alexey plans to release them soon. There was a relevant change to pacman where the update-core was removed and pacman now supports core updates directly. This is desirable to be installed by default and have people migrating from update-core as soon as possible.

    • When you do, can you please perform a more basic installation? The one in includes random additional packages. If they were to be added, there are literally hundreds of them, but this would make system update more expensive. For a default environment we install the basic development groups, with projects installing their specific dependencies when needed:

      pacman --sync --noconfirm VCS
      pacman --sync --noconfirm base-devel
      pacman --sync --noconfirm mingw-w64-i686-toolchain
      pacman --sync --noconfirm mingw-w64-x86_64-toolchain # msys64-only
    • Note that I added VCS above since for some reason they are not part of base-devel. This should get git installed by default and fix errors like cygheap base mismatch that I see reported in that issue. This was because git getting resolved to some external installation. The new installers should also fix similar issues because MSYS2 now only uses a basic Windows path by default.

    • I see the same user is having problem with gcc. Before starting MSYS2 we are supposed to configure path with the MSYSTEM variable in appveyor.yml wtih (they want MINGW64)

      • MINGW32, for 32-bit native toolchain (for example gcc will resolve to /mingw32/bin/gcc)
      • MINGW64, for 64-bit native toolchain (for example gcc will resolve to /mingw64/bin/gcc)
      • MSYS, for MSYS toolchain (for example gcc will resolve to /usr/bin/gcc)
  3. Support Staff 33 Posted by Feodor Fitsner on 06 Apr, 2016 07:24 PM

    Feodor Fitsner's Avatar

    My main concern with this update is backward compatibility. If there is no update-core anymore it would mean a lot of builds broken?

  4. 34 Posted by Someone on 07 Apr, 2016 09:23 PM

    Someone's Avatar

    Currently, projects update the system with:

    update-core # Core
    pacman -Syu # Rest

    This is not going to work anymore even if you keep the old installation. The update-core script will pull latest pacman and remove itself anyway, invalidating these steps for subsequent updates. Projects would need to be patched like this:

    pacman -Sy pacman  # Latest pacman
    pacman -Syu        # Core
    pacman -Syu        # Rest

    However if you migrate to new installation, one meaningless line can be removed:

    pacman -Syu # Core
    pacman -Syu # Rest
  5. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:05 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac