On Thu, Mar 5, 2015 at 9:32 AM, Greg Jung <[email protected]> wrote: > Guys, > The wiki pages give one a start at installation, and when combined with > pacman tips, > some of the upkeep of the installation. But the overall structure/strategy > is nowhere explained very well. I've been working with mingw, cygwin, msys2 > now for almost a year; most of what I know has come from viewing the > installed files and collected tidbits from maillist archives. > > When an explanation is provided as here in maillist it is (appropriately) > terse and usually full of assumptions and jargon shortcuts. If they were to > be unpacked and laid out in a regular composition, we'd have a few more wiki > pages in addition to the installation instructions. >
Agreed. It's difficult to write documentation targeted at such a broad spectrum of users, we're morphing from largely developer-centric to more user-facing so this will need to be improved; bringing developers on-board is probably easier for us. If you feel like writing anything up for the wiki in markdown format then we'd appreciate that. > A major class of mingw users are unix/linux-aware folk who are nevertheless > forced to use a windows platform, and so are familiar with all of the > resultant trappings that msys provides. Howevere, a possibly much larger > audience is the linux-curious, those owning powerful windows machines > (needed to host the good games) but open to hosting, at least > experimentally, an msys system. Please avoid mingw and msys and use MinGW-w64 and MSYS2 if possible. There's enough confusion about them already. > > Well I'm sure this is all familiar territory so I'll just halt my treatise > here. > ----8<---- > Some time earlier Corinna of Cygwin fame asked what was the point of msys2 > when there is cygwin64. I'm still uncertain of that myself. > If one exports PATH=/c/msys64/mingw64/bin:$PATH in cygwin64 how is that > different from using MINGW-64 shell in MSYS2? I will add a page specifically addressing your why-not-just-use-Cygwin question, but for now, here's an email to the mingw-w64 mailing list that describes the changes (which I will largely paste into the wiki): https://sourceforge.net/p/mingw-w64/mailman/message/31045473/ 1. shouldn't say "inside bash.exe", rather "inside msys-2.0.dll (our version of cygwin.dll)" And here cfg emailed about the callouts that Cygwin would need to implement for MSYS2 (we dropped the ball horribly due to time constraints and that unfortunately never got completed): https://sourceware.org/ml/cygwin-developers/2013-07/msg00073.html > Greg > > On Wed, Mar 4, 2015 at 11:37 AM, Ray Donnelly <[email protected]> > wrote: >> >> On Wed, Mar 4, 2015 at 7:06 PM, michel agoyan <[email protected]> >> wrote: >> >> Please read the wiki. https://sourceforge.net/p/msys2/wiki/ >> > ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
