Re: Thinking toward mingw64 and mingw-get

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.

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.

> 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.

-- 
Regards,
Keith.

------------------------------------------------------------------------------
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