This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: -I- option

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: ali hagigat <hagigatali at gmail dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Mon, 26 Sep 2011 11:57:24 +0100
Subject: Re: -I- option
References: <CAKKWdtcPUwzf-mrCpD4Mxwbw9ds3gLVTvCpZ+BYsZqsgM_YzTg@mail.gmail.com> <CAH6eHdTfSBEosgTCrM3Sjz+0Z6h=U6jbMSNfC=qW8qE3itEqTQ@mail.gmail.com> <CAKKWdtf_PPwDrj_HYLP8MoJRUfNwObAQdjeqPUd+Bm76_VhZgA@mail.gmail.com>

On 26 September 2011 11:50, ali hagigat wrote:
> So '-I." is the same as '-I-' except that the current directory is
> searched too, isn't it?

Read the effects of -I- carefully.

1. Any directories specified with -I options before -I- are searched
only for headers requested with "#include "file""; they are not
searched for "#include <file>"."

Does -I. do that?

2. In addition, -I- inhibits the use of the directory of the current
file directory as the first search directory for "#include "file"".

Does -I. do that?

References:
- -I- option
  - From: ali hagigat
- Re: -I- option
  - From: Jonathan Wakely
- Re: -I- option
  - From: ali hagigat

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]