[openbeos] Re: compiler option -nostdinc
- From: "Tony" <togermano@xxxxxxxxx>
- To: <openbeos@xxxxxxxxxxxxx>
- Date: Tue, 6 May 2003 20:17:12 -0400
windows is the best OS ever made i wanna have sex with it!
----- Original Message -----
From: "Marcus Overhagen" <ml@xxxxxxxxxxxx>
To: <openbeos@xxxxxxxxxxxxx>
Sent: Tuesday, May 06, 2003 10:09 PM
Subject: [openbeos] Re: compiler option -nostdinc
> > Hi there,
> >
> > I just wanted to ask why we are using the -nostdinc option, and what's
> > the purpose behind it.
>
> I added it, the purpose was to make the whole compiling of all
> sources independant of any headers from the host system
> (Windows, Linux or BeOS)
>
> > 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
> Yes,
>
> > option does. It prevents the headers from the gcc tool chain to be
> > used.
> Why is this a bad thing? Are you sure that the headers from the
> gcc tool chain are needed?
>
> > 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.
> You are only thinking of gcc here, why does it have it own headers at all?
> What happens if we would like to compile with openwatcom or Intel
compiler,
> do they also have their own haeders?
>
> > Does anybody mind or have reasons to mind when I remove that?
> I wouldn't mind, but are you sure that this is the correct way?
>
> > AFAICT it doesn't have any side effects to the build on x86 (just did a
> > full build).
> Most likely because you build on BeOS, what happens on other platforms
> with different gcc headers?
>
> Marcus
>
>
>
Other related posts:
