Re: Thinking toward mingw64 and mingw-get

On Tue, Feb 26, 2013 at 9:50 PM, Cesar Strauss <[email protected]> wrote:
> 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?
>

Ideally mingw-get would be smart enough to pick the mingw64 package
for 64bit OS and install in into /MinGW and do the same for a 32bit
OS.  If a mingw64 package doesn't exist for a desired library and the
user insists on installing it anyway they would need to specify
mingw32-PACKAGE if they are on the 64bit OS but only specify PACKAGE
for a 32bit OS.

> Option 1)
>
> If the system is 32-bit:
>    c:\MinGW -> mingw32
>    No mingw64 option (it wouldn't run on a 32-bit system)
>

But if the user insists on installing a mingw64 package on a 32bit
system it should go to /mingw64.

> If the system is 64-bit:
>    c:\MinGW   -> mingw64
>    c:\MinGW32 -> mingw32
>

So I like this option.

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

No.

> Option 3)
>    c:\MinGW32 -> mingw32
>    c:\MinGW64 -> mingw64
>

Maybe.

> Option 4)
>    c:\MinGW\32 -> mingw32
>    c:\MinGW\64 -> mingw64
>

No.

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

So it comes down to what happens when you specify -m32 versus -m64
with the 64bit compiler?  Where does it search for libraries?  Or
rather than -m32/-m64 should we offer a 64bit cross to 32bit and vice
versa?  Should the PACKAGE.xml suffix the path given in profile.xml?
See next paragraph.

I'm thinking something along the lines of the 32bit cross environment
the libraries and its headers belong in i686-pc-mingw32 and for the
64bit cross environment the libraries and its headers belong in
x86_64-pc-mingw64.  How can we control this with mingw-get?

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