[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] Slightly modified header inclusion scheme
From: |
Werner LEMBERG |
Subject: |
Re: [ft-devel] Slightly modified header inclusion scheme |
Date: |
Tue, 23 Jun 2015 05:40:26 +0200 (CEST) |
>> 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
- [ft-devel] Slightly modified header inclusion scheme, Werner LEMBERG, 2015/06/22
- Re: [ft-devel] Slightly modified header inclusion scheme, Behdad Esfahbod, 2015/06/22
- Re: [ft-devel] Slightly modified header inclusion scheme, Werner LEMBERG, 2015/06/22
- Re: [ft-devel] Slightly modified header inclusion scheme, Behdad Esfahbod, 2015/06/22
- Re: [ft-devel] Slightly modified header inclusion scheme,
Werner LEMBERG <=
- Re: [ft-devel] Slightly modified header inclusion scheme, Werner LEMBERG, 2015/06/24
- Re: [ft-devel] Slightly modified header inclusion scheme, Behdad Esfahbod, 2015/06/24
- Re: [ft-devel] Slightly modified header inclusion scheme, Werner LEMBERG, 2015/06/25
- Re: [ft-devel] Slightly modified header inclusion scheme, Behdad Esfahbod, 2015/06/25