Re: [Mingw-cross-env-list] Build / Host / Target

[Tony Theodore]

On 21 May 2010 05:19, Mark Brand <address@hidden> wrote:
>
> On 05/20/2010 08:46 PM, Volker Grabsch wrote:
>>
>> Tony Theodore<address@hidden>  schrieb:
>>>
>>> I'm still often confused by host/target
>>
>> I think the build / host / target are quite easy to understand:
>>
>>     "Build" is where the program is compiled.
>>     "Host" is where the program will run.
>>     "Target" is where the program produces code for.
>>
>> Thus, "target" makes only sense for compilers and similar stuff.
>> In Mingw-cross-env, we have the following situation:
>>
>>     Normal packages:
>>
>>         build = Unix
>>         host  = Windows
>>
>>     Native packages (e.g. pkg-config):
>>
>>         build  = Unix
>>         host   = Unix
>>
>>     GCC, Binutils, NSIS:
>>
>>         build  = Unix
>>         host   = Unix
>>         target = Windows
>
> I'll take this opportunity to correct a typo in my previous list of the
> names used in the Qt configure script.  (I made mistakes in the "endian"
> list.)  Here is the new and improved version:
>
> Describe the platform we are building Qt *for* (MinGW aka "win32-g++"):
>  -arch  CFG_ARCH
>  -xplatform XPLATFORM
>  XQMAKESPEC
>  -big-endian or -little-endian switch CFG_ENDIAN

I would still `think` that -arch and -*-endian are the buidling *on* platform.

> Describe the platform we are building Qt *on* (some form of Unix):
> -host-arch CFG_HOST_ARCH
> -platform PLATFORM
> QMAKESPEC
> -host-little-endian or -host-big-endian switch CFG_HOST_ENDIAN

These definitions of host* seem to contradict Volker's definition.
Host can be unix or windows, but arch is always unix.

Thanks for the replies, I'll have to keep thinking about it.

Tony