Re: Thinking toward mingw64 and mingw-get
Cesar Strauss <[email protected]>
| Newsgroups | gmane.comp.gnu.mingw.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2/26/2013 9:08 PM, Earnie Boyd wrote: > > I'm thinking about the possibilities of the MinGW project offering > both 32bit versions and 64bit versions of software. So we'll offer > mingw32-gcc and mingw64-gcc, etc and the end user experience in using > mingw-get to do so. > Where should they be installed by default? Option 1) If the system is 32-bit: c:\MinGW -> mingw32 No mingw64 option (it wouldn't run on a 32-bit system) If the system is 64-bit: c:\MinGW -> mingw64 c:\MinGW32 -> mingw32 Option 2) (Same as option 1, but c:\MinGW32 -> c:\MinGW\32) If the system is 32-bit: c:\MinGW -> mingw32 No mingw64 option (it wouldn't run on a 32-bit system) If the system is 64-bit: c:\MinGW -> mingw64 c:\MinGW\32 -> mingw32 Option 3) c:\MinGW32 -> mingw32 c:\MinGW64 -> mingw64 Option 4) c:\MinGW\32 -> mingw32 c:\MinGW\64 -> mingw64 The advantage of options 2 and 4 is that we have everything under one root only (c:\MinGW). The advantage of options 3 and 4 is that the paths are predictable (do not depend on the host architecture). The disadvantage of options 3 and 4 is the added redundancy if you only want the native compiler. Regards, Cesar ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb