Re: [Mingw-users] Necessary environment path settings?

Quoting NightStrike <nightstrike@...>:

>>
>> I agree that `i686-pc', (as such, or with any other CPU designation),
>> has little relevance for MinGW; formalising the de-facto use of just
>> `mingw32' here makes sense to me.
>
> If you want to be able to have x86_64 support merge back in to mingw,
> then supporting the CPU designation is advantageous.
>

The host/target becomes mingw64 is all.

> To that end, supporting the gnu standard canonicalization fully is
> advantageous.  With the way I build things, I can have both
> i686-pc-mingw and x86_64-pc-mingw targetted compilers installed in the
> same root directory structure.  However, the requirement of the lone
> "mingw32" directory makes that difficult.
>

So you can with --host=mingw32 and --host=mingw64 as well.  The triplet 
is really confusing, especially when i686 has no real value.

Earnie

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace