Re: [ft-devel] Slightly modified header inclusion scheme

[Werner LEMBERG]

>> OK, but there's a fundamental difference: freetype.pc now has a
>> *single* -I directive (e.g. -I/usr/include),
> 
> That's the problem.  Why exactly that is not desired is a bit
> complicated to explain.  [...]

Please give a real-world example.

> Instead, if FreeType uses a private include space,
> ie. /usr/include/freetype2, there's no chance that the -I introduced
> by FreeType will affect header inclusion order of other modules.

And how do you avoid name-clashes like FTGlyph.h and ftglyph.h on
case-insensitive file systems?  This is the very problem I would like
to solve.  The more -I we have, the higher are the chances that two
identical file names do clash.

> Does this make sense?

Not yet, sorry.


    Werner