[openbeos] Re: compiler option -nostdinc
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: Open BeOS <openbeos@xxxxxxxxxxxxx>
- Date: Mon, 5 May 2003 17:23:05 +0200 (MEST)
On Mon, 5 May 2003, Axel Dörfler wrote:
> I just wanted to ask why we are using the -nostdinc option, and what's
> the purpose behind it.
> I think we initially used it to prevent gcc from including the Be
> headers - but (as we already found out long ago) that's not what this
> option does.
Did we? At least I believed until now, that it indeed causes the
standard include paths to be omitted.
> It prevents the headers from the gcc tool chain to be used.
Such as <new>? But it apparently works -- you use it in BFS, don't you?
> And while we are able to build OpenBeOS with this option on the x86
> platform, I cannot see a reason why we would like to replace the gcc
> headers with our own; AFAICT there is no advantage, but it causes
> trouble when trying to build it on other platforms.
> Does anybody mind or have reasons to mind when I remove that?
>
> AFAICT it doesn't have any side effects to the build on x86 (just did a
> full build).
If the option does, what I suspected it to do, then I find that it makes
very much sense, since we certainly want our build to depend as little as
possible on the build platform -- ideally we could build on any system
(any system with gcc maybe).
> BTW there seems to be a build problem: the objects for all kits are
> located in the same directory (which might turn out as annoying someday
> :-).
The objects for libopenbeos (i.e. App, Interface and Storage Kit) aren't
created in the subdirectories, since the library is built there. I think,
it should be possible to change this behavior, I just didn't take the time
to do it.
CU, Ingo
Other related posts:
