[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ros-dev
Subject:    Re: [ros-dev] [ros-diffs] [cfinck] 28423:
From:       "Colin Finck" <mail () colinfinck ! de>
Date:       2007-08-21 19:48:41
Message-ID: 004901c7e42c$46d756c0$9caa3f05 () colinhome
[Download RAW message or body]

> KJK::Hyperion wrote:
> Just how the hell can we have the host include path by default in
> the target compiler?

I didn't say that the target compiler uses the host include path.
I just talked about the host headers. But maybe this was a bit confusing:
When you compile a GCC cross-compiler and specify the --with-headers
parameter, it will copy some important missing headers from the host include
path into the target include path and run "fixincludes" to make them
compatible with GCC.

For Linux and FreeBSD, this includes the "stddef.h" header, which is also
responsible for defining wchar_t on these hosts.
Don't know about Mac OS X as Alex did the tests on that host.


> It sounds like, in fact, we are using target headers in host code

True.
Since we share the code for some libraries for host and target components,
we consequently mix target headers and host code.


> The solution, my good man, is to port RosBE to other hosts

Right, this will most-probably reduce the problems compiling ReactOS on
different hosts.
But if GCC continues using some headers, which are derived from the host
headers, we will still need different fixes for different hosts.

Regards,

Colin


[prev in list] [next in list] [prev in thread] [next in thread]