Ruben Van Boxem wrote: > > http://sourceforge.net/apps/trac/mingw-w64/wiki/MSYS > > > Great, someone actually found the wiki! > > MSYS itself is 32-bit, so having uname return something else is not > quite correct. There are other things bad about this suggestion: 1. > What if you have installed x86_64-w64-mingw32-gcc, > i686-w64-mingw32-gcc, and i686-pc-mingw32-gcc, and added all three > paths to MSYS's path? uname isn't at all a correct way to determine > the compiler's target, especially when you think about > cross-compilation, and (future/current) multilib. 2. The wiki states > the workaround/"The Right Way" to use mingw-w64 under MSYS. >
While MSYS is currently only offered as a 32bit application, you are using it in a 64bit system to do 64bit work. So you want your build environment to reflect natively that you are in a 64bit system. The resolution to what if I have this GCC build and that GCC build is no different than what you need to do now for multiple versions of the product. You just create a script to modify the PATH to point to the correct GCC build. > I believe passing -host=... to configure is a small price to pay (if > any) for the functionality you get from using MSYS+mingw-w64. The > MSYS package provided by mingw-w64 (aka me in this context) is only > the complete binary set of packages conveniently packed into one. Not really a big thing, just comfortableness of the end user. > I don't feel I have the right/will to change internal settings (of > which I do not know how far these reach) or to keep any changes up to > date. > I can create a patch to the msys.bat file that would allow the MSYSTEM to be set to MINGW64 just by passing in a parameter of MINGW64. Currently though if the environment variable is set before starting MSYS it will use that value. So if you start your MSYS with MSYSTEM=MINGW32 and then do ``MSYSTEM=MINGW64 start /msys.bat'' it will open a new window with a build environment for MINGW64. > I hope you can understand my reasoning, and I'll be happy to read any > arguments against what I stated above and consider revising my > opinion, but MSYS works fine as is. I understand your reasoning do you understand mine? My reasoning is toward the comfortableness of the noob who just wants to build 64bit native binaries with the least amount of typing. I am sure that MSYS works fine as you have documented it. But I did create the beast and MSYSTEM was meant to be used to control the build environment so that config.guess could guess correctly. I just didn't get around to documenting it formally. Earnie ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
