Re: [Msys2-users] MinGW - MSYS2 interraction

[Ray D. <min...@gm...>]

On Mon, Jan 5, 2015 at 5:24 PM, Bill Lee <Bi...@wr...> wrote:
> My first attempt at installing and using MinGW on a Windows7 platform
> involved downloading MinGW and using the mingw-get application. As best
> as I can tell that properly loaded MinGW32 and MSYS since MSYS2 is not
> an option.

I think clarity on the projects / names would be helpful. There's no
project called MinGW32, there's mingw.org and MinGW-w64. We're a
friend-project of the latter and have no relationship with the former.

>
> At Pete Batard's suggestion I downloaded a fresh copy of mingw-w64 and
> installed it, followed by a download of MSYS2. This is where the fun
began!

When you say you downloaded a fresh copy of mingw-w64, do you mean one of
the mingw-builds supplied toolchain packages? If so, as Jonathan Baecker
said, you don't need that just use pacman to get everything instead (though
see below *)

>
> 1) Where in the directory hierarchy of the minGW64 should the MSYS2 be
> loaded? r should it even BE IN the MinGW hierarchy?

MSYS2/MinGW-w64 consists of two or three systems, the MSYS2 system itself
(the native sysroot for that would be e.g. C:\msys64) then a 64-bit
MinGW-w64 system (sysroot at C:\msys64\mingw64) and a 32-bit MinGW-w64
system (sysroot at C:\msys64\mingw32).

>
> 2) How do I resolve the fact that between the MinGW install and the
> MSYS2 install there are several(!) 'lib' 'include' 'bin' 'and so-forth"
> floating around, bits and pieces of :stuff: that you need to work with
> floating everywhere.

You don't install "MinGW" except via pacman, then you'll have a
C:\msys64\bin folder and maybe a C:\msys64\mingw64\bin and maybe a
C:\msys64\mingw32\bin folder, same for lib folders. In bash, we bind mount
/bin to C:\msys64\bin since some unix things expect that, all of the same
applies for lib).

>
> As an example: I open a command window in MSYS2 (very nice bash
> implementation, much better than the MSYS version). But none of the
> compilers are visible! A "which g++" returns not found. But the compiler
> IS there, in a /bin directory located somewhere in the minGW hierarchy!

For MSYS2 gcc, install it with:
pacman -S gcc

Jonathan Baecker told you how to install MinGW-w64 toolchains. Also, see:

https://sourceforge.net/p/msys2/wiki/MSYS2%20installation/

(* below) If you want to use MSYS2 purely as a bash prompt/unix-y shell,
then that is fine. In that case, you'd never install any pacman packages
that are prefixed by "mingw-w64-" and would instead download e.g. a
mingw-builds supplied toolchain release. I'd suggest putting that in
/opt/mingw32 or /opt/mingw64 (so C:\msys64\opt\mingw32 or
C:\msys64\opt\mingw64), then prefixing its bin subfolder onto your PATH as
appropriate (in ~/.profile for example).

Regards,

Ray Donnelly.

>
> 3) Is there a comparable tool t mingw-get that operates with the
> MinGW64/MSYS2 combination? Yes, I know of pacman and used it for the
> MSYS2 effort, but is there a pacman-like tool for the whole thing? Like
> mingw-get? And if not, why not and what does a poor user have to do to
> work around the lack?
>
> Regards,
>
> Bill Lee
>
>
------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Msys2-users mailing list
> Msy...@li...
> https://lists.sourceforge.net/lists/listinfo/msys2-users