tag:help.appveyor.com,2012-11-13:/discussions/suggestions/615-support-for-msys2AppVeyor: Discussion 2018-10-19T08:17:06Ztag:help.appveyor.com,2012-11-13:Comment/363767792016-04-05T04:04:01Z2016-04-05T04:04:01ZSupport for MSYS2<div><p>OK, thanks. I've added a new issue: <a href="https://github.com/appveyor/ci/issues/733">https://github.com/appveyor/ci/issues/733</a>
- will try to deliver it in this week update.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/363767792016-04-05T20:13:17Z2016-04-05T20:13:18ZSupport for MSYS2<div><p>Feodor, a few points:</p>
<ul>
<li>
<p>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
<code>update-core</code> was removed and pacman now supports core
updates directly. This is desirable to be installed by default and
have people migrating from <code>update-core</code> as soon as
possible.</p>
</li>
<li>
<p>When you do, can you please perform a more basic installation?
The one in <a href="https://github.com/appveyor/ci/issues/597">https://github.com/appveyor/ci/issues/597</a>
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:</p>
<pre>
<code>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</code>
</pre></li>
</ul>
<ul>
<li>
<p>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 <em>cygheap base mismatch</em> 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.</p>
</li>
<li>
<p>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 <em>MINGW64</em>)</p>
<ul>
<li><em>MINGW32</em>, for 32-bit native toolchain (for example gcc
will resolve to /mingw32/bin/gcc)</li>
<li><em>MINGW64</em>, for 64-bit native toolchain (for example gcc
will resolve to /mingw64/bin/gcc)</li>
<li><em>MSYS</em>, for MSYS toolchain (for example gcc will resolve
to /usr/bin/gcc)</li>
</ul>
</li>
</ul></div>Someonetag:help.appveyor.com,2012-11-13:Comment/363767792016-04-06T19:24:30Z2016-04-06T19:24:30ZSupport for MSYS2<div><p>My main concern with this update is backward compatibility. If
there is no <code>update-core</code> anymore it would mean a lot of
builds broken?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/363767792016-04-07T21:23:54Z2016-04-07T21:23:55ZSupport for MSYS2<div><p>Currently, projects update the system with:</p>
<pre>
<code>update-core # Core
pacman -Syu # Rest</code>
</pre>
<p><em>This is not going to work anymore even if you keep the old
installation</em>. The <code>update-core</code> script will pull
latest pacman and remove itself anyway, invalidating these steps
for subsequent updates. Projects would need to be patched like
this:</p>
<pre>
<code>pacman -Sy pacman # Latest pacman
pacman -Syu # Core
pacman -Syu # Rest</code>
</pre>
<p>However if you migrate to new installation, one meaningless line
can be removed:</p>
<pre>
<code>pacman -Syu # Core
pacman -Syu # Rest</code>
</pre></div>Someone