0

I was wondering if there is a way in MSYS2 to specify the base MinGW/MinGW64 directory?

In MSYS (i.e., MSYS-1), after installing MSYS, it knows that the directory structure is, e.g., /c/mingw/msys/..., and if you install a mingw package using mingw-get, the installed binary goes to /c/mingw/bin. I think this might be because there is /mingw mount in the default /etc/fsab.

Now, when I do a similar operation under MSYS2/MinGW64 with MSYS2 at /c/mingw/msys64, the binary isn't installed the /c/mingw/bin anymore. For example, if I install clang as follows:

pacman -S mingw-w64-x86_64-clang

the binary is installed to:

/c/mingw/msys64/mingw64/bin/clang.exe

as if MSYS2 were creating another mingw64 installation within itself (with bin/lib/etc/share ...). This confuses MinGW64, as it reports that clang cannot be found. I know I can add another path, but it's rather weird to have one MinGW installation at the root, and another inside a subfolder of MSYS2. And I suspect this could cause inconsistency in the tool-chain in the future.

My question is, is there a way to let MSYS2 install MinGW packages to the MinGW directory tree as with MSYS?

Thanks

thor
  • 21,418
  • 31
  • 87
  • 173

1 Answers1

6

To say that you have "another mingw64 installation within itself" is the wrong way to think about it. MSYS2 is the system that is running the show, that you chose to put it in a folder called "C:/mingw" doesn't make that folder a mingw-w64 system in any way, you've just got an MSYS2 system rooted at "C:/mingw/msys64"

I'm afraid that MSYS2 doesn't allow selection of root folders for any of its 3 repositories outside of selecting the global system root (i.e. the folder to which you install or unpack MSYS2). The main reason for this is because we use pacman as our package manager and this facility doesn't exist there since it is a tool to manage the entire system and as such, all pacman packages are compressed with absolute folders (which are unpacked relative to the global system root).

Since MSYS2 (via Cygwin; credit for the core of MSYS2 lies with Cygwin) provides "/etc/fstab", you might think to use that to enable you to put "/mingw{32,64}" elsewhere, and to an extent you can get away with that, but I strongly urge you not to do this as it will just result in problems. For example, Native Windows programs that expect to be able to use a relative path of "../" to get from "C:/msys64/mingw64" to "C:/msys64" will be sorely disappointed, and by that I mean will they will likely crash. For this reason I am not going to tell you how to achieve such a broken system.

You should try to think of your MSYS2 install as being a complete sub-system in its own right, where we've made some decisions (like the location of the "/", "/mingw32" and "/mingw64" folders) for you to improve compatibility and remove some variables that would make problems more frequent and difficult to diagnose and fix.

I would also recommend installing MSYS2 to the root of a drive (any drive) due to Windows 260 MAXPATH limit. I know that with UNC paths the limit is much further out, but most MSYS2 and Windows software do not use UNC paths and have hardcoded C string arrays of size MAXPATH+1 all over the place. Doing this may also help you to think of the MinGW-w64 repositories as being sub-repositories of the overall MSYS2 system, rather than the other way around.

For pacman reference, you should use these pages:

pacman.conf(5) Manual Page and pacman tips

Ray Donnelly
  • 3,920
  • 1
  • 19
  • 20
  • +1: Thanks for the clarification. But regarding: "Doing this may also help you to think of the MinGW-w64 repositories as being sub-repositories of the overall MSYS2 system", what about the MinGW-w64 installation that gives us gcc and the associated 3rd-party development tools in that MinGW installation? Does this mean that MSYS2 and MinGW-w64 actually use two unrelated systems of repositories? – thor Jul 17 '14 at 01:24
  • Historically MinGW-w64 was a source-only project. There are/were various other projects that made binary builds of MinGW-w64 and sometimes some other precompiled binaries. The mingw-builds project became the 'official' binary packagers for MinGW-w64 a while ago, so the only 'official' binaries are toolchain executables and mingw32-make.exe. In other words, the MinGW-w64 project doesn't have a system of repositories. MSYS2 on the other hand has two MinGW-w64 repositories, one for 32bit Windows software and one for 64bit Windows software. Both of these repositories contain toolchain packages. – Ray Donnelly Jul 23 '14 at 11:21
  • @RayDonnelly Hi, I ran into the same confusion. I installed MinGW-w64 first and MSYS2 later to find the folder structure in msys installation directory for mingw32 and 64. And then I edited "/etc/fstab". But I see you have urged not to do. In this case, what do you suppose I shall do? re-installing MinGW-w64 so that it lies inside msys installation directory and edit environmental variables accordingly? – Sndn Dec 22 '17 at 07:44
  • If you are using MSYS2 then you should use MSYS2/mingw-w64 packages instead of using the standalone mingw-w64. `pacman -S mingw-w64-x86_64-toolchain` for example. – Ray Donnelly Dec 26 '17 at 14:17