[haiku-commits] Re: r37174 - haiku/trunk/data/develop

  • From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Sat, 19 Jun 2010 15:34:18 +0200

Hi Siarzhuk,

Siarzhuk Zharski <zharik@xxxxxx> wrote:
> Am 19.06.2010 11:48, schrieb Axel Dörfler:
> > Looks like system includes are incorrectly handled. Ie. they seem
> > to
> > use the old mechanism, but they are now used as local headers with
> > GCC4. "-isystem" is what is used there.
> Hm... Right now I have tried to build the test project with
>
> #include <opensslv.h>
>
> with following settings in the makefile
>
> SYSTEM_INCLUDE_PATH=/boot/common/include/openssl
>
> and it compiled without problems. The -I/boot/common/include/openssl
> worked well for my gcc 4.3.3.

Quoting GCC documentation:
"-iquotedir
    Add the directory dir to the head of the list of directories to be
searched for header files only for the case of `#include "file"'; they
are not searched for `#include <file>', otherwise just like -I. "

It works for you because you are using the old mechanism for system
headers. But that is wrong, you should use -isystem instead for those.

> PS: Are there any objections about the way of version info extracting
> and object directories separation criteria? May be gcc-2, gcc-4 will
> be
> enough here?

I haven't really looked at that, and don't really mind; for my Jam
engines I've just used objects-{debug|release}-{gcc2|gcc4}.

Bye,
   Axel.


Other related posts: