🚀 go-pugleaf

In article <EJH.96Feb27112424@larry.gsfc.nasa.gov>
ejh@larry.gsfc.nasa.gov (Edward Hartnett) writes:
>`-I-'
>     Any directories you specify with `-I' options before the `-I-'
>     option are searched only for the case of `#include "FILE"'; they
>     are not searched for `#include <FILE>'.
...
>I think I understand what this option does, but I don't quite
>understand why one would want to do this. Is it just to save the
>compiler's search time? Or is there some deeper meaning?

It's useful in case a file in your project has the same name as a
system header file.  For instance, I once inherited a project which
had a header file "task.h".  Unfortunately, this was also the name of
a system header included by other system headers, so when those other
headers said "#include <task.h>" they got the project's "task.h"
instead, which confused them no end.

   gcc ... -I. -Iproject_dir1 -Iproject_dir2 -I- -Isystem_dir1 -Isystem_dir2

ensured that system headers could only include other system headers
(assuming they were well enough behaved to use <...> notation).

-David
-- 
============================================================================
David Wald      http://theory.lcs.mit.edu/~wald/     wald@theory.lcs.mit.edu
============================================================================