Re: Thinking toward mingw64 and mingw-get
Earnie Boyd <[email protected]>
| Newsgroups | gmane.comp.gnu.mingw.devel |
|---|---|
| Message-ID | <CA+sc5mkpcd8vhLXqhF5YWKsg1jMVGW1P0rtEP=qqZQ6PcLWX_g@mail.gmail.com> |
On Tue, Feb 26, 2013 at 4:19 PM, Keith Marshall <[email protected]> wrote: > On 26/02/13 20:27, Earnie Boyd wrote: >> No, not really since this is a discussion of our default for mingw-get >> which currently is mingw32. > > Huh? There is no such thing as a default subsystem for mingw-get. > There is a default system-map, defined in profile.xml; it identifies the > subsystems which are to be managed. There is absolutely no reason why > those shouldn't include both mingw32 and mingw64 concurrently, with > separate and independent sysroot paths specified for each. > Well, there certainly appears to be! If I choose gcc it defaults to mingw32 as it appears to the end user. And looking a profile.xml doesn't give me any hint as to how mingw32 is the default by appearance. > Additionally, with respect to your earlier post: > >> Could mingw-get consider the default to be mingw64 based on the value >> of PROCESSOR_ARCHITECTURE? > > Since there is no such thing as a default, this is irrelevant. There is > no need for mingw-get to care about the processor architecture; the > determinant is the subsystem named within the XML catalogue, and the > package names specified within the scope of each subsystem record. When > a user requests installation of a mingw32 package, that is exactly what > he will get; if he requests a mingw64 package, he will get that. > But currently it defaults to mingw32 as it appears to the user. How is that determined? >> Note this value will also depend on if mingw-get is a 64bit native >> binary versus a 32bit one. So if someone downloads the 32bit >> mingw-get they will default to mingw32 while the 64bit native binary >> will default to mingw64. The value of PROCESSOR_ARCHITECTURE will >> change if executing in SysWOW64 emulation mode to x86 and remain at >> AMD64 if running in native mode. > > Also irrelevant. There is no processor affinity for mingw-get; neither > should there be, nor will there be, while I continue to maintain it. Well, then let us discuss end user experience as it relates to installing software where MinGW.org is providing both 32bit and 64bit versions of software. Surely if the user is using a 64bit version of mingw-get he'll want it to appear to default to mingw64 instead of mingw32. -- Earnie -- https://sites.google.com/site/earnieboyd ------------------------------------------------------------------------------ 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