|
From: Bill L. <Bi...@WR...> - 2015-01-05 17:24:50
|
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. 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! 1) Where in the directory hierarchy of the minGW64 should the MSYS2 be loaded? r should it even BE IN the MinGW hierarchy? 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. 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! 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 |